io.github.sylenzor/solana-mcp
NPM · @RIGEL-PROTOCOL/SOLANA-MCP
Read-only Solana MCP: rug-risk, bundle & deployer checks, live market, full audit. No keys.
Available components
Last scanned (5 hours ago)
Scores higher than 55% of npm servers
Category Crypto and Web3
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 48 of 148 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 85 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 469 tokens (~67/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 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 7 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
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 −3
- Stability: pass → 0.80 functional
- 30 Oct 26 0
- Stability: 0.97 → pass security
- 29 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 −3
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. security
- 23 Oct 26 +1
- Stability: 0.97 → pass security
- 22 Oct 26 −1
- Stability: pass → 0.97 functional
- 16 Oct 26 +1
- Stability: 0.97 → pass security
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
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/@rigel-protocol/solana-mcp@1.2.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 5 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-528h-pc64-c93x | CVE-2026-71429 | medium | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-hqr4-qq8f-hg3x | CVE-2026-104182 | medium | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-mjw6-4jj6-33hc | CVE-2026-104183 | medium | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L | yes |
| GHSA-w5hq-g745-h8pq | CVE-2026-41907 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N | yes |
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 148 packages
| Packages resolved | 148 |
|---|---|
| Deprecated | 1 |
| Stale | 47 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
rigel_analyze_rug_risk Analyze rug risk ~66
Check basic on-chain safety metrics for a token — mint/freeze authority status and top-holder concentration — and return a formatted risk report. On-chain facts, not financial advice.
| Name | Type | Req | Description |
|---|---|---|---|
| tokenAddress | string | yes | Base58 mint address of the token to analyze |
No output schema declared.
No examples provided.
rigel_check_first_buyers Check first buyers (bundle detection) ~76
Forensic check of a token's top holders: how many are fresh wallets, whether several share the same funding wallet, and how much supply fresh wallets control. Flags likely bundled launches. Heuristic, read-only, not financial advice.
| Name | Type | Req | Description |
|---|---|---|---|
| tokenAddress | string | yes | Base58 mint address of the token to check |
No output schema declared.
No examples provided.
rigel_deployer_history Deployer rap sheet ~71
Identify who deployed a token and profile that wallet: age, activity level, SOL balance, and whether they still hold a meaningful share of the supply. Heuristic, read-only, not financial advice.
| Name | Type | Req | Description |
|---|---|---|---|
| tokenAddress | string | yes | Base58 mint address of the token whose deployer to profile |
No output schema declared.
No examples provided.
rigel_full_audit Full audit ~74
The complete Rigel battery in one call: safety, bundle forensics, deployer profile, curve state, and live market — combined into a single report with an overall verdict and top reasons. Read-only, not financial advice.
| Name | Type | Req | Description |
|---|---|---|---|
| tokenAddress | string | yes | Base58 mint address of the token to audit |
No output schema declared.
No examples provided.
rigel_get_wallet_balance Get wallet balance ~50
Get the SOL balance and a summary of major SPL token holdings for any public Solana wallet address. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| walletAddress | string | yes | Base58 Solana wallet address to inspect |
No output schema declared.
No examples provided.
rigel_inspect_token_data Inspect token data ~56
Fetch metadata, supply stats, bonding-curve SOL, and estimated curve-completion percentage for a pump.fun token mint. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| tokenAddress | string | yes | Base58 mint address of the token to inspect |
No output schema declared.
No examples provided.
rigel_market_snapshot Market snapshot ~76
Live market state for a token: price, market cap, liquidity, volume, buys-vs-sells flow, and momentum read (surging / steady / bleeding out). Works for bonding-curve and graduated tokens. Read-only, not financial advice.
| Name | Type | Req | Description |
|---|---|---|---|
| tokenAddress | string | yes | Base58 mint address of the token |
No output schema declared.
No examples provided.
How do I install the io.github.sylenzor/solana-mcp server?
io.github.sylenzor/solana-mcp runs locally as an npm package, launched with npx -y @rigel-protocol/solana-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @rigel-protocol/solana-mcp
claude mcp add sylenzor-solana-mcp -- npx -y @rigel-protocol/solana-mcp
What is the io.github.sylenzor/solana-mcp server?
io.github.sylenzor/solana-mcp is listed in the public MCP registry as io.github.sylenzor/solana-mcp. Read-only Solana MCP: rug-risk, bundle & deployer checks, live market, full audit. No keys. This page covers its npm package (@rigel-protocol/solana-mcp).
Is the io.github.sylenzor/solana-mcp server safe to use?
io.github.sylenzor/solana-mcp scores 77 out of 100 on VerifyMCP. We recorded 5 known advisories against it as of 5 November 2026. It declares no install or post-install scripts. 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 io.github.sylenzor/solana-mcp server expose?
io.github.sylenzor/solana-mcp exposes 7 tools: rigel_get_wallet_balance, rigel_inspect_token_data, rigel_analyze_rug_risk, rigel_check_first_buyers, rigel_deployer_history, and 2 more. Their descriptions and schemas cost roughly 469 tokens of context every time the server is loaded.
Is the io.github.sylenzor/solana-mcp server still maintained?
io.github.sylenzor/solana-mcp 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 io.github.sylenzor/solana-mcp server under?
io.github.sylenzor/solana-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.