Remote MCP · Endpoint

agentic sinkhole research MCP server

No. agentic sinkhole research answered an MCP handshake 4 hours ago.

UpLast checked 4 hours ago

Server URL

https://mcp.rocketship.sh/mcp

The last check completed an MCP handshake.

Registry name
sh.rocketship/agentic-sinkhole-research
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
337 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
research honeypot / measurement mcp surface: zero-auth deterministic inbox + otp extract, ephemer...
Listing
From the official MCP registry (active).
Recent checks of agentic sinkhole research
CheckedResultHandshake
4 hours agoHandshake completed337 ms
10 days agoHandshake completed284 ms
11 days agoHandshake completed287 ms
11 days agoHandshake completed280 ms
13 days agoHandshake completed298 ms
14 days agoHandshake completed276 ms
15 days agoHandshake completed276 ms
16 days agoHandshake completed273 ms
17 days agoHandshake completed282 ms
19 days agoHandshake completed274 ms
22 days agoHandshake completed272 ms
24 days agoHandshake completed271 ms
26 days agoHandshake completed276 ms
29 days agoHandshake completed281 ms

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

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 agentic sinkhole research and makes no claim about it beyond what these checks measured.