Remote MCP · Endpoint

io.github.geekmarine/mcp-ssl-inspector MCP server

No. io.github.geekmarine/mcp-ssl-inspector answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://mcp-ssl-inspector.stubby76.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.geekmarine/mcp-ssl-inspector
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
74 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Audits TLS/SSL handshake latency, HSTS headers, and HTTPS availability on the edge.
Repository
https://github.com/geekmarine/mcp-ssl-inspector
Listing
From the official MCP registry (active).
Recent checks of io.github.geekmarine/mcp-ssl-inspector
CheckedResultHandshake
6 hours agoHandshake completed74 ms
9 days agoHandshake completed68 ms
10 days agoHandshake completed70 ms
11 days agoHandshake completed118 ms
12 days agoHandshake completed55 ms
14 days agoHandshake completed83 ms
14 days agoHandshake completed76 ms
15 days agoHandshake completed65 ms
17 days agoHandshake completed120 ms
19 days agoHandshake completed61 ms
22 days agoHandshake completed73 ms
24 days agoHandshake completed63 ms
26 days agoHandshake completed115 ms
28 days agoHandshake completed143 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 24 responding of 24.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with io.github.geekmarine/mcp-ssl-inspector and makes no claim about it beyond what these checks measured.