TLS Radar

Name: TLS Radar
Author: com.tlsradar

MCP serverMCP

SSL/TLS scanning, free Let's Encrypt issuance, and certificate-expiry monitoring.

by com.tlsradarrepository ↗homepage ↗v0.5.1

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"tls-radar","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability111/111 checks ok

when	check	result	http	latency	detail
6 h ago	mcp initialize	ok	200	399 ms	server TLS Radar 1.0 · protocol 2024-11-05 · 16 tools
13 h ago	mcp initialize	ok	200	385 ms	server TLS Radar 1.0 · protocol 2024-11-05 · 16 tools
23 h ago	mcp initialize	ok	200	3065 ms	server TLS Radar 1.0 · protocol 2024-11-05 · 16 tools
32 h ago	mcp initialize	ok	200	391 ms	server TLS Radar 1.0 · protocol 2024-11-05 · 16 tools
2 d ago	mcp initialize	ok	200	396 ms	server TLS Radar 1.0 · protocol 2024-11-05 · 16 tools
2 d ago	mcp initialize	ok	200	3191 ms	server TLS Radar 1.0 · protocol 2024-11-05 · 16 tools
2 d ago	mcp initialize	ok	200	2925 ms	server TLS Radar 1.0 · protocol 2024-11-05 · 16 tools
2 d ago	mcp initialize	ok	200	373 ms	server TLS Radar 1.0 · protocol 2024-11-05 · 16 tools
3 d ago	mcp initialize	ok	200	730 ms	server TLS Radar 1.0 · protocol 2024-11-05 · 16 tools
3 d ago	mcp initialize	ok	200	595 ms	server TLS Radar 1.0 · protocol 2024-11-05 · 16 tools

Tools observed via MCP handshake

scan_domain — Run a free, anonymous SSL/TLS scan against a hostname and return certificate details. No account required.
create_certificate — Start issuing a FREE Let's Encrypt certificate for a domain (no account required). Step 1 of 3. Lifetime is Let's Encrypt's default: 90 days today, 64 days from
check_certificate_propagation — 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 cal
finalize_certificate — 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 - cal
get_certificate_status — Return the current state of a certificate order (dns_pending, validating, ready, completed, failed) and per-authorization Let's Encrypt statuses. Use it to resu
renew_certificate — 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 record
get_account — Return the current user's plan, limits, and usage so the client can render upgrade nudges proactively.
list_monitors — 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 mon
add_monitor — 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, th
add_monitors — 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 a
remove_monitor — Stop monitoring a domain. Accepts the domain name or the host_id returned by list_monitors.
list_expiring_certificates — Return monitored certificates expiring within N days. Defaults to 30. If the response's structuredContent includes a `nudge` object, the user is watching enough
get_scan_history — Return recent scan results for a domain the user monitors. Useful for spotting issuer changes, grade drops, or vulnerability appearances over time.
export_monitors — 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 domai
import_monitors — 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 — 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 ca

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registrycom.tlsradar/tlsradar

first seen 2 mo ago · fetched 8 h agoopen ↗

Field history (7 recent events)

2 mo ago · declared · summary → "SSL/TLS scanning, free Let's Encrypt issuance, and certificate-expiry monitoring."
2 mo ago · declared · description → "SSL/TLS scanning, free Let's Encrypt issuance, and certificate-expiry monitoring."
2 mo ago · declared · publisherName → "com.tlsradar"
2 mo ago · declared · homepageUrl → "https://tlsradar.com/cli"
2 mo ago · declared · repoUrl → "https://github.com/TLS-Radar/tlsradar-claude-plugin"
2 mo ago · declared · version → "0.5.1"
2 mo ago · declared · protocols → ["mcp"]

TLS Radar

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from