TLS Radar is a remote MCP server that gives an AI agent 17 tools, among them add_monitor, add_monitors, check_certificate_propagation. It answers at https://tlsradar.com/api/v1/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 5 September 2026; the last check, on 18 October 2026, succeeded.
SSL/TLS scanning, free Let's Encrypt issuance, and certificate-expiry monitoring.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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, the response's structuredContent carries a limit-reached payload - when relaying i Inputs: domain |
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 as add_monitor. Inputs: domains |
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 call finalize_certificate. Returns per-record resolver results. Inputs: order_id |
create_certificate | 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" (default; publish a TXT record; covers apex + www) or "http-01" (serve a file over HT Inputs: domain, email, challenge, marketing_consent, client_id |
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 domain configuration. |
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 - call after check_certificate_propagation reports all_found. STRONGLY PREFER passing Inputs: order_id, csr_pem, passphrase, max_wait_seconds, resume_token |
get_account | Return the current user's plan, limits, and usage so the client can render upgrade nudges proactively. |
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 resume an interrupted issuance. Inputs: order_id |
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. Inputs: domain, limit |
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 per-domain status. Inputs: payload |
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 cap is hit). Inputs: email, team_id, role |
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 soon-to-expire certs to benefit from a higher tier - mention it casually ONCE ( Inputs: within |
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 monitor cap - surface it casually ONCE (lead with `nudge.recommended_upgrade`, ment |
register_beacon_order | OBSOLETE - do not call. The cert→monitoring handoff is server-side now (issue via create_certificate, which records the order itself). This tool is kept only so old plugin versions that still call it don't error; it remains idempotent and h Inputs: order_id, email, domain, webhook_secret |
remove_monitor | Stop monitoring a domain. Accepts the domain name or the host_id returned by list_monitors. Inputs: domain, host_id |
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 records - then poll check_certificate_propagation and call finalize_certificate. If yo Inputs: order_id |
scan_domain | Run a free, anonymous SSL/TLS scan against a hostname and return certificate details. No account required. Inputs: domain, client_id |
Every block below points at https://tlsradar.com/api/v1/mcp. Pick your client and copy.
claude mcp add --transport http tls-radar https://tlsradar.com/api/v1/mcp
{
"mcpServers": {
"tls-radar": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://tlsradar.com/api/v1/mcp"]
}
}
}{
"mcpServers": {
"tls-radar": {
"url": "https://tlsradar.com/api/v1/mcp"
}
}
}{
"servers": {
"tls-radar": {
"type": "http",
"url": "https://tlsradar.com/api/v1/mcp"
}
}
}{
"context_servers": {
"tls-radar": {
"url": "https://tlsradar.com/api/v1/mcp"
}
}
}{
"mcpServers": {
"tls-radar": {
"serverUrl": "https://tlsradar.com/api/v1/mcp"
}
}
}{
"mcpServers": {
"tls-radar": {
"url": "https://tlsradar.com/api/v1/mcp"
}
}
}name: TLS Radar
version: 0.0.1
schema: v1
mcpServers:
- name: TLS Radar
type: streamable-http
url: https://tlsradar.com/api/v1/mcp{
"mcpServers": {
"tls-radar": {
"httpUrl": "https://tlsradar.com/api/v1/mcp"
}
}
}{
"mcpServers": {
"tls-radar": {
"type": "http",
"url": "https://tlsradar.com/api/v1/mcp"
}
}
}{
"mcpServers": {
"tls-radar": {
"url": "https://tlsradar.com/api/v1/mcp"
}
}
}goose://extension?url=https%3A%2F%2Ftlsradar.com%2Fapi%2Fv1%2Fmcp&type=streamable_http&id=tls-radar&name=TLS%20Radar
It answered our last check on 18 October 2026 in 484 ms. Over 10 checks since 5 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by tlsradar.com and served from tlsradar.com, the vendor's own domain: https://tlsradar.com/api/v1/mcp.
17, as returned by the server's own tools/list on 31 August 2026: add_monitor, add_monitors, check_certificate_propagation, create_certificate, export_monitors, finalize_certificate, get_account, get_certificate_status, and 9 more.
It answered our last check on 18 October 2026 in 484 ms. Over 10 checks since 5 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://tlsradar.com/api/v1/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.tlsradar. Endpoint host: tlsradar.com. ARD identifier: urn:air:com.tlsradar:mcp:tlsradar.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.