Remote MCP · Endpoint
FetchSandbox MCP server
No. FetchSandbox answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://fetchsandbox.com/mcp/v1
The last check completed an MCP handshake.
- Registry name
- io.github.fetchsandbox/mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 422 ms
- Tools exposed
- 8 tools
- Uptime, last 30 days
- 94.1% from 17 checks
- Described by its publisher as
- A deterministic verification engine for agents. Proves a fix: fails on the old code, passes on new.
- Website
- https://fetchsandbox.com/
- Repository
- https://github.com/fetchsandbox/mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 422 ms |
| 2 days ago | Handshake completed | 396 ms |
| 4 days ago | Handshake completed | 417 ms |
| 5 days ago | Handshake completed | 318 ms |
| 7 days ago | Handshake completed | 386 ms |
| 8 days ago | Handshake completed | 454 ms |
| 9 days ago | Failed - the server returned an HTTP error | — |
| 12 days ago | Handshake completed | 310 ms |
| 13 days ago | Handshake completed | 341 ms |
| 15 days ago | Handshake completed | 310 ms |
| 16 days ago | Handshake completed | 385 ms |
| 18 days ago | Handshake completed | 317 ms |
| 19 days ago | Handshake completed | 371 ms |
| 20 days ago | Handshake completed | 372 ms |
| 20 days ago | Handshake completed | 316 ms |
| 21 days ago | Handshake completed | 342 ms |
| 22 days ago | Handshake completed | 302 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 16 responding of 17.
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 FetchSandbox and makes no claim about it beyond what these checks measured.