mcp-ssl-inspector
io.github.geekmarine/mcp-ssl-inspectorgeekmarinestreamable-httpv1.0.0Scanned
Audits TLS/SSL handshake latency, HSTS headers, and HTTPS availability on the edge.
1 tool: 1 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the mcp-ssl-inspector can do
The mcp-ssl-inspector is published by the GitHub account geekmarine. It has 1 tool. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
1 tool brings in text other people can write (inspect_ssl_cert).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 21, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
1 tool
Only reads 1Show 1 read-only tool
inspect_ssl_certAudits TLS/SSL handshake latency, HSTS headers, cipher negotiation, and HTTPS certificate integrity.Reads text others writeNo findings
Why it is in this group
- The name "inspect_ssl_cert" says "inspect": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "http": it reads web pages, which anyone can write.
Description, as the server wrote it Audits TLS/SSL handshake latency, HSTS headers, cipher negotiation, and HTTPS certificate integrity.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:23 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2024-11-05
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http ssl-inspector https://mcp-ssl-inspector.stubby76.workers.dev/mcpclaude mcp add --transport http ssl-inspector https://mcp-ssl-inspector.stubby76.workers.dev/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__ssl-inspector__inspect_ssl_cert"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as ssl-inspector. Review it before you use it.
Capability tags behind 1 rule
- mcp__ssl-inspector__inspect_ssl_cert untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.geekmarine/mcp-ssl-inspector/verify?hash=e2c1c896a8fcb5285dfad150611349ac938b85e1744f096e8a20cd8f695f2de2" | jq -e '.changed == false'Pinned hash e2c1c896a8fc, from Nov 21, 2026, 07:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.geekmarine/mcp-ssl-inspector/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.geekmarine/mcp-ssl-inspector)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:34 UTC.
mcp-ssl-inspector: questions and answers
Answered from the scan above, not from the publisher's description.
Is the mcp-ssl-inspector safe?
- No scan can promise that. What its definitions show: 1 tool, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the mcp-ssl-inspector delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the mcp-ssl-inspector do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the mcp-ssl-inspector have?
- 1 tool: 1 read. inspect_ssl_cert.
Does the mcp-ssl-inspector need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the mcp-ssl-inspector send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the mcp-ssl-inspector changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.