Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Solana Rpc

NPM · @PIPEWORX/MCP-SOLANA-RPC · 2 COMPONENTS

Solana RPC (keyless)

+4 this week 84 Trust /100

Last scanned (8 hours ago)

Scores higher than 81% of npm servers

Category Crypto and Web3

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-solana-rpc). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 869 tokens (~144/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +1
    • Tool safety: pass → unverified ▼ security
    • Stability: 0.20 → unverified ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
    • Package version: 0.3.0 → 0.3.1 functional
  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Oct 26 +1
    • Security disclosure: unverified → fail ▼ functional
  • 29 Oct 26 80

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-solana-rpc@0.3.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-solana-rpc
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-solana-rpc/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3692354663
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:8d94c3cd2151026de41408172c63d3c8011d8bfd9c63a9e21a0e9776c8d0abf6a4dd10dc8d5f003476ca3da4b3fdedb0edd413a98320a29bcab57d848

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~813 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
solana_rpc_health ~88

Live reachability of each public Solana JSON-RPC endpoint this pack uses, per method: current slot, whether token-account scans are served, latency and the exact error text when one refuses. Answers "which Solana endpoint is answering right now, and for which calls" — useful when a wallet lookup comes back empty and you want to tell an endpoint block apart from an idle wallet.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

solana_token_holders ~210

Top holders of a Solana SPL token by mint address: the largest token accounts ranked by balance, each with its owner wallet address, token-account address, raw and decimal balance and percentage of total supply, plus the mint's total supply, decimals and the share the top holders control together. Answers "who are the biggest holders of this Solana token" and "how concentrated is its supply". Sourced live from public Solana JSON-RPC (getTokenLargestAccounts, getTokenSupply, getMultipleAccounts); up to 20 holders from most endpoints, up to 100 where the node allows.

NameTypeReqDescription
limitnumber–Holders to return, 1-100 (default 20; the RPC caps what it serves)
mintstringyesBase58 SPL token mint address (e.g. USDC EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v)

No output schema declared.

No examples provided.

solana_transaction ~93

Details of one Solana transaction by signature: block time, slot, fee, success or failure, signers, the programs and instruction types it invoked, SOL balance changes per account, and SPL token balances before and after. Answers "what did this Solana transaction actually do". Sourced live from public Solana JSON-RPC (getTransaction).

NameTypeReqDescription
signaturestringyesBase58 transaction signature (~88 chars)

No output schema declared.

No examples provided.

solana_wallet_balance ~75

Native SOL balance of a Solana address, in lamports and SOL, with the slot it was read at. Answers "how much SOL does this address hold". Sourced live from public Solana JSON-RPC (getBalance).

NameTypeReqDescription
walletstringyesBase58 Solana wallet address (32-44 chars)

No output schema declared.

No examples provided.

solana_wallet_tokens ~205

SPL token holdings of a Solana wallet: mint address, token balance, decimals and token-account address for every position, sorted largest first, covering both the SPL Token and Token-2022 programs. Answers "which tokens does this Solana address hold and how much of each". Sourced live from public Solana JSON-RPC (getTokenAccountsByOwner). Zero balances are dropped and results paginate, because a busy wallet can hold thousands of token accounts.

NameTypeReqDescription
include_zeroboolean–Include emptied token accounts (default false)
limitnumber–Holdings per page, 1-200 (default 25)
min_amountnumber–Keep only holdings at or above this token balance
offsetnumber–Page offset into the balance-sorted list (default 0)
programstring–Which token program to scan (default both)
walletstringyesBase58 Solana wallet address (32-44 chars)

No output schema declared.

No examples provided.

solana_wallet_transactions ~142

Recent transaction history for a Solana address: signature, slot, block time, success or failure, and memo for each transaction, newest first, with a cursor for paging further back. Answers "what has this Solana wallet done lately". Sourced live from public Solana JSON-RPC (getSignaturesForAddress).

NameTypeReqDescription
beforestring–Signature to page backwards from (from next_before)
limitnumber–Signatures to return, 1-100 (default 20)
untilstring–Stop when this signature is reached
walletstringyesBase58 Solana wallet address (32-44 chars)

No output schema declared.

No examples provided.

Install

How do I install the Solana Rpc MCP server?

Solana Rpc runs locally as an npm package, launched with npx -y @pipeworx/mcp-solana-rpc. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pipeworx/mcp-solana-rpc

# add to Claude Code
claude mcp add pipeworx-io-solana-rpc -- npx -y @pipeworx/mcp-solana-rpc
Common questions

What is the Solana Rpc MCP server?

Solana Rpc is an MCP server listed in the public MCP registry as io.github.pipeworx-io/solana-rpc. Solana RPC (keyless). This page covers its npm package (@pipeworx/mcp-solana-rpc).

Is the Solana Rpc MCP server safe to use?

Solana Rpc scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Solana Rpc MCP server expose?

Solana Rpc exposes 6 tools: solana_wallet_tokens, solana_wallet_balance, solana_wallet_transactions, solana_transaction, solana_token_holders, solana_rpc_health. Their descriptions and schemas cost roughly 813 tokens of context every time the server is loaded.

Is the Solana Rpc MCP server still maintained?

Solana Rpc is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Solana Rpc MCP server under?

Solana Rpc declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.