Remote MCP · Endpoint

ChainRay MCP server

No. ChainRay answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://chainray.online/mcp

The last check completed an MCP handshake.

Registry name
online.chainray/chainray
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
265 ms
Tools exposed
79 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Multi-chain on-chain intelligence for AI agents through a public remote MCP server.
Listing
From the official MCP registry (active).
Recent checks of ChainRay
CheckedResultHandshake
1 hour agoHandshake completed265 ms
3 days agoHandshake completed302 ms
13 days agoHandshake completed316 ms
14 days agoHandshake completed345 ms
15 days agoHandshake completed287 ms
16 days agoHandshake completed270 ms
18 days agoHandshake completed268 ms
18 days agoHandshake completed274 ms
19 days agoHandshake completed281 ms
21 days agoHandshake completed290 ms
22 days agoHandshake completed270 ms
25 days agoHandshake completed137 ms
27 days agoHandshake completed302 ms
30 days agoHandshake completed372 ms

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

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 ChainRay and makes no claim about it beyond what these checks measured.