Nansen MCP server

Connect Nansen and your agent gets 47 tools, among them address_counterparties, address_counterparties_batch, address_dex_trades. It answers at https://mcp.nansen.ai/ra/mcp/ over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 22 October 2026, succeeded.

Status

Answering

Tools

Reliability

6 of 6 checks

Response time

172 ms

Transport

streamable HTTP

Last checked

22 October 2026

Blockchain analytics API for AI agents. Smart Money signals, wallet profiling, token analytics.

Description as the publisher wrote it.

The 47 tools Nansen offers

Tool	What it does
`address_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 for each counterparty Note: To get related Inputs: request
`address_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 this tool to compare wallets — counterparties Inputs: request
`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: one per call ('all'/'evm' unsupported). EVM Inputs: request
`address_historical_balances`	Get historical native coin & token balances of address. Inputs: request
`address_labels`	Get the standard labels for one wallet address. This tool returns identity, behavioural, and protocol labels. It does not return premium labels. Inputs: request
`address_perp_positions`	Get a wallet's Hyperliquid positions and liquidation risk without a portfolio lookup. Inputs: request
`address_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 different modes: - 'fast-mode-default': Walle Inputs: request
`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 Multisig Signer of', 'Deployed via', 'Deployed Inputs: request
`address_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. Inputs: request
`general_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, topics, event slugs, or URLs, use `prediction Inputs: query, result_type, max_results, chain
`growth_chain_rank`	Get chain growth rankings by active addresses, transactions, gas fees and DEX volume. Inputs: request
`hyperliquid_leaderboard`	Get Hyperliquid perpetual futures trader leaderboard with performance metrics. Returns: Trader performance rankings as markdown. Columns returned: - Address / Label: trader wallet, and its Nansen label if any - Total PnL (USD): Inputs: request
`nansen_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 recommendations based on backtested indicator Inputs: request
`prediction_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` = redemption + unrealized value + sell proc Inputs: request
`prediction_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 asks for a general wallet profile, activity su Inputs: request
`prediction_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 transaction. Pitfalls: - Use this for wallet tr Inputs: request
`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 tradable outcome with its own `marketId`. - Exa Inputs: request
`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: - `Close` is the share price for the displaye Inputs: request
`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 describe share size as dollar depth unless you Inputs: request
`prediction_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 market only. - `Net Buy Cost USD` is what the Inputs: request
`prediction_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 received for this outcome token. - `Unrealized Inputs: request
`prediction_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/slug/URL — use `prediction_market_lookup` Inputs: request
`prediction_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 Held` is the share side currently held. **P Inputs: request
`prediction_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 fields: - `Share Size` is quantity; `Value US Inputs: request
`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; use smart_traders_and_funds_dex_trades for Inputs: request
`smart_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). Use this to see exactly which wallet bo Inputs: request
`smart_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. Use this to see how smart money holdings Inputs: request
`smart_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 specific chain(s). Use this for what smart Inputs: request
`smart_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 of Smart Money activity across all tokens, Inputs: request
`smart_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. Use this to find the best performing sm Inputs: request
`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 all supported chains) or specific chain(s). Inputs: request
`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 it, or to combine it with other non smart Inputs: request
`token_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 to "hyperliquid") NOTE: In onchain_toke Inputs: request
`token_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 filtering options to narrow down the results. In a
`token_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_segment: smart_money` is not a good proxy for an Inputs: request
`token_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, socials) and spot trading metrics (volume, Inputs: request
`token_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 Hyperliquid perps, pass `chain="hyperliquid"` a Inputs: request
`token_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 address - `perps`: Analyze Hyperliquid perp
`token_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 quantitative data to make trading decisions. R Inputs: request
`token_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 as 1d. Returns TOTAL token flows per s Inputs: request

7 more tools

token_sectors, token_technical_indicators, token_transfers, token_who_bought_sold, transaction_lookup, wallet_pnl_for_token, wallet_pnl_summary

Add Nansen to your AI client

Every block below points at https://mcp.nansen.ai/ra/mcp/. Pick your client and copy.

Claude Code: one command in your terminal

claude mcp add --transport http nansen https://mcp.nansen.ai/ra/mcp/

Claude Desktop: claude_desktop_config.json

{
  "mcpServers": {
    "nansen": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.nansen.ai/ra/mcp/"]
    }
  }
}

Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project

{
  "mcpServers": {
    "nansen": {
      "url": "https://mcp.nansen.ai/ra/mcp/"
    }
  }
}

VS Code and GitHub Copilot: .vscode/mcp.json

{
  "servers": {
    "nansen": {
      "type": "http",
      "url": "https://mcp.nansen.ai/ra/mcp/"
    }
  }
}

Zed: Zed settings.json

{
  "context_servers": {
    "nansen": {
      "url": "https://mcp.nansen.ai/ra/mcp/"
    }
  }
}

Windsurf: ~/.codeium/mcp_config.json

{
  "mcpServers": {
    "nansen": {
      "serverUrl": "https://mcp.nansen.ai/ra/mcp/"
    }
  }
}

JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON

{
  "mcpServers": {
    "nansen": {
      "url": "https://mcp.nansen.ai/ra/mcp/"
    }
  }
}

Continue: .continue/mcpServers/neuronto.yaml

name: Nansen
version: 0.0.1
schema: v1
mcpServers:
  - name: Nansen
    type: streamable-http
    url: https://mcp.nansen.ai/ra/mcp/

Gemini CLI: ~/.gemini/settings.json

{
  "mcpServers": {
    "nansen": {
      "httpUrl": "https://mcp.nansen.ai/ra/mcp/"
    }
  }
}

Codex CLI: MCP server config

{
  "mcpServers": {
    "nansen": {
      "type": "http",
      "url": "https://mcp.nansen.ai/ra/mcp/"
    }
  }
}

Warp: MCP servers, + Add, paste JSON

{
  "mcpServers": {
    "nansen": {
      "url": "https://mcp.nansen.ai/ra/mcp/"
    }
  }
}

Goose: a one-click extension link

goose://extension?url=https%3A%2F%2Fmcp.nansen.ai%2Fra%2Fmcp%2F&type=streamable_http&id=nansen&name=Nansen

Is Nansen up right now?

It answered our last check on 22 October 2026 in 172 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to Nansen

Kansei3 tools CaudexCatena0 tools BentCrypto Machine Payments2 tools BankSync0 tools Agentic AI4 tools Intelligence3 tools

Questions about Nansen

How many tools does Nansen have?

47, as returned by the server's own tools/list on 17 September 2026: address_counterparties, address_counterparties_batch, address_dex_trades, address_historical_balances, address_labels, address_perp_positions, address_portfolio, address_related_addresses, and 39 more.

Is Nansen down?

It answered our last check on 22 October 2026 in 172 ms. Over 6 checks since 11 September 2026 it answered 6.

How do I add Nansen to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.nansen.ai/ra/mcp/. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does Nansen need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: io.github.nansen-ai. Endpoint host: mcp.nansen.ai. ARD identifier: urn:air:io.github.nansen-ai:mcp:nansen-mcp. First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.