Remote MCP · Endpoint
Scry MCP server
No. Scry answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://mcp.tunnelmind.ai/mcp
The last check completed an MCP handshake.
- Registry name
- ai.tunnelmind/scry
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-03-26
- Handshake latency
- 312 ms
- Tools exposed
- 12 tools
- Uptime, last 30 days
- 66.7% from 18 checks
- Described by its publisher as
- Free IPv4 lookups against a distributed attacker-observation corpus.
- Website
- https://api.tunnelmind.ai/
- Repository
- https://github.com/TunnelMind/scry-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 312 ms |
| 2 days ago | Handshake completed | 335 ms |
| 4 days ago | Handshake completed | 348 ms |
| 6 days ago | Handshake completed | 295 ms |
| 7 days ago | Handshake completed | 292 ms |
| 9 days ago | Handshake completed | 320 ms |
| 10 days ago | Handshake completed | 311 ms |
| 11 days ago | Handshake completed | 381 ms |
| 14 days ago | Handshake completed | 296 ms |
| 15 days ago | Handshake completed | 310 ms |
| 17 days ago | Failed - the server returned an HTTP error | — |
| 18 days ago | Failed - the server returned an HTTP error | — |
| 19 days ago | Failed - the server returned an HTTP error | — |
| 20 days ago | Failed - the server returned an HTTP error | — |
| 21 days ago | Failed - the server returned an HTTP error | — |
| 22 days ago | Failed - the server returned an HTTP error | — |
| 23 days ago | Handshake completed | 527 ms |
| 24 days ago | Handshake completed | 315 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 12 responding of 18.
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 Scry and makes no claim about it beyond what these checks measured.