Remote MCP · Endpoint

io.chainhelix/intel MCP server

No. io.chainhelix/intel answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.chainhelix.io/

The last check completed an MCP handshake.

Registry name
io.chainhelix/intel
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
331 ms
Tools exposed
82 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Nine chain onchain intelligence with a verifiable onchain signal attestation stream
Website
https://chainhelix.io/
Listing
From the official MCP registry (active).
Recent checks of io.chainhelix/intel
CheckedResultHandshake
1 hour agoHandshake completed331 ms
1 day agoHandshake completed330 ms
2 days agoHandshake completed336 ms
3 days agoHandshake completed330 ms
4 days agoHandshake completed339 ms
5 days agoHandshake completed334 ms
6 days agoHandshake completed446 ms
9 days agoHandshake completed333 ms
11 days agoHandshake completed441 ms
14 days agoHandshake completed336 ms
16 days agoHandshake completed337 ms
18 days agoHandshake completed341 ms
20 days agoHandshake completed334 ms
22 days agoHandshake completed330 ms
24 days agoHandshake completed338 ms
26 days agoHandshake completed335 ms
27 days agoHandshake completed355 ms
28 days agoHandshake completed326 ms

The last 18 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.

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