Nansen
NPM · @PIPEWORX/MCP-NANSEN · 2 COMPONENTS
Nansen Smart Money MCP — on-chain smart-money labels & flows (nansen.ai)
Available components
Last scanned (19 hours ago)
Scores higher than 72% 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-nansen). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 611 tokens (~203/item across 3 items; 3 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 Management20
- Stability observed for 6 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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.
- 4 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 −12
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.17 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 79
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 4 Nov 2026 · Analysed npm/@pipeworx/mcp-nansen@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-nansen |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-nansen/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3655611131 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:d2e178a3641beed1b6f5492a4063555f5c8ac2d36eb9f2a80bd0d1aa140d016f720374b62c183960d382b504ee6f6a07794970326be901eb4cc92181a |
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 →
nansen_smart_money_holdings ~161
What does smart money hold on chain X — returns tokens currently held by Nansen "Smart Money" wallets on a chain, ranked by USD value held, with holder counts and 24h balance change. Example: nansen_smart_money_holdings({ chain: "ethereum", _apiKey: "your-nansen-key" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Nansen API key from your nansen.ai account (paid — $10/10k credits PAYG). |
| chain | string | – | Chain to query (default "ethereum"), e.g. "ethereum", "solana", "base", "arbitrum". |
| limit | integer | – | Max tokens to return (default 20, max 50). |
No output schema declared.
No examples provided.
nansen_smart_money_netflow ~215
What is smart money buying or selling (net flow) on chain X — returns tokens ranked by net USD flow from Nansen "Smart Money" wallets (top traders + funds) over a time window. Positive = accumulation, negative = distribution. Example: nansen_smart_money_netflow({ chain: "ethereum", timeframe: "1d", _apiKey: "your-nansen-key" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Nansen API key from your nansen.ai account (paid — $10/10k credits PAYG). |
| chain | string | – | Chain to query (default "ethereum"), e.g. "ethereum", "solana", "base", "arbitrum". |
| limit | integer | – | Max tokens to return (default 20, max 50). |
| timeframe | string | – | Net-flow window to rank/surface: "1h", "1d" (=24h), "7d", or "30d". Default "1d". |
No output schema declared.
No examples provided.
nansen_wallet_profiler ~183
Labels & profile for wallet X — returns Nansen labels (e.g. "Smart Money", "Fund", exchange/entity tags) for a wallet address, plus a best-effort USD balance summary. Example: nansen_wallet_profiler({ address: "0x28c6c06298d514db089934071355e5743bf21d60", chain: "ethereum", _apiKey: "your-nansen-key" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Nansen API key from your nansen.ai account (paid — $10/10k credits PAYG). |
| address | string | yes | Wallet address to profile (required), e.g. "0x28c6...d60". |
| chain | string | – | Chain the address lives on (default "ethereum"); use "all" to span chains where supported. |
No output schema declared.
No examples provided.
How do I install the Nansen MCP server?
Nansen runs locally as an npm package, launched with npx -y @pipeworx/mcp-nansen. 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-nansen
claude mcp add pipeworx-io-nansen -- npx -y @pipeworx/mcp-nansen
What is the Nansen MCP server?
Nansen is an MCP server listed in the public MCP registry as io.github.pipeworx-io/nansen. Nansen Smart Money MCP, on-chain smart-money labels & flows (nansen.ai). This page covers its npm package (@pipeworx/mcp-nansen).
Is the Nansen MCP server safe to use?
Nansen scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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 Nansen MCP server expose?
Nansen exposes 3 tools: nansen_smart_money_netflow, nansen_smart_money_holdings, nansen_wallet_profiler. Their descriptions and schemas cost roughly 559 tokens of context every time the server is loaded.
Is the Nansen MCP server still maintained?
Nansen is still listed as active in the MCP registry. We last reached this channel on 4 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 Nansen MCP server under?
Nansen declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.