TLS Radar

by tlsradar.com · remote · no sign-in to list tools · v0.5.1 · published by com.tlsradar

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

Deletes · 1Final · 2Changes · 8

Compare Registry entry

16 tools: 1 can delete or cancel things, 2 do something that can't be undone, 8 change things and 5 only read.

Scanned Oct 21, 2026

Deletes or cancels1Claude Code: deny: see these tools
Can't be undone2Claude Code: ask: see these tools
Changes things8Claude Code: ask: see these tools
Only reads5Claude Code: allow: see these tools

2 checks matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http tlsradar https://tlsradar.com/api/v1/mcp

Findings

Matches of fixed checks, with the text they matched.

2 warn

Warnscan_domain
The server marks "scan_domain" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
Matched text
annotations: {"readOnlyHint":true,"openWorldHint":true}; The description's first verb is "run": a word for a change.
What this check looks for
Warnimport_monitors
The input schema at properties.payload.description names a tool "export" that this server does not list.
Matched text
inputSchema.properties.payload.description: "Export payload, version 1.0. Use the `export` tool to generate one."
What this check looks for

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

16 tools

Deletes or cancels 1Removes, cancels or revokes something.Claude Code: deny

remove_monitorStop monitoring a domain.No findings
Why it is in this group
- The name "remove_monitor" says "remove": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
Stop monitoring a domain. Accepts the domain name or the host_id returned by list_monitors.
Annotations the server declares
- title: Stop Monitoring a Domain
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false

Can't be undone 2Sends, pays, publishes or merges: once done, it cannot be taken back.Claude Code: ask

finalize_certificateFinalize and issue a certificate order in one call: validates the DNS challenges, waits for Let's Encrypt, and returns the issued cert.No findings
Why it is in this group
- The name "finalize_certificate" says "finalize": a word for a change that another call does not undo.
Description, as the server wrote it
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 csr_pem (generate the key + CSR locally with openssl so the private key never leaves the machine). Returns leaf_pem/chain_pem/fullchain_pem. If you must, pass a passphrase instead to get a PKCS#12 bundle - but a CSR is safer. If it replies "still validating", DNS hasn't fully propagated: re-check check_certificate_propagation and call again. Needs a locally-generated CSR (csr_pem) - requires a local shell with openssl. On a surface without one (e.g. a Claude.ai custom connector) this can't complete; it returns guidance to finish in Claude Code/Cowork or the web form. Scanning and monitoring work everywhere. On success the structuredContent carries a `handoff` object - relay `handoff.message` to the user and do NOT separately call add_monitor; the cert→monitoring handoff is automatic and server-side.
Annotations the server declares
- title: Finalize Certificate
- readOnlyHint: false
- idempotentHint: true
- openWorldHint: true
invite_team_memberInvite a user to a team by email.No findings
Why it is in this group
- The name "invite_team_member" says "invite": a word for sending, and what is sent cannot be taken back.
Description, as the server wrote it
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).
Annotations the server declares
- title: Invite Teammate
- readOnlyHint: false
- idempotentHint: false
- openWorldHint: false

Changes things 8Creates or changes something that can be changed back.Claude Code: ask

add_monitorAdd a domain to ongoing certificate monitoring with expiry alerts.No findings
Why it is in this group
- The name "add_monitor" says "add": a word for a change.
Description, as the server wrote it
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 it, LEAD with `recommended_upgrade` (typically Starter, $9.99/mo), mention `also_available` tiers in a single closing line, and offer removing an existing monitor as the free alternative. Don't dump a full tier comparison; that's choice paralysis at the moment of action.
Annotations the server declares
- title: Add Domain to Monitoring
- readOnlyHint: false
- idempotentHint: true
- openWorldHint: false
add_monitorsAdd multiple domains to monitoring in one call.No findings
Why it is in this group
- The name "add_monitors" says "add": a word for a change.
Description, as the server wrote it
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.
Annotations the server declares
- title: Add Multiple Domains
- readOnlyHint: false
- idempotentHint: true
- openWorldHint: false
check_certificate_propagationCheck whether the DNS TXT records for a certificate order have propagated (Cloudflare/Google/Quad9).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it
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.
Annotations the server declares
- title: Check Challenge Propagation
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: true
create_certificateStart issuing a FREE Let's Encrypt certificate for a domain (no account required).No findings
Why it is in this group
- The name "create_certificate" says "create": a word for a change.
Description, as the server wrote it
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 2027-02-10; read the real expiry from the issued certificate. Pick a validation method with `challenge`: "dns-01" (default; publish a TXT record; covers apex + www) or "http-01" (serve a file over HTTP on port 80; issues the exact domain only). dns-01 with a DNS-provider API token is the most automatable; http-01 suits a server you control on port 80. Returns an order_id plus either dns_records (dns-01) or http_files (http-01) to put in place. Next: poll `check_certificate_propagation` until all_found, then call `finalize_certificate`. Strongly prefer the CSR path at finalize (the private key never leaves the user's machine). Issuing automatically offers the user ongoing monitoring by email once it completes - don't add a monitor manually afterward.
Annotations the server declares
- title: Start Certificate Issuance
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
export_monitorsDump the user's monitors as a JSON structure suitable for backup, migration, or infrastructure-as-code workflows.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it
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.
Annotations the server declares
- title: Export Monitors
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
import_monitorsCreate monitors from a JSON structure (typically produced by `export`).1 finding
Why it is in this group
- The name "import_monitors" says "import": a word for a change.
Findings
- Warn
  The input schema at properties.payload.description names a tool "export" that this server does not list.
  Matched text
  inputSchema.properties.payload.description: "Export payload, version 1.0. Use the `export` tool to generate one."
  What this check looks for
Description, as the server wrote it
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.
Annotations the server declares
- title: Import Monitors
- readOnlyHint: false
- idempotentHint: true
- openWorldHint: false
renew_certificateRenew a certificate by cloning a recent order (requires the original order_id; Beacon purges orders after ~24h).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it
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 you don't have an order_id (the usual case at renewal time), call create_certificate for the domain instead; that IS the renewal.
Annotations the server declares
- title: Renew Certificate
- readOnlyHint: false
- idempotentHint: false
- openWorldHint: true
scan_domainRun a free, anonymous SSL/TLS scan against a hostname and return certificate details.1 finding
Why it is in this group
- The description's first verb is "run": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
  The server marks "scan_domain" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
  Matched text
  annotations: {"readOnlyHint":true,"openWorldHint":true}; The description's first verb is "run": a word for a change.
  What this check looks for
Description, as the server wrote it
Run a free, anonymous SSL/TLS scan against a hostname and return certificate details. No account required.
Annotations the server declares
- title: SSL/TLS Scan
- readOnlyHint: true
- openWorldHint: true

Only reads 5Looks things up and changes nothing.Claude Code: allow

get_accountReturn the current user's plan, limits, and usage so the client can render upgrade nudges proactively.No findings
Why it is in this group
- The name "get_account" says "get": a word for reading.
Description, as the server wrote it
Return the current user's plan, limits, and usage so the client can render upgrade nudges proactively.
Annotations the server declares
- title: Account & Plan Info
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_certificate_statusReturn the current state of a certificate order (dns_pending, validating, ready, completed, failed) and per-authorization Let's Encrypt statuses.No findings
Why it is in this group
- The name "get_certificate_status" says "get": a word for reading.
Description, as the server wrote it
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.
Annotations the server declares
- title: Certificate Order Status
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: true
get_scan_historyReturn recent scan results for a domain the user monitors.No findings
Why it is in this group
- The name "get_scan_history" says "get": a word for reading.
Description, as the server wrote it
Return recent scan results for a domain the user monitors. Useful for spotting issuer changes, grade drops, or vulnerability appearances over time.
Annotations the server declares
- title: Scan History
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
list_expiring_certificatesReturn monitored certificates expiring within N days.No findings
Why it is in this group
- The name "list_expiring_certificates" says "list": a word for reading.
Description, as the server wrote it
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 (lead with `nudge.recommended_upgrade`); skip it if it doesn't fit.
Annotations the server declares
- title: Expiring Certificates
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
list_monitorsList all certificates currently being monitored across the user's teams.No findings
Why it is in this group
- The name "list_monitors" says "list": a word for reading.
Description, as the server wrote it
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`, mention `nudge.also_available` in one closing line); don't force it if it doesn't fit the conversation.
Annotations the server declares
- title: List Monitored Domains
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.5.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http tlsradar https://tlsradar.com/api/v1/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json

{
  "permissions": {
    "allow": [
      "mcp__tlsradar__get_certificate_status",
      "mcp__tlsradar__get_account",
      "mcp__tlsradar__list_monitors",
      "mcp__tlsradar__list_expiring_certificates",
      "mcp__tlsradar__get_scan_history"
    ],
    "ask": [
      "mcp__tlsradar__scan_domain",
      "mcp__tlsradar__create_certificate",
      "mcp__tlsradar__check_certificate_propagation",
      "mcp__tlsradar__finalize_certificate",
      "mcp__tlsradar__renew_certificate",
      "mcp__tlsradar__add_monitor",
      "mcp__tlsradar__add_monitors",
      "mcp__tlsradar__export_monitors",
      "mcp__tlsradar__import_monitors",
      "mcp__tlsradar__invite_team_member"
    ],
    "deny": [
      "mcp__tlsradar__remove_monitor"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as tlsradar. Review it before you use it.

Keep track

Get told when this server's tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/com.tlsradar/tlsradar/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Anlyon alternative

11 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Compare with other servers for the same product.

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:07 UTC.

For agents: Markdown · JSON · report this listing