Tls Radar

Name: Tls Radar
Author: TLS-Radar

@TLS-Radar

About Tls Radar

Run SSL/TLS scans, issue free Let's Encrypt certificates (private key stays local), and monitor certificate expiry from inside Claude Code or Cowork - through a single MCP server, no account needed for scans and issuance.

#ssl #tls #certificates #monitoring #letsencrypt #security

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "tls-radar": {
      "type": "http",
      "url": "https://tlsradar.com/api/v1/mcp"
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is TLS Radar?

TLS Radar is an MCP server that lets you run SSL/TLS scans, issue free Let's Encrypt certificates, and manage certificate monitoring directly from Claude Code or Claude Cowork, with no configuration required.

How to use TLS Radar?

Install via the Claude Code marketplace by running /plugin marketplace add TLS-Radar/tlsradar-claude-plugin then /plugin install tlsradar@tlsradar. Use slash commands such as /tls-scan example.com for a free scan or /tls-cert mydomain.dev to issue a certificate. Run /mcp once to connect for monitoring via OAuth.

Key features of TLS Radar

Run free SSL/TLS scans with no account
Issue free 90-day Let's Encrypt certificates
Private keys generated locally, never sent
Monitor certificate expiration with alerts
Works in both Claude Code and Cowork
OAuth 2.0 + PKCE for authenticated tools

Use cases of TLS Radar

Scan any domain's TLS configuration instantly from chat
Issue and renew a free Let's Encrypt certificate for a domain
Add automated monitoring for one or more domains
View expiration status and upcoming renewals in plain language
Export/import monitor lists or invite teammates

FAQ from TLS Radar

Do I need an account to use TLS Radar?

No. Public tools like scan and certificate issuance work without any account. For monitoring, connect once via /mcp using built-in OAuth.

How are private keys handled during certificate issuance?

The plugin generates the private key and CSR locally using openssl. Only the CSR is sent to the server; the private key never leaves your computer.

What are the free plan limits?

The free plan includes 1 monitor, 1 alert per month (7 days before expiry), unlimited scans (rate-limited), and free Let's Encrypt issuance.

How do I connect for monitoring?

Run /mcp in Claude Code. This triggers an OAuth 2.0 + PKCE flow: your client fetches the authorization server metadata, registers as a public client, and opens the browser for consent. The token is managed by Claude Code automatically.

What about privacy and security?

The plugin sends no tracking headers and stores an anonymous install ID in ~/.config/tlsradar/install_id (opt out by deleting that file). OAuth tokens expire in 2 hours; refresh tokens rotate and are capped at 90 days. Access can be revoked at tlsradar.com/oauth/authorized_applications.