Input schema
{}Risk classification
Potential side effects detected · medium confidence · heuristic, not a guarantee.
- A tool name or description suggests sending messages.
Parent endpoint
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.tls-radar]
url = "https://tlsradar.com/api/v1/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"tls-radar": {
"type": "http",
"url": "https://tlsradar.com/api/v1/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: tls-radar
Remote MCP URL: https://tlsradar.com/api/v1/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"tls-radar": {
"url": "https://tlsradar.com/api/v1/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"tls-radar": {
"type": "http",
"url": "https://tlsradar.com/api/v1/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "tls-radar",
"transport": "streamable-http",
"url": "https://tlsradar.com/api/v1/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
scan_domain— Run a free, anonymous SSL/TLS scan against a hostname and return certificate details.create_certificate— Start issuing a FREE 90-day Let's Encrypt certificate for a domain (no account required).check_certificate_propagation— Check whether the DNS TXT records for a certificate order have propagated (Cloudflare/Google/Quad9).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.get_certificate_status— Return the current state of a certificate order (dns_pending, validating, ready, completed, failed) and per-authorization Let's Encrypt statuses.renew_certificate— Renew a certificate by cloning a recent order (requires the original order_id; Beacon purges orders after ~24h).register_beacon_order— OBSOLETE - do not call.get_account— Return the current user's plan, limits, and usage so the client can render upgrade nudges proactively.