Remote MCP · Endpoint
Scry MCP server
Yes, as of 1 hour ago: the server returned an HTTP error.
DownLast checked 1 hour ago
Server URL
https://mcp.tunnelmind.ai/mcp
The last check failed: the server returned an HTTP error.
- Registry name
- ai.tunnelmind/scry
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 12 tools
- Uptime, last 30 days
- 89.5% from 19 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 |
|---|---|---|
| 1 hour ago | Failed - the server returned an HTTP error | — |
| 10 hours ago | Failed - the server returned an HTTP error | — |
| 1 day ago | Handshake completed | 375 ms |
| 2 days ago | Handshake completed | 304 ms |
| 4 days ago | Handshake completed | 346 ms |
| 4 days ago | Handshake completed | 335 ms |
| 5 days ago | Handshake completed | 328 ms |
| 6 days ago | Handshake completed | 320 ms |
| 8 days ago | Handshake completed | 511 ms |
| 11 days ago | Handshake completed | 324 ms |
| 13 days ago | Handshake completed | 366 ms |
| 16 days ago | Handshake completed | 340 ms |
| 18 days ago | Handshake completed | 376 ms |
| 20 days ago | Handshake completed | 312 ms |
| 22 days ago | Handshake completed | 335 ms |
| 24 days ago | Handshake completed | 348 ms |
| 26 days ago | Handshake completed | 295 ms |
| 27 days ago | Handshake completed | 292 ms |
| 29 days ago | Handshake completed | 320 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 23 responding of 31.
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.