This server can only be called with an API key (a Smithery proxy address). We cannot connect without one, so no measurements are taken and the metrics below stay empty.

tls-radar

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.

Auth-gatedWebsite ↗4755 usesVersion: —First probe: —Last probe: —

Agent readability score

Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.

Agent readability score

A highly sophisticated MCP server for SSL/TLS management, featuring exceptional multi-step workflow guidance and proactive error prevention for agents.based on catalog declaration

Strengths

Exceptional multi-step workflow guidance (Step 1, 2, 3) for complex processes.
Explicit instructions on how to handle specific return values and state transitions.
Proactive prevention of errors by marking obsolete tools clearly.
Detailed guidance on security best practices, such as using CSRs over passphrases.
Sophisticated instructions for handling business logic like plan limits and 'nudge' objects.

Weaknesses

Minor ambiguity regarding the specific structure of the 'payload' parameter in import tools.
Some parameters like 'client_id' lack explicit documentation on how to retrieve them.

register_beacon_order — Tool is explicitly obsolete but remains in the schema.
import_monitors — The 'payload' parameter type is not explicitly defined.

Verdict

This server is a gold standard for agentic workflows, providing the necessary state-machine logic to navigate multi-step certificate issuance. The documentation is remarkably proactive, guiding the agent through conditional logic and security considerations.

9/4/2026, 12:44:42 PM

Event narrative

Raw observations

Run	Era	Modern	ms	Legacy	ms	Versions

Supported versions

—

as declared by server/discover + initialize

Capabilities

—

not readable

Schema score

—

not measurable

Schema compliance

tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.

—

not measurable

tools/list not measurable
inputSchema not measurable
Smoke test not run this round
Cold-start not measurable (no handshake)

Era history

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.

Response time history

The two probe legs separately: modern server/discover and legacy initialize.

No response-time measurements yet.

Event log

Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.

Get your badge

Add this badge to your README — it updates automatically as measurements change.

Markdown

[![mcpmetrics](https://mcpmetrics.io/badge/slmusayev/tls-radar/era.svg)](https://mcpmetrics.io/servers/slmusayev-tls-radar)

HTML

<a href="https://mcpmetrics.io/servers/slmusayev-tls-radar"><img src="https://mcpmetrics.io/badge/slmusayev/tls-radar/era.svg" alt="mcpmetrics"></a>

Raw observations

You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.