Remote MCP · Endpoint

xyz.chain-ops/mgo MCP server

No. xyz.chain-ops/mgo answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.mgo.chain-ops.xyz/mcp

The last check completed an MCP handshake.

Registry name
xyz.chain-ops/mgo
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
73 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
Compare live gas across up to 9 EVM chains and get the cheapest one. x402 pay-per-call on Base.
Listing
From the official MCP registry (active).
Recent checks of xyz.chain-ops/mgo
CheckedResultHandshake
1 hour agoHandshake completed73 ms
1 day agoHandshake completed133 ms
2 days agoHandshake completed93 ms
3 days agoHandshake completed72 ms
4 days agoHandshake completed59 ms
5 days agoHandshake completed59 ms
6 days agoHandshake completed71 ms
8 days agoHandshake completed83 ms
11 days agoHandshake completed61 ms
13 days agoHandshake completed107 ms
15 days agoHandshake completed57 ms
18 days agoHandshake completed119 ms
20 days agoHandshake completed79 ms
22 days agoHandshake completed214 ms
24 days agoHandshake completed75 ms
26 days agoHandshake completed53 ms
27 days agoHandshake completed76 ms
29 days agoHandshake completed53 ms
29 days agoHandshake completed59 ms

The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.

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 xyz.chain-ops/mgo and makes no claim about it beyond what these checks measured.