Remote MCP · Endpoint

xRocket Exchange MCP MCP server

No. xRocket Exchange MCP answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://xrocket-mcp-production.up.railway.app/mcp

The last check completed an MCP handshake.

Registry name
io.github.nakazanie-ton/xrocket
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
128 ms
Tools exposed
10 tools
Uptime, last 30 days
77.8% from 18 checks
Described by its publisher as
Autonomous xRocket CEX trading inside operator-set limits, plus live market data over MCP
Listing
From the official MCP registry (active).
Recent checks of xRocket Exchange MCP
CheckedResultHandshake
1 hour agoHandshake completed128 ms
1 day agoHandshake completed128 ms
2 days agoHandshake completed116 ms
3 days agoHandshake completed132 ms
4 days agoHandshake completed131 ms
5 days agoHandshake completed261 ms
6 days agoHandshake completed120 ms
9 days agoHandshake completed125 ms
11 days agoHandshake completed111 ms
14 days agoFailed - the server returned an HTTP error—
16 days agoFailed - the server returned an HTTP error—
18 days agoFailed - the server returned an HTTP error—
20 days agoFailed - the server returned an HTTP error—
22 days agoHandshake completed142 ms
24 days agoHandshake completed135 ms
26 days agoHandshake completed115 ms
27 days agoHandshake completed134 ms
29 days agoHandshake completed141 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 25 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 xRocket Exchange MCP and makes no claim about it beyond what these checks measured.