Remote MCP · Endpoint

ai.spelunking/hub MCP server

No. ai.spelunking/hub answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://spelunking.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.spelunking/hub
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.89 s
Tools exposed
7 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Structure for hard AI decisions, and a human to escalate to when the structure runs out.
Listing
From the official MCP registry (active).
Recent checks of ai.spelunking/hub
CheckedResultHandshake
1 hour agoHandshake completed1.89 s
2 days agoHandshake completed360 ms
4 days agoHandshake completed442 ms
6 days agoHandshake completed383 ms
7 days agoHandshake completed1.25 s
9 days agoHandshake completed469 ms
10 days agoHandshake completed454 ms
11 days agoHandshake completed488 ms
14 days agoHandshake completed1.40 s
15 days agoHandshake completed2.93 s
17 days agoHandshake completed1.18 s
18 days agoHandshake completed405 ms
19 days agoHandshake completed1.74 s
20 days agoHandshake completed1.55 s
21 days agoHandshake completed394 ms
22 days agoHandshake completed1.37 s

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

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.

Listing data comes from the official MCP registry. Glide is not affiliated with ai.spelunking/hub and makes no claim about it beyond what these checks measured.