Solscan
NPM · @PIPEWORX/MCP-SOLSCAN · 2 COMPONENTS
Solscan MCP — Solana block-explorer + network analytics
Available components
Last scanned (9 hours ago)
Scores higher than 76% 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 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-solscan). 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 Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1941 tokens (~149/item across 13 items; 13 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 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 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
- Security disclosure: unverified → fail ▼ functional
- Stability: unverified → 0.23 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 4 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 80
First indexed and scored.
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-solscan@0.2.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-solscan |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-solscan/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3692354850 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:f8dc301d9dcabf7f309f696f55386f4e755ec912c8a038bc34bdce768f197c43a69cb03a1df788c486aceb44080251c2b434df6559e8030761d05ea79 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
get_account_detail ~72
Overview of a Solana account: SOL balance (lamports + UI), owner program, executable flag, rent epoch. Pro tier — requires your own Solscan API key (Pipeworx's platform key is Free tier and cannot call this).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Solana public key (base58) |
No output schema declared.
No examples provided.
get_dex_activity ~162
Daily Solana DEX activity: trade count, distinct trader count, USD volume, and number of active DEX platforms. Free tier — covered by Pipeworx's own Solscan key, no caller key needed. Pass range OR from_date+to_date, not both.
| Name | Type | Req | Description |
|---|---|---|---|
| from_date | string | – | Start date, YYYYMMDD. Use together with to_date instead of range. |
| range | number | – | Lookback window in days: 30, 90, 180, or 365 (default 30). Ignored if from_date/to_date are given — the vendor rejects any other value with a 400. |
| to_date | string | – | End date, YYYYMMDD. Use together with from_date instead of range. |
No output schema declared.
No examples provided.
get_network_compute_units ~148
Daily total compute units consumed across the Solana network. Free tier — covered by Pipeworx's own Solscan key, no caller key needed. Pass range OR from_date+to_date, not both.
| Name | Type | Req | Description |
|---|---|---|---|
| from_date | string | – | Start date, YYYYMMDD. Use together with to_date instead of range. |
| range | number | – | Lookback window in days: 30, 90, 180, or 365 (default 30). Ignored if from_date/to_date are given — the vendor rejects any other value with a 400. |
| to_date | string | – | End date, YYYYMMDD. Use together with from_date instead of range. |
No output schema declared.
No examples provided.
get_network_fees ~159
Daily Solana network fees: base fee and priority fee, each in SOL and USD, plus their total. Free tier — covered by Pipeworx's own Solscan key, no caller key needed. Pass range OR from_date+to_date, not both.
| Name | Type | Req | Description |
|---|---|---|---|
| from_date | string | – | Start date, YYYYMMDD. Use together with to_date instead of range. |
| range | number | – | Lookback window in days: 30, 90, 180, or 365 (default 30). Ignored if from_date/to_date are given — the vendor rejects any other value with a 400. |
| to_date | string | – | End date, YYYYMMDD. Use together with from_date instead of range. |
No output schema declared.
No examples provided.
get_network_slots ~147
Daily count of Solana blocks (slots) produced. Free tier — covered by Pipeworx's own Solscan key, no caller key needed. Pass range OR from_date+to_date, not both.
| Name | Type | Req | Description |
|---|---|---|---|
| from_date | string | – | Start date, YYYYMMDD. Use together with to_date instead of range. |
| range | number | – | Lookback window in days: 30, 90, 180, or 365 (default 30). Ignored if from_date/to_date are given — the vendor rejects any other value with a 400. |
| to_date | string | – | End date, YYYYMMDD. Use together with from_date instead of range. |
No output schema declared.
No examples provided.
get_network_stake ~152
Daily total active stake on the Solana network, in SOL and USD. Free tier — covered by Pipeworx's own Solscan key, no caller key needed. Pass range OR from_date+to_date, not both.
| Name | Type | Req | Description |
|---|---|---|---|
| from_date | string | – | Start date, YYYYMMDD. Use together with to_date instead of range. |
| range | number | – | Lookback window in days: 30, 90, 180, or 365 (default 30). Ignored if from_date/to_date are given — the vendor rejects any other value with a 400. |
| to_date | string | – | End date, YYYYMMDD. Use together with from_date instead of range. |
No output schema declared.
No examples provided.
get_network_transactions ~157
Daily Solana network transaction counts: total, vote, and non-vote (split success/fail). Free tier — covered by Pipeworx's own Solscan key, no caller key needed. Pass range OR from_date+to_date, not both.
| Name | Type | Req | Description |
|---|---|---|---|
| from_date | string | – | Start date, YYYYMMDD. Use together with to_date instead of range. |
| range | number | – | Lookback window in days: 30, 90, 180, or 365 (default 30). Ignored if from_date/to_date are given — the vendor rejects any other value with a 400. |
| to_date | string | – | End date, YYYYMMDD. Use together with from_date instead of range. |
No output schema declared.
No examples provided.
get_ohlcv ~254
OHLCV price candles for a Solana liquidity pool (1-minute to 1-year buckets, cursor-paged). Announced by Solscan 2026-10-07; Pipeworx has not been able to verify the exact response shape because this is a Pro-tier-only endpoint and Pipeworx has no Pro-tier key — pass whatever extra query parameters Solscan's own docs specify via extra_params if the named fields below are not enough. Pro tier — requires your own Solscan API key (Pipeworx's platform key is Free tier and cannot call this).
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Pagination cursor from a previous response |
| extra_params | object | – | Any additional query parameters Solscan's docs name that are not covered above — forwarded verbatim. |
| pool_address | string | yes | Solana liquidity pool address (base58) |
| time_bucket | string | – | Candle size, e.g. "1m", "1H", "1D", "1W" — Solscan supports 1 minute to 1 year. |
| time_from | number | – | Unix timestamp (seconds), start of range |
| time_to | number | – | Unix timestamp (seconds), end of range |
No output schema declared.
No examples provided.
get_token_holdings ~103
SPL-token balances held by a Solana account. Returns mint, symbol, amount, decimals, USD value (if known). Pro tier — requires your own Solscan API key (Pipeworx's platform key is Free tier and cannot call this).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Solana account public key |
| page | number | – | 1-based page (default 1) |
| page_size | number | – | 1-40 (default 20) |
No output schema declared.
No examples provided.
get_token_meta ~71
Metadata for an SPL token mint: name, symbol, decimals, supply, icon, market cap, holders, social links. Pro tier — requires your own Solscan API key (Pipeworx's platform key is Free tier and cannot call this).
| Name | Type | Req | Description |
|---|---|---|---|
| token_address | string | yes | SPL token mint address |
No output schema declared.
No examples provided.
get_token_screener ~274
Solscan's Token List V2 screener — sorts/filters tokens over 170+ metric fields across nine time windows. Announced by Solscan 2026-10-07; Pipeworx has not been able to verify the full field list because this is a Pro-tier-only endpoint and Pipeworx has no Pro-tier key — pass any filter/window parameter from Solscan's own docs via extra_params. Pro tier — requires your own Solscan API key (Pipeworx's platform key is Free tier and cannot call this).
| Name | Type | Req | Description |
|---|---|---|---|
| extra_params | object | – | Any additional screener filter Solscan's docs name that is not covered above — forwarded verbatim. |
| page | number | – | 1-based page (default 1) |
| page_size | number | – | Items per page |
| sort_by | string | – | Metric field to sort by, e.g. "market_cap", "holder", "created_time" (v1 values; v2 adds many more per Solscan's announcement). |
| sort_order | string | – | Sort direction |
| time_window | string | – | One of Solscan's nine screener time windows, e.g. "1h", "24h", "7d" — exact set not published as of 2026-10-07. |
No output schema declared.
No examples provided.
get_transaction ~85
Fetch a Solana transaction by base58 signature. Returns status (Success/Fail), slot, block time, fee in lamports, SOL balance changes per account, and parsed instruction list. Pro tier — requires your own Solscan API key (Pipeworx's platform key is Free tier and cannot call this).
| Name | Type | Req | Description |
|---|---|---|---|
| signature | string | yes | Solana transaction signature (base58) |
No output schema declared.
No examples provided.
list_transfers ~105
Recent SOL and SPL token transfers for an account. Returns signature, timestamp, side (sent/received), token, amount, counterparty. Pro tier — requires your own Solscan API key (Pipeworx's platform key is Free tier and cannot call this).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Solana account public key |
| page | number | – | 1-based page (default 1) |
| page_size | number | – | 1-40 (default 20) |
No output schema declared.
No examples provided.
How do I install the Solscan MCP server?
Solscan runs locally as an npm package, launched with npx -y @pipeworx/mcp-solscan. 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-solscan
claude mcp add pipeworx-io-solscan -- npx -y @pipeworx/mcp-solscan
What is the Solscan MCP server?
Solscan is an MCP server listed in the public MCP registry as io.github.pipeworx-io/solscan. Solscan MCP, Solana block-explorer + network analytics. This page covers its npm package (@pipeworx/mcp-solscan).
Is the Solscan MCP server safe to use?
Solscan scores 83 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 Solscan MCP server expose?
Solscan exposes 13 tools: get_account_detail, get_token_holdings, list_transfers, get_token_meta, get_transaction, and 8 more. Their descriptions and schemas cost roughly 1,889 tokens of context every time the server is loaded.
Is the Solscan MCP server still maintained?
Solscan 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 Solscan MCP server under?
Solscan declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.