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
270 ms
Tools exposed
79 tools
Uptime, last 30 days
100% from 14 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 completed270 ms
2 days agoHandshake completed137 ms
5 days agoHandshake completed302 ms
7 days agoHandshake completed372 ms
9 days agoHandshake completed279 ms
11 days agoHandshake completed294 ms
13 days agoHandshake completed276 ms
15 days agoHandshake completed302 ms
17 days agoHandshake completed279 ms
18 days agoHandshake completed888 ms
20 days agoHandshake completed285 ms
21 days agoHandshake completed931 ms
23 days agoHandshake completed250 ms
25 days agoHandshake completed284 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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.