Remote MCP · Endpoint

Solana Rpc MCP server

No. Solana Rpc answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/solana-rpc/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/solana-rpc
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.14 s
Tools exposed
50 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Solana RPC (keyless)
Listing
From the official MCP registry (active).
Recent checks of Solana Rpc
CheckedResultHandshake
1 hour agoHandshake completed1.14 s
1 day agoHandshake completed398 ms
2 days agoHandshake completed147 ms
3 days agoHandshake completed64 ms
4 days agoHandshake completed508 ms
5 days agoHandshake completed157 ms
6 days agoHandshake completed188 ms
9 days agoHandshake completed327 ms
12 days agoHandshake completed121 ms
14 days agoHandshake completed88 ms
16 days agoHandshake completed126 ms
18 days agoHandshake completed71 ms
21 days agoHandshake completed57 ms
23 days agoHandshake completed88 ms
25 days agoHandshake completed52 ms
26 days agoHandshake completed1.36 s
28 days agoHandshake completed1.98 s
29 days agoHandshake completed1.56 s

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 28 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.

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