Remote MCP · Endpoint

OpenNodes MCP server

No. OpenNodes answered an MCP handshake 52 minutes ago.

UpLast checked 52 minutes ago

Server URL

https://registry.opennodes.io/mcp

The last check completed an MCP handshake.

Registry name
io.github.opennodes-io/opennodes
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
324 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Discover verified AI inference nodes, get the best node+model per task, pre-price chains.
Listing
From the official MCP registry (active).
Recent checks of OpenNodes
CheckedResultHandshake
52 minutes agoHandshake completed324 ms
3 days agoHandshake completed301 ms
12 days agoHandshake completed476 ms
13 days agoHandshake completed290 ms
14 days agoHandshake completed589 ms
15 days agoHandshake completed598 ms
17 days agoHandshake completed299 ms
18 days agoHandshake completed298 ms
18 days agoHandshake completed311 ms
20 days agoHandshake completed312 ms
22 days agoHandshake completed292 ms
25 days agoHandshake completed478 ms
27 days agoHandshake completed307 ms
29 days agoHandshake completed300 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.

Listing data comes from the official MCP registry. Glide is not affiliated with OpenNodes and makes no claim about it beyond what these checks measured.