# Nansen MCP server

> Query Nansen onchain analytics: labeled wallets, Smart Money activity, token flows, wallet PnL and Hyperliquid perps.

- Listing: https://mcp.tc/i/nansen
- Connect: use the server's own URL `https://mcp.nansen.ai/ra/mcp` (with your API key); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: API key
- Category: [Data & Analytics](https://mcp.tc/c/analytics)
- Vendor: Nansen
- Homepage: <https://docs.nansen.ai/mcp/connecting>

## About

Nansen MCP gives an assistant read access to Nansen onchain data. It covers labeled wallets, Smart Money trades and netflows, token screening, holders, OHLCV and technical indicators, wallet PnL, portfolios and Hyperliquid perpetuals across many chains.

It runs as a hosted Streamable HTTP endpoint at https://mcp.nansen.ai/ra/mcp. Access needs a Nansen API key sent in the NANSEN-API-KEY header. A separate curated connector endpoint exists for sign-in with a Nansen account.

## What it can do

- Track Smart Money DEX trades, perp trades and netflows
- Screen and discover trending tokens with filters
- Look up wallet labels, counterparties and first funder
- Analyze wallet PnL and portfolio holdings
- Get token OHLCV, technical indicators and quant scores
- Check Hyperliquid leaderboard and wallet positions
- Search tokens, entities and addresses

## Tools (54)

- `get_feedback_preferences`: Read the account's saved automatic feedback preference. (read-only)
- `submit_feedback`: Submit product feedback for the authenticated Nansen account.
- `get_feedback`: Read a feedback receipt by feedback ID. (read-only)
- `smart_traders_and_funds_token_balances`: Aggregated Smart Money token balances and 24h change per chain. (read-only)
- `smart_traders_and_funds_perp_trades`: Recent Hyperliquid perp trades by Smart Money addresses. (read-only)
- `smart_traders_and_funds_netflow`: Smart Money net USD flow per token over several windows. (read-only)
- `smart_traders_and_funds_dex_trades`: Individual DEX trades made by Smart Money wallets. (read-only)
- `smart_traders_and_funds_dcas`: Jupiter DCA orders opened by Smart Money on Solana. (read-only)
- `smart_traders_and_funds_historical_token_balances`: Day-by-day history of aggregated Smart Money balances. (read-only)
- `smart_traders_and_funds_pnl_leaderboard`: Rank Smart Money addresses by realized and unrealized PnL. (read-only)
- `fund_token_balances`: Current token holdings aggregated across Fund-labelled wallets. (read-only)
- `token_current_top_holders`: Top holders for a specific token. (read-only)
- `token_dex_trades`: DEX trades for a specific token. (read-only)
- `token_transfers`: Token transfers for a specific token, sortable. (read-only)
- `token_flows`: Hourly token-flow history for one holder segment. (read-only)
- `token_pnl_leaderboard`: Trader PnL for a token with sorting and filters. (read-only)
- `token_who_bought_sold`: Net buyers or sellers of a token on DEXs. (read-only)
- `token_recent_flows_summary`: On-chain flow snapshot across all wallet categories. (read-only)
- `token_discovery_screener`: Screen tokens across chains with advanced filters. (read-only)
- `token_ohlcv`: OHLCV price data for a token. (read-only)
- `token_technical_indicators`: Technical-analysis snapshot: SMA, EMA, RSI, MACD, Bollinger, ATR. (read-only)
- `token_info`: Token details or Hyperliquid perp stats. (read-only)
- `token_quant_scores`: Nansen Score risk and reward indicators for a token. (read-only)
- `nansen_score_top_tokens`: Daily list of tokens ranked by Nansen Score. (read-only)
- `hyperliquid_leaderboard`: Hyperliquid perp trader leaderboard with performance metrics. (read-only)
- `token_jup_dca`: Jupiter DCA orders opened against a Solana token. (read-only)
- `address_historical_balances`: Historical native and token balances of an address. (read-only)
- `address_labels`: Standard identity, behavioural and protocol labels for a wallet. (read-only)
- `address_related_addresses`: Related addresses such as first funder and signers. (read-only)
- `address_counterparties`: Addresses or entities with the most interactions with an address. (read-only)
- `address_counterparties_batch`: Top counterparties for up to 10 wallets in one call. (read-only)
- `address_transactions`: Most recent transactions of an address or entity. (read-only)
- `address_dex_trades`: A wallet's DEX swaps or Hyperliquid trades on one chain. (read-only)
- `address_perp_positions`: A wallet's Hyperliquid positions and liquidation risk. (read-only)
- `wallet_pnl_for_token`: PnL stats for a wallet on a specific token and date range. (read-only)
- `wallet_pnl_summary`: Aggregate realized PnL for an address. (read-only)
- `address_first_funder`: First address that funded an EVM wallet. (read-only)
- `address_portfolio`: Portfolio overview for a wallet or entity. (read-only)
- `general_search`: Search tokens, entities and addresses by query. (read-only)
- `entity_name_search`: Find exact entity names from a partial name. (read-only)
- `token_sectors`: List valid token sectors for token discovery filters. (read-only)
- `growth_chain_rank`: Get chain growth rankings by active addresses, transactions, gas fees and DEX volume. (read-only)
- `transaction_lookup`: Get transaction details and token transfers for a transaction hash. (read-only)
- `prediction_market_lookup`: Search Polymarket for events and markets by name, topic, URL, or slug. (read-only)
- `prediction_market_screener`: Browse and sort Polymarket markets, events, or categories. (read-only)
- `prediction_market_ohlcv`: Historical odds/volume candles for a Polymarket market. (read-only)
- `prediction_market_orderbook`: Live orderbook for a Polymarket market. (read-only)
- `prediction_market_top_holders`: Largest current holders for a Polymarket market. (read-only)
- `prediction_market_trades`: Recent trades for a Polymarket market. (read-only)
- `prediction_market_pnl_leaderboard`: PnL leaderboard for a Polymarket market. (read-only)
- `prediction_market_position_detail`: Detailed position breakdown for a Polymarket market. (read-only)
- `prediction_market_address_trades`: Prediction market trade history for a Polygon wallet. (read-only)
- `prediction_market_address_summary`: Prediction market summary metrics for a Polygon wallet. (read-only)
- `prediction_market_address_pnl`: Prediction market PnL breakdown for a Polygon wallet, market by market. (read-only)

## Example prompts

- "Show Solana tokens with Smart Money inflows over the last 24 hours."
- "Find Wintermute in Nansen and show its current token holdings."
- "Look up PEPE on Ethereum and summarize its recent price and token flows."
- "Show the PnL summary for this wallet address on Ethereum."

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http nansen https://mcp.nansen.ai/ra/mcp --header "NANSEN-API-KEY: <YOUR_API_KEY>"
```

2. Replace the placeholder with your key before you run it, then check it with `/mcp` inside Claude Code.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Use the `mcp-remote` bridge, which keeps the key on this computer (a connector added on claude.ai with the key under **Request headers** also shows up here). Open **Settings → Developer → Edit Config** and add:

`claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "nansen": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.nansen.ai/ra/mcp",
        "--header",
        "NANSEN-API-KEY: <YOUR_API_KEY>"
      ]
    }
  }
}
```

2. Replace the placeholder with your key and restart Claude Desktop.

The bridge needs Node.js on your computer.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Nansen&connectorUrl=https%3A%2F%2Fmcp.nansen.ai%2Fra%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://mcp.nansen.ai/ra/mcp`. Under **Request headers**, add `NANSEN-API-KEY: <YOUR_API_KEY>` with your key from Nansen, then click **Add**.

3. Turn it on in a chat from the tools menu.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=nansen&config=eyJ1cmwiOiJodHRwczovL21jcC5uYW5zZW4uYWkvcmEvbWNwIiwiaGVhZGVycyI6eyJOQU5TRU4tQVBJLUtFWSI6IjxZT1VSX0FQSV9LRVk%2BIn19>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "nansen": {
      "url": "https://mcp.nansen.ai/ra/mcp",
      "headers": {
        "NANSEN-API-KEY": "<YOUR_API_KEY>"
      }
    }
  }
}
```

### VS Code

Add it to `.vscode/mcp.json`. VS Code asks for the key the first time and stores it securely:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "nansen": {
      "type": "http",
      "url": "https://mcp.nansen.ai/ra/mcp",
      "headers": {
        "NANSEN-API-KEY": "${input:nansen-api-key}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "nansen-api-key",
      "description": "NANSEN-API-KEY",
      "password": true
    }
  ]
}
```

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "nansen": {
      "serverUrl": "https://mcp.nansen.ai/ra/mcp",
      "headers": {
        "NANSEN-API-KEY": "<YOUR_API_KEY>"
      }
    }
  }
}
```

2. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add nansen --url https://mcp.nansen.ai/ra/mcp
```

`codex mcp add` can’t set the `NANSEN-API-KEY` header, so this step is required: put this entry in `~/.codex/config.toml` instead of running the command, or add its `env_http_headers` line to the entry the command made:

`config.toml`:

```toml
[mcp_servers.nansen]
url = "https://mcp.nansen.ai/ra/mcp"
env_http_headers = { "NANSEN-API-KEY" = "NANSEN_API_KEY" }
```

Codex reads the header values from the environment variables named in `env_http_headers`.

### Gemini CLI

```bash
gemini mcp add --transport http --header "NANSEN-API-KEY: <YOUR_API_KEY>" nansen https://mcp.nansen.ai/ra/mcp
```

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "nansen": {
      "type": "http",
      "url": "https://mcp.nansen.ai/ra/mcp",
      "headers": {
        "NANSEN-API-KEY": "<YOUR_API_KEY>"
      }
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://mcp.nansen.ai/ra/mcp`.

## Recent changes

- 2026-11-22 02:57 UTC: Server instructions changed. Source: automatic check. Worth a look: new server instructions.
- 2026-11-21 23:59 UTC: Server instructions changed. Source: automatic check. Worth a look: new server instructions.
- 2026-11-21 21:00 UTC: Server instructions changed. Source: automatic check. Worth a look: new server instructions.
- 2026-11-21 02:52 UTC: Server instructions changed. Source: automatic check. Worth a look: new server instructions.
- 2026-11-20 23:55 UTC: Server instructions changed. Source: automatic check. Worth a look: new server instructions.

More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/nansen#history (Atom feed: https://mcp.tc/i/nansen/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review.

## Details

- Server version: 3.2.4
- MCP protocol version: 2025-11-25
- Last checked: 2026-11-22 (reachable, asks for credentials)
- Listed: 2026-11-19
- Updated: 2026-11-19

---
Source: https://mcp.tc/i/nansen (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
