Remote MCP · Endpoint

NEARpedia MCP server

No. NEARpedia answered an MCP handshake 49 minutes ago.

UpLast checked 49 minutes ago

Server URL

https://near-pedia.xyz/mcp

The last check completed an MCP handshake.

Registry name
io.github.UnityNodes/near-pedia
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
507 ms
Tools exposed
27 tools
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
Live NEAR knowledge for agents: deprecations, breaking changes, protocol and contracts, dated
Listing
From the official MCP registry (active).
Recent checks of NEARpedia
CheckedResultHandshake
49 minutes agoHandshake completed507 ms
10 days agoHandshake completed566 ms
10 days agoHandshake completed526 ms

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

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