https://tls-radar--slmusayev.run.tools ↗
tls-radar is a remote MCP server published at tls-radar--slmusayev.run.tools. Its tool list could not be read; the server is closed to direct calls. It answers direct calls with an authentication wall.
Run SSL/TLS scans, issue free Let's Encrypt certificates (private key stays local), and monitor certificate expiry from inside Claude Code or Cowork - through a single MCP server, no account needed for scans and issuance.
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
register_beacon_order — Tool is explicitly obsolete but remains in the schema.import_monitors — The 'payload' parameter type is not explicitly defined.| Run | Era | Modern | ms | Legacy | ms | Versions |
|---|
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
Each cell is one probe run. Faded cells are incomplete probes — one leg did not answer, so the era is inconclusive.
No era measurements yet.
The two probe legs separately: modern server/discover and legacy initialize.
No response-time measurements yet.
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/slmusayev-tls-radar)<a href="https://mcpmetrics.io/servers/slmusayev-tls-radar"><img src="https://mcpmetrics.io/badge/slmusayev/tls-radar/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to see