Remote MCP · Endpoint
XGR MCP Gateway MCP server
No. XGR MCP Gateway answered an MCP handshake 3 hours ago.
UpLast checked 3 hours ago
Server URL
https://mcp.xgr.network/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.xgr-network/xdala-workflow-builder
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 386 ms
- Tools exposed
- 112 tools
- Uptime, last 30 days
- 100% from 14 checks
- Described by its publisher as
- Public Streamable HTTP MCP gateway for XGRChain, XDaLa sessions, Explorer data and XGR standards.
- Repository
- https://github.com/xgr-network/xgr-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 3 hours ago | Handshake completed | 386 ms |
| 9 days ago | Handshake completed | 351 ms |
| 10 days ago | Handshake completed | 357 ms |
| 11 days ago | Handshake completed | 360 ms |
| 12 days ago | Handshake completed | 336 ms |
| 14 days ago | Handshake completed | 349 ms |
| 14 days ago | Handshake completed | 365 ms |
| 15 days ago | Handshake completed | 327 ms |
| 17 days ago | Handshake completed | 350 ms |
| 19 days ago | Handshake completed | 343 ms |
| 21 days ago | Handshake completed | 352 ms |
| 24 days ago | Handshake completed | 347 ms |
| 26 days ago | Handshake completed | 346 ms |
| 28 days ago | Handshake completed | 345 ms |
The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 31 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 XGR MCP Gateway and makes no claim about it beyond what these checks measured.