Remote MCP · Endpoint

SwiftNodes RPC MCP server

No. SwiftNodes RPC answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

https://rpc.swiftnodes.io/mcp

The last check completed an MCP handshake.

Registry name
io.swiftnodes/swiftnodes
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
313 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Blockchain RPC for 125+ chains: endpoints, method support, probing and RPC calls with your key.
Listing
From the official MCP registry (active).
Recent checks of SwiftNodes RPC
CheckedResultHandshake
20 minutes agoHandshake completed313 ms
9 days agoHandshake completed303 ms
9 days agoHandshake completed281 ms
11 days agoHandshake completed301 ms
12 days agoHandshake completed282 ms
13 days agoHandshake completed291 ms
14 days agoHandshake completed349 ms
15 days agoHandshake completed292 ms
16 days agoHandshake completed337 ms
19 days agoHandshake completed305 ms
21 days agoHandshake completed438 ms
24 days agoHandshake completed433 ms
26 days agoHandshake completed297 ms
28 days agoHandshake completed533 ms

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

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