MCP servercom.tlsradar/tlsradar
SSL/TLS scanning, free Let's Encrypt issuance, and certificate-expiry monitoring.
Overview
Score?
UNRATED 0.672
of what a free look can see, on 30 looks
Looks
36
last 3 hr ago
Tools
16
changed 20 days ago
More info
URL
tlsradar.com/api/v1/mcp
streamable-http
Says it is
TLS Radar 1.0
protocol 2024-11-05
In the record since
32 days ago
Among servers18,413 with a card
0median 0.606 · this server 0.672 · highest on record 0.8561
Toolsfrom sha256:c16633ac88…6e7f0d · +0 −1 20 days ago
| Tool | Schema |
|---|---|
| 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 structu |
input · output |
| 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. |
input · output |
| 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_certifica |
input · output |
| 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 r |
input · output |
| 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. |
input · output |
| 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_certif |
input · output |
| get_account Return the current user's plan, limits, and usage so the client can render upgrade nudges proactively. |
input · output |
| 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 is |
input · output |
| 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. |
input · output |
| 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. |
input · output |
| 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). |
input · output |
| 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 cert |
input · output |
| 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 i |
input · output |
| remove_monitor Stop monitoring a domain. Accepts the domain name or the host_id returned by list_monitors. |
input · output |
| 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_ |
input · output |
| scan_domain Run a free, anonymous SSL/TLS scan against a hostname and return certificate details. No account required. |
input · output |
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 |
— |
Verify it yourself
npx teppi-check https://tlsradar.com/api/v1/mcpcurl -s https://api.teppi.xyz/v1/trust/mcp/mcs_01M1FZ29GWDA6510H6S9WQHHHD