MCP.Market

Solana Rpc MCP server

online · 100% uptime
by pipeworx-io·io.github.pipeworx-io/solana-rpc·v0.3.1

Solana RPC (keyless)

B73/100grade B
What users say
No reviews yet
Be the first
Safety scan
B73/100

not scanned yet

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Solana Rpc yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Solana Rpc tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Solana Rpc compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
73/100
higher than 38% of 48,243 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
171 ms
faster than 71% of 30,027 servers

Release history: 4 versions in the registry since 2026-09-11, latest 2026-11-05, typically one every 13 days.

Install Solana Rpc in Claude Code, Cursor or VS Code

claude mcp add --transport http solana-rpc https://gateway.pipeworx.io/solana-rpc/mcp
Add to Cursor

What the publisher says

From the Solana Rpc repository's README, as published. We do not edit it. Read it on GitHub

@pipeworx/solana-rpc

SPL token holdings, SOL balance and transaction history for any Solana address, and the top holders of any SPL token mint, read live from public Solana JSON-RPC endpoints — no API key.

Part of Pipeworx — an MCP gateway connecting AI agents to 1576+ live data sources.

Tools

a wallet holds: mint address, balance, decimals, token-account address, across both the SPL Token and Token-2022 programs. Zero balances dropped, sorted largest first, paginated.

  • solanawallettokens(wallet, limit?, offset?, minamount?, includezero?, program?) — every SPL token position

success/failure and memo, newest first; next_before pages further back.

  • solanawalletbalance(wallet) — native SOL balance in lamports and SOL, with the slot it was read at.
  • solanawallettransactions(wallet, limit?, before?, until?) — recent signatures with block time, slot,

types invoked, SOL balance changes, SPL token balances before and after, first log lines.

  • solana_transaction(signature) — one transaction summarised: fee, status, signers, programs and instruction

each with its owner wallet, token-account address, raw and decimal balance and percentage of total supply; plus the mint's supply, decimals and the share the returned holders control together. 20 holders from most endpoints, up to 100 where the node allows.

  • solanatokenholders(mint, limit?) — the largest token accounts of an SPL token mint, ranked by balance,

and you need to tell an endpoint block apart from an idle wallet.

  • solanarpchealth() — live per-endpoint, per-method reachability probe. Use it when a lookup comes back empty

Auth

Keyless.

Data sources

only keyless endpoint found that serves getTokenLargestAccounts; first in line for mint-level calls, last resort for wallet calls.

  • — Solana mainnet JSON-RPC operated by PublicNode/Allnodes.
  • — Solana mainnet JSON-RPC operated by LeoRPC (free shared key).
  • — Solana mainnet JSON-RPC operated by MagicBlock (public endpoint). The

Things worth knowing before you touch this

The endpoint that works on your laptop is not the endpoint that works in production. api.mainnet-beta.solana.com returns 200 locally and HTTP 403 "Your IP or provider is blocked from this endpoint" from a Cloudflare Worker. Twelve free RPC endpoints were probed from a deployed Worker; ankr, rpcpool and mainnet-beta 403, drpc 400s for a paid plan, blockeden 402, onfinality and omniatech 429, grove 1016, public-rpc 526, shyft 401. Two survived, and neither serves everything:

So failover is the architecture, not a safety net. Calls walk PROVIDERS in order, retry once on a transient failure, and skip a provider that refuses the method outright (-32601/-32602/-32000/403). A refusal is remembered per isolate so later calls go straight to the endpoint that serves it; a flake is not remembered, because flakes recover. Every response carries providers_tried with the outcome and latency of each hop, so a caller can see exactly where the answer came from.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Solana Rpc: common questions

Is Solana Rpc MCP server safe?
Mostly: it is graded B (73/100). Read the Solana Rpc safety report
How do I install Solana Rpc?
It runs remotely at gateway.pipeworx.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Solana Rpc need an API key?
Yes. The registry entry asks for PIPEWORX_API_KEY.
Is Solana Rpc maintained?
The last commit was 42 days ago (2026-09-25). The latest release is v0.3.1.
Is Solana Rpc up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Solana Rpc compare with other MCP servers?
safety score 73/100 (higher than 38% of 48,243 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 171 ms (faster than 71% of 30,027 servers). Full comparison.

More from pipeworx-io →