Nansen MCP
Official Nansen MCP exposing smart-money and wallet-labeling data across 25+ chains.
- Sato Score67
- ChainsMultichain
Nansen MCP is a MCP server by Nansen, with no code activity tracked. Sato Score 67/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-15. How the score works →
See how to install Nansen MCP →No code activity tracked
Listed from nansen.ai on 2026-07-13. Install: not attempted. Evidence →
Next step
Watch Nansen MCP
One email if what we observe changes — its endpoint stops answering, or the listing is retired. Nothing else.
Check it from your agent
Add Sato Hub’s MCP server (no key), then ask:
https://satohub.ai/api/mcpRun Sato Hub Preflight on https://mcp.nansen.ai/ra/mcp before I use it.Your project?
Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.
Claim this listing →Overview
Nansen MCP is Nansen's official Model Context Protocol server, giving agents access to its wallet-labeling database, smart-money trade tracking, token intelligence, and PnL/trading-pattern data across 25+ blockchains including Ethereum, Solana, and Base. A builder wires it in for wallet-profiling or smart-money-following agent workflows with one-click Claude Desktop install.
Sato Score
67/100· MediumHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 35/35
- Code transparency
- 0/20
- Interface verifiability
- 10/10
- Docs & demo
- 6/10
- Listing transparency & provenance
- 9/15
- Independent verification
- 7/10
Live endpoint probed — we called the hosted MCP endpoint and it answered with its real tool inventory (proves the interface works, not runtime safety).
Evidence — listed vs checked · what the words mean
Listed from nansen.ai on 2026-07-13. Install: not attempted.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | Multichain | self-reported | docs.nansen.ai | as of 2026-10-15 |
| Verification status | Self-Reported — not independently reviewed | self-reported | nansen.ai | as of 2026-10-15 |
| Install works | documented by the project, not run by Sato Hubnot attempted by Sato Hub | self-reported | docs.nansen.ai | as of 2026-07-20 |
| MCP endpoint answers | answered — 50 tools listed | observed | mcp.nansen.ai | 2026-10-15 |
| Daily check record | 90 of 90 daily checks since 2026-07-17 succeededa success rate of our checks, not uptime; the source is this listing's own history | observed | — | 2026-10-14 |
| ERC-8004 registration | declared address not found in the registry | observed | — | 2026-10-15 |
| Works with | Claude, Claude Desktop, Cursorconfidence 0.85 | self-reported | docs.nansen.ai | as of 2026-07-14 |
| Sato Score | 67/100 (Medium)how open, active and verifiable — not a safety or quality grade | computed | satohub.ai | 2026-10-15 |
Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.
Install — as documented by the project, not run by us
Runtime: Hosted MCP endpoint (no local install)
claude mcp add --transport http nansen https://mcp.nansen.ai/ra/mcp --header "NANSEN-API-KEY: YOUR_API_KEY_HERE"
{"mcpServers": {"nansen-mcp": {"command": "npx", "args": ["-y", "mcp-remote", "https://mcp.nansen.ai/ra/mcp", "--header", "NANSEN-API-KEY: ", "--allow-http"]}}}You supply: Nansen API key (NANSEN-API-KEY header; from app.nansen.ai/api?tab=api)
claude mcp add --transport http satohub-nansen-mcp https://mcp.nansen.ai/ra/mcp
A remote server: your client connects to the project's endpoint. Installing runs third-party software under your own credentials. Sato Hub publishes the documented invocation and, where the harness reproduced it, the date it did — neither is a safety review.
Read from the project’s own docs as of 2026-07-20. What a deploy spec is →
Tool inventory — 50 tools, probed live 2026-10-15
smart_traders_and_funds_token_balances— Get aggregated (not per wallet) smart trader and fund (EXCLUDES whales, large holders, influencers, etc.) token balances and 24h change per chain for all chains (default is ['all'], which queries allsmart_traders_and_funds_perp_trades— Get recent Hyperliquid perpetual futures trades from Smart Money addresses across all tokens. Optional labels narrow this cohort; they do not search all addresses with that label. For a broad view ofsmart_traders_and_funds_netflow— Get aggregated (not per wallet) smart trader and fund (EXCLUDES whales, large holders, influencers, etc.) net USD flow per token over 1h/24h/7d/30d, per chain for all chains (default is ['all']) or spsmart_traders_and_funds_dex_trades— Get individual (per wallet, per transaction) DEX trades made by smart traders and funds (EXCLUDES whales, large holders, influencers, etc.) across all chains (default is ['all']) or specific chain(s).smart_traders_and_funds_dcas— Get Jupiter DCA (dollar-cost-averaging) orders opened by smart traders and funds on Solana, including deposit size, amount spent so far and order status. Use this for scheduled accumulation intent; ussmart_traders_and_funds_historical_token_balances— Get the day-by-day history of aggregated smart trader and fund token balances (EXCLUDES whales, large holders, influencers, etc.) for a date range on base, bnb, ethereum, monad, robinhood or solana. Usmart_traders_and_funds_pnl_leaderboard— Rank smart trader and fund addresses (EXCLUDES whales, large holders, influencers, etc.) by realized, unrealized and total USD PnL over a 1/7/30/90/180 day window, with ROI, win rate and trade counts.token_current_top_holders— Get upto 25 (per page) top holders information for a specific token. **Note:** Using `labelType: smart_money` is not a good proxy for an overall market view. Use it only if user explicitly requests itoken_dex_trades— Get DEX trades for a specific token. **Modes:** - `onchain_tokens` (default): Analyze on-chain tokens by contract address - `perps`: Analyze Hyperliquid perpetual futures by symbol (chain auto-set totoken_transfers— Get 25 token transfers (per page) for a specific token based on the sort order. Default: the last 24 hours, largest transfers first (orderBy "amount", "desc"). Direction rules (fromAddress = the sendtoken_flows— Get hourly token-flow history for ONE holder segment over a date range. Use `token_recent_flows_summary` instead for an on-chain snapshot across ALL wallet categories. **Note:** Using `holder_segmenttoken_pnl_leaderboard— Upto 25 results (per page) of trader PnL for a token. Use the sorting and filtering options to narrow down the results. **Modes:** - `onchain_tokens` (default): Analyze on-chain tokens by contract adtoken_who_bought_sold— Get TOTAL amount of tokens bought/sold by address for a token on DEX (Decentralised Exchanges) ONLY. Use this tool to find out WHO is buying or selling a token (on DEX) AND then you can check if theytoken_recent_flows_summary— Get an on-chain flow snapshot across **ALL** wallet categories in one call. This tool supports native ETH on Ethereum and native SOL on Solana, and is the correct choice for standard lookbacks such astoken_discovery_screener— Get comprehensive token screening data across multiple blockchain networks with advanced filtering. A maximum of 25 results per page are returned out of 1000s of tokens. Use the sorting and filteringtoken_ohlcv— Get OHLCV (Open, High, Low, Close, Volume) price data for a token with automatic interval resolution. Supports EVM chains and Solana for on-chain tokens, AND Hyperliquid perpetual futures. For Hyperltoken_technical_indicators— Get a technical-analysis snapshot for a token: SMA(20/50/200), EMA(12/26), RSI(14), MACD(12,26,9), Bollinger Bands(20, 2σ), ATR(14), and rolling VWAP(20), computed from the last 260 closed candles attoken_info— Get token information — spot on-chain details or Hyperliquid perpetual futures stats. On-chain tokens mode (default): Returns token details (name, symbol, market cap, FDV, supply, deployment date, sotoken_quant_scores— Get Nansen Score Indicators for a token - quantitative risk and reward signals. Use this tool when assessing a token's risk/reward profile, evaluating buy/sell decisions, or when the user needs quantnansen_score_top_tokens— Discover and filter a daily list of attractive tokens using Nansen Score Indicators weighted by coefficients (= Performance Score). Use this tool when you don't know which tokens to buy and need recohyperliquid_leaderboard— Get Hyperliquid perpetual futures trader leaderboard with performance metrics. Returns: Trader performance rankings as markdown. Columns returned: - **Address** / **Label**: trader walletoken_jup_dca— Get Jupiter DCA (dollar-cost-averaging) orders opened against a Solana token, with deposit size, amount spent so far, amount accumulated and order status. Use this to see scheduled buying or selling paddress_historical_balances— Get historical native coin & token balances of address.address_labels— Get the standard labels for one wallet address. This tool returns identity, behavioural, and protocol labels. It does not return premium labels.address_related_addresses— Get information about related addresses of an input address. Note: This only includes the the "special" connections 'First Funder', 'Signer', 'Previous Signer', 'Multisig Signer of', 'Previous Multisaddress_counterparties— Get 25 (per page) addresses or entities with the most common interactions with input addresses Default sort is net value transferred between them. Also returns the top 3 tokens transferred by count foaddress_counterparties_batch— Get the top counterparties of up to 10 wallet addresses in one call. Every wallet gets its own counterparty list. The lists are NOT added together: the answer has one table for each wallet. Use thisaddress_transactions— Get list of 20 MOST RECENT transactions made by an address (per page). Only the latest transactions according to the date range are returned.address_dex_trades— Get a wallet's individual trades on a single chain — DEX swaps (spot) or Hyperliquid perpetual trades, newest first. Wallet-centric companion to `token_dex_trades` (which is token-centric). Chain: onaddress_perp_positions— Get a wallet's Hyperliquid positions and liquidation risk without a portfolio lookup.wallet_pnl_for_token— Get PnL stats for a specific token traded by the input address during a specific date range. Use this tool for analysing the performance of the wallet for the specific token over a time period. Chainwallet_pnl_summary— Get aggregate stats of overall realized PnL for the input address. For Hyperliquid perp traders (chain='hyperliquid'), includes realized PnL from fills plus a current unrealized snapshot of open positaddress_first_funder— Get the first address that ever funded an EVM wallet, with the funding transaction hash, chain and timestamp. Use this to attribute an unlabelled wallet to a known entity — the first funder is often aaddress_portfolio— Get comprehensive portfolio overview for a wallet address or entity. Hyperliquid perpetual positions include liquidation prices to support risk analysis workflows. For wallet addresses, supports difgeneral_search— General search tool. This is your FIRST entry point to look up for possible tokens, entities, and addresses related to a query. Do NOT use this tool for prediction markets. For Polymarket names, topientity_name_search— Search Nansen's entity names by a partial name and get back the exact entity names that match. Use this when a tool needs an exact entity name and the user gave an approximate one (e.g. "binance" -> "token_sectors— List valid token sectors for token discovery filters.growth_chain_rank— Get chain growth rankings by active addresses, transactions, gas fees and DEX volume.transaction_lookup— Get comprehensive transaction details including token transfers.prediction_market_lookup— Search Polymarket for events and markets by name, topic, URL, or slug. **PM building blocks:** - An **event** is a grouped prediction topic containing many child markets. - A **market** is one tradabprediction_market_screener— Browse and sort Polymarket markets, events, or categories. **When to use:** - Broad discovery, screening, and ranked browsing across many markets. - Do NOT use this to resolve one named market/event/prediction_market_ohlcv— Historical odds/volume candles for a Polymarket market. **When to use:** - Current odds / implied probability, price history, and recent probability changes on a specific market. **Key fields:** -prediction_market_orderbook— Live orderbook for a Polymarket market. **When to use:** - Bid/ask depth, liquidity, and yes-share / no-share order structure. **Key fields:** - `Order Size` is share quantity, not USD. Do not descrprediction_market_top_holders— Largest current holders for a Polymarket market. **Key fields:** - Positions are share balances, not USD notional. - `Position Value USD` is current marked value, not payout at resolution. - `Side Heprediction_market_trades— Recent trades for a Polymarket market. **When to use:** - Source of truth for recent fills and latest trade-tape pricing. - Do not overwrite recent trade prices with older OHLCV candles. **Key fieldprediction_market_pnl_leaderboard— PnL leaderboard for a Polymarket market. **When to use:** - Only for profitability claims. **Key fields:** - `Total PnL USD` = redemption + unrealized value + sell proceeds − buy cost, for this maprediction_market_position_detail— Detailed position breakdown for a Polymarket market. **Key fields:** - `Position Size (Shares)` is the share quantity still held. - `Buy Cost USD` and `Sell Proceeds USD` are the cash paid and receivprediction_market_address_trades— Prediction market trade history for a Polygon wallet. **Key fields:** - `Share Size` is quantity traded in the displayed outcome side. - `Value USD` applies to that row only, not the whole transactioprediction_market_address_summary— Prediction market summary metrics for a Polygon wallet. **When to use:** - First wallet-level Polymarket tool for a quick trader overview. - Use before detailed address trades/PnL when the user asksprediction_market_address_pnl— Prediction market PnL breakdown for a Polygon wallet, market by market. **When to use:** - Wallet-level Polymarket track record with per-market cost and proceeds. **Key fields:** - `Total PnL USD` =
- Answers a handshake
- yes · 2026-10-15
- Answers a call
- not asked — no tool is named as a read (list_/get_/search_)
Live probe verifies the interface responds — not what the tools do, their safety, or their output quality. The call is one read-only tool named by this server's own list (list_/get_/search_, no mutating verb anywhere in the name, no required arguments and none that look like a key, an address or an amount), asked once a day with no arguments. Not asked is not a failure.
Observed record — 91 daily checks since 2026-07-17
- Succeeded
- 91
- Failed
- 0
- Their error
- 0
- Unattributed
- 0
This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 46 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. Every one of them passed, so the rate covers them too.
Last 30 days — to 2026-10-15, one point per UTC day
A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.
Tool inventory history — 50 now, peak 50, since 2026-07-19
- 2026-09-18 47 → 50 +3 (address_first_funder, entity_name_search, token_jup_dca)
- 2026-09-17 46 → 47 +1 (address_counterparties_batch)
- 2026-09-06 41 → 46 +5 (smart_traders_and_funds_dcas, smart_traders_and_funds_dex_trades, smart_traders_and_funds_historical_token_balances, smart_traders_and_funds_netflow…)
- 2026-09-05 38 → 41 +3 (address_labels, address_perp_positions, token_sectors)
- 2026-08-01 37 → 38 +1 (token_technical_indicators)
Recorded from our own daily tools/list handshake. A shrinking toolset is a real signal for an agent choosing a server; a gap in the series means the probe did not succeed that day, not that the tools disappeared.
Details
- Chains
- Multichain
- Agent types
- MCP Server, Data Provider
- Open source
- Unknown
- Works with
- Claude, Claude Desktop, Cursor
- Last checked
- 2026-10-15
Marketplace Signals
No marketplace signals recorded for this resource yet.
Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.
Where Nansen MCP fits
Related concepts: How Agents Interact With Smart Contracts, How Agents Use Wallets, What Are Onchain Agents?
Listing History
Recorded changes to Nansen MCP's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.
- Jul 20, 2026Edited: mcp endpoint url
- Jul 20, 2026Edited: deploy spec
- Jul 19, 2026Edited: mcp endpoint url
- Jul 19, 2026Sato Score tier: Low → MediumScore 34 → 59.
- Jul 18, 2026Sato Hub began tracking this listing
- Jul 14, 2026Auto-enriched: supported integrations
- Jul 13, 2026Listed on Sato Hub
Compared with
Appears in
Related Resources
Coinbase AgentKit
ActiveCoinbase's toolkit for giving AI agents wallets and the ability to take onchain actions.
Hyperliquid
ActiveOnchain perpetual futures and spot DEX running on its own L1 with an HyperEVM smart-contract layer.
Model Context Protocol (MCP)
ActiveAnthropic's open standard for connecting AI systems to external tools and data sources.
Reference
QuestionsWhat people ask about this pageShowHide
Questions people ask about Nansen MCP
- Is Nansen MCP open source?
- Unknown. Sato Hub has not found a public repository or a license statement for Nansen MCP as of 2026-10-15.
- Which chains does Nansen MCP support?
- Nansen MCP lists support for Multichain as of 2026-10-15.
- Is Nansen MCP still maintained?
- Sato Hub tracks no commit or release for Nansen MCP; it cannot say whether it is maintained.
- How do I install or run Nansen MCP?
- Hosted MCP endpoint (no local install). Install: claude mcp add --transport http nansen https://mcp.nansen.ai/ra/mcp --header "NANSEN-API-KEY: YOUR_API_KEY_HERE". Entry: {"mcpServers": {"nansen-mcp": {"command": "npx", "args": ["-y", "mcp-remote", "https://mcp.nansen.ai/ra/mcp", "--header", "NANSEN-API-KEY: ", "--allow-http"]}}}. This is taken from the project's own documentation and has not been reproduced by Sato Hub. It runs as an MCP server (https://mcp.nansen.ai/ra/mcp (Streamable HTTP)).
- Is Nansen MCP verified on Sato Hub?
- Sato Hub holds one earned check for Nansen MCP: Live endpoint probed — we called the hosted MCP endpoint and it answered with its real tool inventory (proves the interface works, not runtime safety). Its Sato Score is 67 of 100, a measure of how open, active and verifiable the project is, not a safety, quality or returns grade.
Cite this pagePlain text, APA or BibTeXShowHide
Cite this page
Sato Hub. "Nansen MCP — Sato Hub." Sato Hub, updated 2026-10-15, accessed 2026-10-15. https://satohub.ai/resources/nansen-mcpData last refreshed 2026-10-15; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.
Join the Sato Hub Briefing
Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.