Remote MCP · Endpoint
Imagio Relay MCP server
No. Imagio Relay answered an MCP handshake 3 hours ago.
UpLast checked 3 hours ago
Server URL
https://relay.imagiolabs.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.imagiolabs.www/imagio-relay
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-03-26
- Handshake latency
- 84 ms
- Tools exposed
- 139 tools
- Uptime, last 30 days
- 100% from 11 checks
- Described by its publisher as
- 57 deterministic web-intel, trade and infra tools for agents. USDC per call via x402.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 3 hours ago | Handshake completed | 84 ms |
| 4 days ago | Handshake completed | 384 ms |
| 14 days ago | Handshake completed | 90 ms |
| 15 days ago | Handshake completed | 104 ms |
| 15 days ago | Handshake completed | 73 ms |
| 17 days ago | Handshake completed | 51 ms |
| 18 days ago | Handshake completed | 63 ms |
| 19 days ago | Handshake completed | 71 ms |
| 20 days ago | Handshake completed | 65 ms |
| 21 days ago | Handshake completed | 62 ms |
| 23 days ago | Handshake completed | 93 ms |
The last 11 checks. Full history is kept for 30 days; the all-time counter stands at 11 responding of 11.
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 Imagio Relay and makes no claim about it beyond what these checks measured.