Remote MCP · Endpoint

Ankr Agent RPC MCP server

No. Ankr Agent RPC answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mcp.ankr.com/rpc

The last check completed an MCP handshake.

Registry name
io.github.w3tech/agent-rpc-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
307 ms
Tools exposed
25 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Read chain data on 200+ networks and Sui: transactions, logs, balances, objects, ABI-decoded.
Listing
From the official MCP registry (active).
Recent checks of Ankr Agent RPC
CheckedResultHandshake
2 hours agoHandshake completed307 ms
20 hours agoHandshake completed299 ms
2 days agoHandshake completed301 ms
4 days agoHandshake completed308 ms
6 days agoHandshake completed322 ms
9 days agoHandshake completed319 ms
11 days agoHandshake completed315 ms
13 days agoHandshake completed336 ms
15 days agoHandshake completed310 ms
17 days agoHandshake completed310 ms
19 days agoHandshake completed338 ms
21 days agoHandshake completed335 ms
23 days agoHandshake completed313 ms
24 days agoHandshake completed312 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 Ankr Agent RPC and makes no claim about it beyond what these checks measured.