Nansen is an MCP server with 38 tools an agent can call, among them address_counterparties, address_dex_trades, address_historical_balances. 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 10 of 10 times since 5 September 2026; the last check, on 18 October 2026, succeeded.
DEPRECATED - This server has been moved to io.github.nansen-ai/nansen-mcp. Do not use.
Description as the publisher wrote it.
| 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_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_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. **Key fields:** - Market-by-market PnL when the API provides it. - Blank PnL fields mean unavailable data, not zero. - `Position Size (Shares)` is quantity; `Position Value USD` is curre 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:** - `Side Held` reflects current side exposure where the API provides it. **Pitfalls:** - If PnL fields are blank, say profitability is Inputs: request |
prediction_market_position_detail | Detailed position breakdown for a Polymarket market. **Key fields:** - `Position Size (Shares)` is quantity held in this market. - `Position Value USD` is current marked value, not final payout at resolution. - `Cost Basis USD` and `Unreali 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_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_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 |
token_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 at an explicit timeframe. Supports EVM chai Inputs: request |
token_transfers | Get 25 token transfers (per page) for a specific token based on the sort order. Default is most recent transfers first. **NOTE:** This tool does not support native tokens (so11111111111111111111111111111111111111112, 0xeeeeeeeeeeeeeeeeeeeee Inputs: request |
token_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 they are liquidating profits or accumulating Inputs: request |
transaction_lookup | Get comprehensive transaction details including token transfers. Inputs: transaction_hash, chain |
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. Chain: pass 'hyperliquid' for a perp coin — th Inputs: request |
wallet_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 positions. For chain='all'/'evm' on an EVM ad Inputs: request |
Every block below points at https://mcp.nansen.ai/ra/mcp. Pick your client and copy.
claude mcp add --transport http nansen https://mcp.nansen.ai/ra/mcp
{
"mcpServers": {
"nansen": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.nansen.ai/ra/mcp"]
}
}
}{
"mcpServers": {
"nansen": {
"url": "https://mcp.nansen.ai/ra/mcp"
}
}
}{
"servers": {
"nansen": {
"type": "http",
"url": "https://mcp.nansen.ai/ra/mcp"
}
}
}{
"context_servers": {
"nansen": {
"url": "https://mcp.nansen.ai/ra/mcp"
}
}
}{
"mcpServers": {
"nansen": {
"serverUrl": "https://mcp.nansen.ai/ra/mcp"
}
}
}{
"mcpServers": {
"nansen": {
"url": "https://mcp.nansen.ai/ra/mcp"
}
}
}name: Nansen
version: 0.0.1
schema: v1
mcpServers:
- name: Nansen
type: streamable-http
url: https://mcp.nansen.ai/ra/mcp{
"mcpServers": {
"nansen": {
"httpUrl": "https://mcp.nansen.ai/ra/mcp"
}
}
}{
"mcpServers": {
"nansen": {
"type": "http",
"url": "https://mcp.nansen.ai/ra/mcp"
}
}
}{
"mcpServers": {
"nansen": {
"url": "https://mcp.nansen.ai/ra/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.nansen.ai%2Fra%2Fmcp&type=streamable_http&id=nansen&name=Nansen
It answered our last check on 18 October 2026 in 195 ms. Over 10 checks since 5 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
38, as returned by the server's own tools/list on 31 August 2026: address_counterparties, address_dex_trades, address_historical_balances, address_portfolio, address_related_addresses, address_transactions, general_search, growth_chain_rank, and 30 more.
It answered our last check on 18 October 2026 in 195 ms. Over 10 checks since 5 September 2026 it answered 10.
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.
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.
Publisher: io.github.hurcannansen. Endpoint host: mcp.nansen.ai. ARD identifier: urn:air:io.github.hurcannansen:mcp:nansen-mcp.
First indexed 31 August 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.