# TLS Radar

> TLS Radar, an MCP server by tlsradar.com, listed from the official MCP registry. Indexed, not reviewed: facts and our own checks, no score or ranking. SSL/TLS scanning, free Let's Encrypt issuance, and certificate-expiry monitoring.

- Canonical: https://www.anchorterminal.com/tools/tlsradar
- Markdown: https://www.anchorterminal.com/tools/tlsradar.md (~1,300 tokens)
- Slim: https://www.anchorterminal.com/tools/tlsradar.min.md (~1,230 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/tools/tlsradar.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-04

# TLS Radar

> Indexed, not reviewed: facts from the official MCP registry and our own checks. No score, grade or rank, and not in the rankings until the panel reviews it. How the index works: https://www.anchorterminal.com/indexed/

- Kind: MCP server, by tlsradar.com (https://tlsradar.com/cli)
- Category: Observability & incidents (https://www.anchorterminal.com/categories/observability.md)
- Listed because: It's published in the registry under tlsradar.com, a namespace the registry only gives to whoever proves they control that domain.
- What the official MCP registry says: SSL/TLS scanning, free Let's Encrypt issuance, and certificate-expiry monitoring.

## Facts

- MCP registry: `com.tlsradar/tlsradar` 0.5.1
- Endpoint: https://tlsradar.com/api/v1/mcp (streamable HTTP)
- Source: https://github.com/TLS-Radar/tlsradar-claude-plugin
- Website: https://tlsradar.com/cli
- GitHub stars: 3
- Registry entry updated: 2026-06-15

## Tools

- Tools it lists (16, about 4,158 tokens of context, `tools/list` without credentials, checked 2026-10-04 22:24 UTC):
  - `scan_domain` (read-only): Run a free, anonymous SSL/TLS scan against a hostname and return certificate details. No account required.
  - `create_certificate` (writes): Start issuing a FREE 90-day Let's Encrypt certificate for a domain (no account required). Step 1 of 3. Pick a validation method with `challenge`: "dns-01"…
  - `check_certificate_propagation` (read-only): Check whether the DNS TXT records for a certificate order have propagated (Cloudflare/Google/Quad9). Step 2 of issuance - poll until all_found is true, then…
  - `finalize_certificate` (writes): Finalize and issue a certificate order in one call: validates the DNS challenges, waits for Let's Encrypt, and returns the issued cert. Step 3 of issuance -…
  - `get_certificate_status` (read-only): Return the current state of a certificate order (dns_pending, validating, ready, completed, failed) and per-authorization Let's Encrypt statuses. Use it to…
  - `renew_certificate` (writes): Renew a certificate by cloning a recent order (requires the original order_id; Beacon purges orders after ~24h). Returns a new order_id and fresh DNS TXT…
  - `get_account` (read-only): Return the current user's plan, limits, and usage so the client can render upgrade nudges proactively.
  - `list_monitors` (read-only): List all certificates currently being monitored across the user's teams. If the response's structuredContent includes a `nudge` object, the user is at their…
  - `add_monitor` (writes): Add a domain to ongoing certificate monitoring with expiry alerts. Requires authentication (the user runs /mcp once). If the plan's monitor limit is reached,…
  - `add_monitors` (writes): Add multiple domains to monitoring in one call. Returns a per-domain status so the caller can show partial-success outcomes. Honors the same plan-limit checks…
  - `remove_monitor` (writes): Stop monitoring a domain. Accepts the domain name or the host_id returned by list_monitors.
  - `list_expiring_certificates` (read-only): Return monitored certificates expiring within N days. Defaults to 30. If the response's structuredContent includes a `nudge` object, the user is watching…
  - `get_scan_history` (read-only): Return recent scan results for a domain the user monitors. Useful for spotting issuer changes, grade drops, or vulnerability appearances over time.
  - `export_monitors` (read-only): Dump the user's monitors as a JSON structure suitable for backup, migration, or infrastructure-as-code workflows. Tokens and PII are NEVER included - only…
  - `import_monitors` (writes): Create monitors from a JSON structure (typically produced by `export`). Skips domains the user is already monitoring; honors the plan's domain limit. Returns a…
  - `invite_team_member` (writes): Invite a user to a team by email. Defaults to the user's current team. Honors the plan's seat limit (returns the same upgrade payload as add_monitor when the…
- How its tools read to an agent (0 errors, 1 warning, 0 notes, about 4,158 tokens; rules at https://www.anchorterminal.com/check.md; not part of the score):
  - warn TC13 import_monitors: payload (object with no properties)

- JSON: https://www.anchorterminal.com/api/v1/tools/tlsradar.json
- Being indexed says nothing about quality, and nobody can pay for it. Ask for a review: https://www.anchorterminal.com/builders/#claiming