Security & Testing

tlsradar.com

Manage SSL/TLS certificates, including scanning, issuing, and checking propagation.

1 endpoint17 known toolsFirst detected July 25, 2026Last detected July 25, 2026

ENDPOINT 1

https://tlsradar.com/api/v1/mcp

No auth detected

MCP server metadata

Name: TLS Radar
Version: 1.0

Capabilities

toolsresourcesprompts

Known tools 17

scan_domain

Run a free, anonymous SSL/TLS scan against a hostname and return certificate details.

Inferred read-only

create_certificate

Start issuing a FREE 90-day Let's Encrypt certificate for a domain (no account required).

Inferred read-only

check_certificate_propagation

Check whether the DNS TXT records for a certificate order have propagated (Cloudflare/Google/Quad9).

Inferred read-only

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.

Inferred read-only

get_certificate_status

Return the current state of a certificate order (dns_pending, validating, ready, completed, failed) and per-authorization Let's Encrypt statuses.

Inferred read-only

renew_certificate

Renew a certificate by cloning a recent order (requires the original order_id; Beacon purges orders after ~24h).

Inferred read-only

register_beacon_order

OBSOLETE - do not call.

Inferred read-only

get_account

Return the current user's plan, limits, and usage so the client can render upgrade nudges proactively.

Inferred read-only

list_monitors

List all certificates currently being monitored across the user's teams.

Inferred read-only

add_monitor

Add a domain to ongoing certificate monitoring with expiry alerts.

Inferred read-only

add_monitors

Add multiple domains to monitoring in one call.

Inferred read-only

remove_monitor

Stop monitoring a domain.

Inferred read-only

list_expiring_certificates

Return monitored certificates expiring within N days.

Inferred read-only

get_scan_history

Return recent scan results for a domain the user monitors.

Inferred read-only

export_monitors

Dump the user's monitors as a JSON structure suitable for backup, migration, or infrastructure-as-code workflows.

Inferred read-only

import_monitors

Create monitors from a JSON structure (typically produced by `export`).

Potential side effects

invite_team_member

Invite a user to a team by email.

Potential side effects

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.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.