Nansen MCP server
io.github.nansen-ai/nansen-mcpnansen-aistreamable-httpv1.0.1Scanned
Blockchain analytics API for AI agents. Smart Money signals, wallet profiling, token analytics.
54 tools: 2 do something that can't be undone, 13 change things and 39 only read.
- Reads private data · 0
- Reads text others write · 51
- Can send data out · 1
- 16 findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here do something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Nansen MCP server can do
The Nansen MCP server is published by the GitHub account nansen-ai. It has 54 tools. It can do things that cannot be undone, such as sending, paying or publishing (token_transfers and token_pnl_leaderboard) and create or change data (13 tools: submit_feedback, smart_traders_and_funds_pnl_leaderboard, nansen_score_top_tokens, address_labels and 9 more), but cannot delete data. 39 tools only read.
51 tools bring in text other people can write (smart_traders_and_funds_token_balances, smart_traders_and_funds_perp_trades, smart_traders_and_funds_netflow and 48 more); 1 tool can send data out of your system (submit_feedback).
The fixed checks matched 16 findings (credentials-mention, base64-blob, long-description and annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 21, 2026, version 1.0.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
54 tools
Can't be undone 2Claude Code: ask
token_pnl_leaderboardUpto 25 results (per page) of trader PnL for a token.Reads text others write2 findings
Why it is in this group
- The input addresses people (input.request.dateRange.to): what it sends cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The description is 4,040 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...otherwise you will miss data. ** This tool does not support hyperevm as chain **"
- Warn
The server marks "token_pnl_leaderboard" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The input addresses people (input.request.dateRange.to): what it sends cannot be taken back.
Description, as the server wrote it 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 perpetual futures by symbol (chain auto-set to "hyperliquid") — supports native tokens **NOTE:** This tool does not support native tokens (so11111111111111111111111111111111111111112, 0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee) in `onchain_tokens` mode. Native tokens (by symbol - SOL, ETH, ARB etc) ARE fully supported in `perps` mode. Returns: Trader performance rankings as markdown. Returns empty string if no trading data found. Columns returned: - **Address**: Trader's wallet address - **Label**: Nansen label of the trader - **Total PnL**: Combined realized and unrealized PnL (currency formatted, can be negative) - **Total ROI**: Total return on investment as percentage (percentage formatted) - **Realized PnL**: Profit/loss from completed trades (currency formatted, can be negative) - **Realized ROI**: Return on investment from realized trades only (percentage formatted) - **Unrealized PnL**: Current profit/loss on open positions (currency formatted, can be negative) - **Unrealized ROI**: Return on investment from unrealized positions only (percentage formatted) - **Token Holdings**: Current token quantity held (numeric formatted) - **Holdings USD**: Current USD value of token holdings (currency formatted) - **Token Price**: Current price per token (price formatted) - **Peak Token Holdings**: Maximum token quantity ever held in the date range (numeric formatted) - **Peak Holdings USD**: Maximum USD value ever held in the date range (currency formatted) - **Still Holding %**: Percentage of peak holdings still held (percentage formatted) - **Total Trades**: Number of trades executed by this address - **Net Flow**: Net money flow - negative means net seller (currency formatted, can be negative) **Sorting** Options You can **ONLY** sort by pnl_usd_total, roi_percent_total, pnl_usd_realised, roi_percent_realised, pnl_usd_unrealised, roi_percent_unrealised, holding_amount, max_balance_held, nof_trades, still_holding_balance_ratio, netflow_amount **Filtering** Options: 📋 List filters: trader_address, trader_address_label 📊 Numeric range filters: pnl_usd_realised, pnl_usd_unrealised, holding_amount, holding_usd, nof_trades, still_holding_balance_ratio, max_balance_held, max_balance_held_usd Examples: # On-chain tokens (default mode) ``` { "mode": "onchain_tokens", "chain": "ethereum", "tokenAddress": "0xa0b86a33e6ba3e5b9e4b1b1b1b1b1b1b1b1b1b1b", "dateRange": {"from": "30D_AGO", "to": "NOW"}, "orderBy": "pnl_usd_total", "order_by_direction": "desc" } ``` # Hyperliquid perpetual futures ``` { "mode": "perps", "tokenAddress": "ETH", "dateRange": {"from": "7D_AGO", "to": "NOW"} } ``` # Advanced filtering: Find profitable active traders with significant holdings ``` { "chain": "ethereum", "tokenAddress": "0xa0b86a33e6ba3e5b9e4b1b1b1b1b1b1b1b1b1b1b", "dateRange": {"from": "30D_AGO", "to": "NOW"}, "pnlUsdTotal": {"from": 1000, "to": 999999999}, "nofTrades": {"from": 5, "to": 100}, "holdingUsd": {"from": 10000, "to": 999999999}, "stillHoldingBalanceRatio": {"from": 0.1, "to": 1.0}, "orderBy": "roi_percent_total", "order_by_direction": "desc" } ``` Notes: - Ranked by total PnL performance by default - Useful for identifying successful traders and copying strategies - Both ascending and descending sorts provide valuable insights (winners vs losers) - ONLY RETURNS TOP 25 RESULTS for the sort order. Hence the result is NEVER complete. - Make sure the sort order is relevant to your analysis as otherwise you will miss data. ** This tool does not support hyperevm as chain **
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
token_transfersGet 25 token transfers (per page) for a specific token based on the sort order.Reads text others write5 findings
Why it is in this group
- The name "token_transfers" says "transfer": a word for a change that another call does not undo.
- The input addresses people (input.request.dateRange.to): what it sends cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The description contains a 42-character base64 string.
What this check looks forMatched text
description: "..."fromAddress": "0x2b060b9c89B8aD04e5E1fD40F1f327e41DD32c72", "columns":..."
- Warn
The description contains a 42-character base64 string.
What this check looks forMatched text
description: "..."toAddress": "0x2b060b9c89B8aD04e5E1fD40F1f327e41DD32c72", "min_amount..."
- Warn
The description contains a 42-character base64 string.
What this check looks forMatched text
description: "..."fromAddress": "0x2b060b9c89B8aD04e5E1fD40F1f327e41DD32c72", "orderBy":..."
- Info
The description is 7,329 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...*Smart Money*) - transferValueUsd filters by USD value at time of transaction"
- Warn
The server marks "token_transfers" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "token_transfers" says "transfer": a word for a change that another call does not undo.
Description, as the server wrote it 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 sender, toAddress = the receiver): - "Transfers of X", "X's transfers", "track X", and "what is X doing" do not name a direction. For these, make two calls with the same address: one with fromAddress, one with toAddress. Sort both by amount. Each call then shows different transactions: the largest sent and the largest received. - Use only fromAddress when the user asks what X sent (outflows, withdrawals, "sent to", "moved to an exchange"). - Use only toAddress when the user asks what X received (inflows, deposits, "where did X get"). - Do not put the same address in fromAddress and toAddress of one call. The filters combine with AND, so the call returns only transfers from the wallet to itself (usually none). - If the user names no wallet, do not add an address filter. **NOTE:** This tool does not support native tokens (so11111111111111111111111111111111111111112, 0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee). Columns returned: - **Time**: Timestamp when the transfer occurred (block_timestamp: ISO 8601 format) - **From Label**: Source address label (from_address_label: sender of tokens) - **To Label**: Destination address label (to_address_label: receiver of tokens) - **From Address**: Raw source address (from_address: hex address) - **To Address**: Raw destination address (to_address: hex address) - **Amount**: Quantity of tokens transferred (transfer_amount: numeric) - **Value USD**: USD value of the transfer at time of transaction (transfer_value_usd: currency formatted) - **Type**: Transfer category (transaction_type: DEX, CEX, transfer, etc.) - **Tx Hash**: Blockchain transaction hash for verification (transaction_hash) Sorting Options (all fields support "asc"/"desc"): Available for sorting: timestamp, amount - amount (default): largest transfers first. Use it when the user asks about size, value, dollar amounts, the largest transfers, or whales. - timestamp: latest transfers first. Use it only when the user asks for the latest transfers or for a time order. A page shows at most 25 transfers. For every total, min, max, mean, count or list of wallets ("which wallets", "all wallets", "how much in total"), use `columns` with `aggregations`, also when the transfers fit on one page. The tool then computes the result from the raw values of all matching transfers. Examples: # Basic request (largest transfers in the last 24 hours, the default sort) ``` { "chain": "ethereum", "tokenAddress": "0xa0b86a33e6b6c4b3add000b44b3a1234567890ab", "dateRange": {"from": "24H_AGO", "to": "NOW"}, "orderBy": "amount", "order_by_direction": "desc" } ``` # Latest transfers first (only when the user asks for the latest) ``` { "chain": "ethereum", "tokenAddress": "0xa0b86a33e6b6c4b3add000b44b3a1234567890ab", "dateRange": {"from": "24H_AGO", "to": "NOW"}, "orderBy": "timestamp", "order_by_direction": "desc" } ``` # Smart money only filter (largest transfers first) ``` { "chain": "ethereum", "tokenAddress": "0xa0b86a33e6b6c4b3add000b44b3a1234567890ab", "dateRange": {"from": "7D_AGO", "to": "NOW"}, "transferOriginCategories": ["all_transfers"], "onlySmartTradersAndFunds": true, "orderBy": "amount", "order_by_direction": "desc" } ``` # Filter by DEX only with minimum transfer value (USD) ``` { "chain": "ethereum", "tokenAddress": "0xa0b86a33e6b6c4b3add000b44b3a1234567890ab", "dateRange": {"from": "24H_AGO", "to": "NOW"}, "transferOriginCategories": ["dex"], "transferValueUsd": {"from": 1000} } ``` # Every wallet that received the token from one sender, all pages ``` { "chain": "ethereum", "tokenAddress": "0xa0b86a33e6b6c4b3add000b44b3a1234567890ab", "dateRange": {"from": "2026-10-02", "to": "2026-10-02"}, "fromAddress": "0x2b060b9c89B8aD04e5E1fD40F1f327e41DD32c72", "columns": ["to_address"], "aggregations": ["unique"] } ``` # Total amount that one wallet received, without transfers below 1 token ``` { "chain": "ethereum", "tokenAddress": "0xa0b86a33e6b6c4b3add000b44b3a1234567890ab", "dateRange": {"from": "7D_AGO", "to": "NOW"}, "toAddress": "0x2b060b9c89B8aD04e5E1fD40F1f327e41DD32c72", "min_amount": 1, "columns": ["amount"], "aggregations": ["sum"] } ``` # One wallet, no direction named: make two calls, both sorted by amount # Call 1: what the wallet sent ``` { "chain": "base", "tokenAddress": "0x833589fcd6edb6e08f4c7c32d4f71b54bda02913", "dateRange": {"from": "7D_AGO", "to": "NOW"}, "fromAddress": "0x2b060b9c89B8aD04e5E1fD40F1f327e41DD32c72", "orderBy": "amount", "order_by_direction": "desc" } ``` # Call 2: what the wallet received ``` { "chain": "base", "tokenAddress": "0x833589fcd6edb6e08f4c7c32d4f71b54bda02913", "dateRange": {"from": "7D_AGO", "to": "NOW"}, "toAddress": "0x2b060b9c89B8aD04e5E1fD40F1f327e41DD32c72", "orderBy": "amount", "order_by_direction": "desc" } ``` **Available Filters:** Address Filters: - **fromAddress** (str or list[str], optional): the wallet(s) that SENT the tokens Example: "0x2b060b9c89B8aD04e5E1fD40F1f327e41DD32c72" Example: ["0xaddr1", "0xaddr2"] - **toAddress** (str or list[str], optional): the wallet(s) that RECEIVED the tokens See the Direction rules at the top. Transfer Origin Categories: - **transferOriginCategories** (list[str]): List of transfer types to include Possible values: ['dex', 'cex', 'non_exchange_transfers', 'all_transfers'] Default: ['all_transfers'] Examples: - ['dex… [1329 more characters not shown]
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Changes things 13Claude Code: ask
address_labelsGet the standard labels for one wallet address.Reads text others write1 finding
Why it is in this group
- The name "address_labels" says "label": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "address_labels" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "address_labels" says "label": a word for a change.
Description, as the server wrote it Get the standard labels for one wallet address. This tool returns identity, behavioural, and protocol labels. It does not return premium labels.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
nansen_score_top_tokensDiscover and filter a daily list of attractive tokens using Nansen Score Indicators weighted by coefficients (= Performance Score).Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 indicators. For specific token analysis (e.g., "should I buy AAVE?"), use token_quant_scores instead. **When to use this tool vs token_discovery_screener**: - Use **this tool** when you want **pre-scored buying recommendations** without specifying criteria. It answers "what should I buy?" by returning tokens that already meet a quantitative buying threshold (Performance Score ≥15) based on alpha indicators like price momentum, chain fees, and protocol fees. Data is updated in batches. - Use **token_discovery_screener** when you want **live data** or to **explore tokens by specific criteria** like sectors (e.g., "AI memecoins"), token age (e.g., "new launches"), smart money activity, or custom volume/liquidity thresholds. It's a filtering tool with real-time metrics where you define what you're looking for. Returns tokens pre-filtered by: performance_score >= 15 (buying threshold). **Example queries**: "what tokens should I buy?", "which tokens look good?", "best tokens to buy today" **Scoring:** - **Performance Score** (range -60 to +75): Higher = better alpha opportunity. **Buy threshold: ≥15** - **Risk Score** (range -60 to +80): Higher = safer token. >0 indicates low to medium risk. Every time you give the Performance Score to the user, explain the scoring thresholds above. Same for the Risk Score. Every time quote the underlying indicators that contributed the most to the Performance/ Risk score and recall their definition to the user. Returns: A list of tokens with the highest Performance Score as markdown. Core fields: Token Address, Token Symbol, Chain, Performance Score, Risk Score. Indicator columns are included dynamically based on data availability (columns with all zeros are excluded).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
prediction_market_address_pnlPrediction market PnL breakdown for a Polygon wallet, market by market.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 proceeds − buy cost, for that market only. - `Net Buy Cost USD` is what the wallet paid for shares. - `Net Sell Proceeds USD` is what it received for shares sold before resolution. - `Redemption Value USD` is the payout collected after the market settled. - `Unrealized Value USD` is the marked value of shares still held. - `Resolved` says whether the market has settled. **Pitfalls:** - Each row covers one market. Sum the rows for a wallet total, or use `prediction_market_address_summary` for the aggregate. - The API gives no ROI or share count here. Do not state them. - Blank PnL fields mean unavailable data, not zero.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
prediction_market_address_summaryPrediction market summary metrics for a Polygon wallet.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 summary, or whether a wallet is active on Polymarket. **Key fields:** - `Markets Traded` and `Markets Won` are lifetime counts; `Win Rate` is won / traded. - `Total PnL USD` = realized + unrealized. - `First Seen` and `Wallet Age (Days)` show how long the wallet has been active on Polymarket. **Pitfalls:** - The API gives no trade count, volume, or ROI here. Do not state them. For per-market cost and proceeds use `prediction_market_address_pnl`. - Blank PnL fields mean unavailable data, not zero.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
prediction_market_address_tradesPrediction market trade history for a Polygon wallet.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 trade activity, not profitability.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
prediction_market_ohlcvHistorical odds/volume candles for a Polymarket market.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 displayed outcome side. - In binary markets, Yes and No shares are complementary and sum to about $1. **Pitfalls:** - Each response is for one exact `marketId` — do not mix dates or prices across different markets. - If no candles are returned for the requested window, say so directly — do not estimate. **Prerequisites:** If `marketId` is unknown, call `prediction_market_lookup` first.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
prediction_market_orderbookLive orderbook for a Polymarket market.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 calculate `shares × price`. **Yes/No price relationship:** - Yes and No are complementary (Yes + No ≈ $1). A No bid at price $X means willingness to buy No when Yes is near $(1−X). - A cluster of No bids at low prices (e.g. $0.20) is resistance for Yes rallying to ~$0.80, NOT a support floor for the current Yes price. - When comparing OHLCV odds against orderbook depth, convert No-side prices to Yes-equivalent (1 − No price) before drawing divergence conclusions. **Pitfalls:** - Do not treat raw no-share prices as bearish yes-share odds — prefer `prediction_market_ohlcv` for current odds / implied probability. **Prerequisites:** If `marketId` is unknown, call `prediction_market_lookup` first.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
prediction_market_pnl_leaderboardPnL leaderboard for a Polymarket market.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 wallet paid for shares. - `Net Sell Proceeds USD` is what it received for shares sold before resolution. - `Redemption Value USD` is the payout collected after the market settled. - `Unrealized Value USD` is the marked value of shares still held. - `Side Held` reflects current side exposure where the API provides it. **Pitfalls:** - The API gives no ROI, volume, or trade count here. Do not state them. - If PnL fields are blank, say profitability is unavailable — do not substitute top holders or position size. **Prerequisites:** If `marketId` is unknown, call `prediction_market_lookup` first.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
prediction_market_position_detailDetailed position breakdown for a Polymarket market.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 Value USD` is the marked value of shares still held; `Redemption Value USD` is the payout collected after settlement. - `Position PnL USD` applies to the displayed row only — not the wallet's total PM activity. **Pitfalls:** - Each row is one outcome token of one wallet. A wallet holding both sides appears twice. **Prerequisites:** If `marketId` is unknown, call `prediction_market_lookup` first.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
prediction_market_top_holdersLargest current holders for a Polymarket market.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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. **Pitfalls:** - The visible holder table is the source of truth for holder-side concentration — do not infer risk, max loss, or potential profit unless the tool output explicitly provides it. - Output summary is based only on shown rows, not the entire holder table. - Large visible positions or labels do not by themselves identify smart money unless Nansen smart-money-labelled data supports it. **Prerequisites:** If `marketId` is unknown, call `prediction_market_lookup` first.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
prediction_market_tradesRecent trades for a Polymarket market.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 USD` is dollar value. - Each row is one visible trade leg — `Value USD` applies to that row, not the whole transaction hash. **Pitfalls:** - Large visible trades do not by themselves identify smart money or institutions. **Prerequisites:** If `marketId` is unknown, call `prediction_market_lookup` first.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
smart_traders_and_funds_pnl_leaderboardRank smart trader 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 tr…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Rank smart trader 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 smart money wallets; use token_pnl_leaderboard for the best performers on one specific token.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
submit_feedbackSubmit product feedback for the authenticated Nansen account.Can send data out1 finding
Why it is in this group
- The name "submit_feedback" says "submit": a word for a change.
What it can reach
- outboundThe input takes a URL (input.request.endpoint): a request to a URL can carry data to whoever runs it.
Findings
- Info
The input schema at properties.request.properties.endpoint.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.request.properties.endpoint.description: "...about. Do not include a query string or credentials."
Description, as the server wrote it Submit product feedback for the authenticated Nansen account. Costs zero credits, including with zero balance. Send when the user requests or approves this report. Before a new automatic report, call get_feedback_preferences for a fresh account preference. If it is off, unconfigured or unavailable, show the report and ask before sending. If the user refuses or you cannot ask, do not send. Enabled permits sending subject to host controls. One report approval does not change the preference. Never enable it yourself. Host denial means no submission. A feedback_not_enabled refusal means stop automatic retries and tell the user the feature is not enabled for this account. Approval and saved preferences do not override rollout. Seven accepted reports per account per week across all clients, resetting Monday 00:00 UTC. Generate submission_id once per new report; reuse it and the exact report for retries and re-invocations. Never replace an ID after a timeout. Limits: description/goal/expected/observed/workaround 2,000 Unicode characters each; endpoint/tool 256; 10 distinct request IDs of 128 characters; client name/version 64; total JSON body 16 KiB UTF-8. Use category missing_capability for a feature request or a product gap. Missing capabilities need no endpoint, tool, or request ID. Omit secrets. Received means saved, not fixed. Failures preserve recovery guidance. No alternate-account or server-key fallback. Do not redirect failed submissions to unrelated feedback channels.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 39Show 39 read-only tools
address_counterpartiesGet 25 (per page) addresses or entities with the most common interactions with input addresses Default sort is net value transferred between them.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 wallets: - Focus on direct value transfers to get most likely addresses. - Include CEX deposit addresses (not withdrawal addresses!) as well. - Also go one level deeper: - Find addresses that interacted with the most likely addresses. - Find addresses that deposited to the same CEX deposit (NOT withdrawal!) addresses. - Address structure / string is not important, but the relationship is! Sorting Options (all fields support "ASC"/"DESC"): Available for sorting: total_volume_usd, volume_in_usd, volume_out_usd, interaction_count Examples: # Query by single address { "address": "0x123...", "sourceInput": "Combined", "groupBy": "wallet", "chain": "ethereum", "timeRange": {"from": "30D_AGO", "to": "NOW"}, "order_by": "total_volume_usd", "order_by_direction": "desc" } # Query by entity { "entity_id": "Binance", "sourceInput": "Combined", "groupBy": "entity", "chain": "all", "timeRange": {"from": "7D_AGO", "to": "NOW"} } For a trader, send trader_id instead of address or entity_id: the counterparties of all wallets of the trader, at most 90 days. # Query by trader { "trader_id": "5482f9aeb02f67b7", "chain": "solana", "timeRange": {"from": "30D_AGO", "to": "NOW"} }
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
address_counterparties_batchGet the top counterparties of up to 10 wallet addresses in one call.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 that two wallets share, a group of wallets that sends to the same CEX deposit address, or one fund with many wallets. For one wallet, or for an entity name, use address_counterparties. Limits: - Maximum 10 distinct wallet addresses for each call. Repeated addresses are removed. - Maximum 90 days for the date range. A wider range is rejected — make more than one call. - One chain family for each call: every address must be EVM, or every address must be Solana, and so on. Do not mix families. Name a `chain` (for example ethereum) to read that chain only. Leave `chain` out to read every chain of the addresses' family at one time — then a counterparty met on more than one chain gets one row for each chain, so do not add those rows together. Sorting Options (all fields support "ASC"/"DESC"): Available for sorting: total_volume_usd, volume_in_usd, volume_out_usd, interaction_count. The sort is applied inside each wallet's block. Example (every key below is the name the request accepts, and the addresses are real — copy this shape as it stands): { "walletAddresses": [ "0x28c6c06298d514db089934071355e5743bf21d60", "0xd8da6bf26964af9d7eed9e03e53415d37aa96045" ], "chain": "ethereum", "timeRange": {"from": "30D_AGO", "to": "NOW"}, "sourceInput": "Combined", "orderBy": "total_volume_usd", "orderByDirection": "DESC", "perPage": 100 }
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
address_dex_tradesGet a wallet's individual trades on a single chain — DEX swaps (spot) or Hyperliquid perpetual trades, newest first.Reads text others write1 finding
Why it is in this group
- The description's first verb is "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The description is 2,399 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "..., "columns": ["closed_pnl", "fee_usd"], "aggregations": ["sum"] }"
Description, as the server wrote it 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). Use it when the question names one wallet, for example "when did this wallet open, add to, reduce or close its BTC long on Hyperliquid". Chain: one per call ('all'/'evm' unsupported). EVM wallets MUST pass `chain` explicitly (e.g. ethereum, base, arbitrum); non-EVM (e.g. Solana) is auto-detected. Use 'hyperliquid' for Hyperliquid perpetual trades (requires an EVM address). Call once per chain to span multiple networks. A `trader_id` instead of `address` returns the spot swaps of all wallets of a trader, or the Hyperliquid perp position segments with chain `hyperliquid`. Spot columns: Time, Bought / Bought Amount, Sold / Sold Amount, Value USD, Tx Hash. Perp columns: Time, Token, Side, Action, Size, Price, Value USD, Fee USD, Closed PnL, Tx Hash. Sort (`order_by`, asc/desc): timestamp, value. Filter by `valueUsd`, `tokenAddressBought`, or `tokenAddressSold`. On spot chains the token fields take contract addresses. On Hyperliquid they take perp symbols and select Long or Short trades respectively; only one token field is allowed. A page shows at most 25 trades. For every total, min, max, mean, count or list of tokens ("how much did it buy or sell", "total volume", "total PnL", "average trade size", "which tokens"), use `columns` with `aggregations`, also when the trades fit on one page. The tool then computes the result from the raw values of all matching trades. Token amounts are summed per token. Examples: # Latest trades { "address": "0x1f2f10d1c40777ae1da742455c65828ff36df387", "chain": "ethereum", "dateRange": {"from": "7D_AGO", "to": "NOW"} } # How much of each token the wallet bought on one day, all pages { "address": "0x1f2f10d1c40777ae1da742455c65828ff36df387", "chain": "ethereum", "dateRange": {"from": "2026-10-02", "to": "2026-10-02"}, "columns": ["bought_amount"], "aggregations": ["sum"] } # Total closed PnL and fees of Hyperliquid perp trades in 7 days { "address": "0x90dbb196cacf24bd212b377a0dd62eaad5e8151b", "chain": "hyperliquid", "dateRange": {"from": "7D_AGO", "to": "NOW"}, "columns": ["closed_pnl", "fee_usd"], "aggregations": ["sum"] }
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
address_first_funderGet the first address that ever funded an EVM wallet, with the funding transaction hash, chain and timestamp.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 a CEX withdrawal or a wallet the same owner already controls. The funder is resolved across all chains, so no chain argument is needed.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
address_historical_balancesGet historical native coin & token balances of address.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Get historical native coin & token balances of address. For a trader, send trader_id instead of address or entity_id: the daily USD balances of all wallets of the trader. # Query by trader {"trader_id": "5482f9aeb02f67b7", "lookbackDays": 30}
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
address_perp_positionsGet a wallet's Hyperliquid positions and liquidation risk without a portfolio lookup.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Get a wallet's Hyperliquid positions and liquidation risk without a portfolio lookup.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
address_portfolioGet comprehensive portfolio overview for a wallet address or entity.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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': Wallet balances + Hyperliquid positions (skip defi, for fast mode only) - 'all': Wallet balances + DeFi positions + Hyperliquid positions - 'wallet_balances': Only token balances (tokens and native coins across all chains) - 'defi': Only DeFi positions (lending, staking, LP tokens, etc., excluding Hyperliquid) - 'hyperliquid': Only Hyperliquid data — perp positions (with liquidation prices and margin summary) plus HL spot wallet balances For entities (e.g., "Binance", "Paradigm Fund"), only on-chain token balances are returned, aggregated across all addresses associated with the entity. For a trader, send trader_id: the token balances and open Hyperliquid perp positions of all wallets of the trader. This tool provides flexible portfolio analysis in a single request, allowing users to focus on specific aspects of their holdings. The output is pre-formatted markdown that should be presented exactly as returned, preserving all tables, sections, and formatting without reinterpretation. Example Usage: Get full comprehensive portfolio for a wallet: ``` { "walletAddress": "0x28c6c06298d514db089934071355e5743bf21d60", "mode": "all" } ``` Get only DeFi positions: ``` { "walletAddress": "0x28c6c06298d514db089934071355e5743bf21d60", "mode": "defi" } ``` Get only Hyperliquid positions: ``` { "walletAddress": "0x28c6c06298d514db089934071355e5743bf21d60", "mode": "hyperliquid" } ``` Get token balances for an entity: ``` { "entity_id": "Binance" } ``` Get the portfolio of a trader: ``` { "trader_id": "5482f9aeb02f67b7" } ```
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
address_transactionsGet list of 20 MOST RECENT transactions made by an address or an entity (per page).Reads text others writeNo findings
Why it is in this group
- The description's first verb is "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Get list of 20 MOST RECENT transactions made by an address or an entity (per page). Only the latest transactions according to the date range are returned. Provide exactly one of `address`, `entity_id` or `trader_id`. An entity lookup returns transactions across all wallets of that entity and covers at most 7 days. A `trader_id` returns the transfers of all wallets of the trader, at most 366 days. A page shows at most 20 transactions. For every total, min, max, mean, count or list of counterparties or tokens ("how much did it send or receive", "total volume", "who did it send to", "which tokens"), use `columns` with `aggregations`, also when the transactions fit on one page. The tool then computes the result from the raw values of all matching transactions. By default (`min_volume_usd` 1) the tool hides dust, spam and transactions whose tokens have no price. Send `"min_volume_usd": null` only when the user asks for transactions under $1 or for unpriced tokens (airdrops, new tokens, NFTs). Examples: # Latest transactions {"address": "0x1234567890123456789012345678901234567890", "chain": "all"} # USD volume, and tokens sent and received, in 7 days { "address": "CDkCdBbvQfQudgBKunbbqiVYnERKANMfMJqxnVbScskB", "chain": "solana", "dateRange": {"from": "7D_AGO", "to": "NOW"}, "columns": ["volume_usd", "token_amount"], "aggregations": ["sum"] }
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
entity_name_searchSearch Nansen's entity names by a partial name and get back the exact entity names that match.Reads text others writeNo findings
Why it is in this group
- The name "entity_name_search" says "search": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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" -> "Binance 14"). Matching is case-insensitive and matches anywhere in the name. For tokens or addresses use `general_search` instead.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
fund_token_balancesGet the CURRENT token holdings aggregated (not per wallet) across Fund-labelled wallets only, per chain for all chains (default is ['all']) or specific chain(s).Reads text others writeNo findings
Why it is in this group
- The description's first verb is "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Get the CURRENT token holdings aggregated (not per wallet) across Fund-labelled wallets only, per chain for all chains (default is ['all']) or specific chain(s). Funds are a separate cohort from Smart Money: use this for fund-only holdings questions, and smart_traders_and_funds_token_balances for Smart Money as a whole. This is a snapshot of now: it has no date range and no history, and it does not list individual fund wallets. Stablecoins, native tokens and tokens with less than minValueUsd (default $1,000) of combined Fund balance are excluded by default. The default sort is the largest absolute 24h balance change, increases and decreases together. Large percentage changes can come from small positions or one wallet, and balance changes alone do not prove purchases or sales. minValueUsd applies to the current balance, so a token that funds sold to below it does not show in decreases. Which arguments to use: - What funds are buying: balanceChange='increase', orderBy='balance_24h_percent_change', orderByDirection='DESC'. - What funds are trading: two calls, the buying call above and balanceChange='decrease', orderBy='balance_24h_percent_change', orderByDirection='ASC'. - What funds are holding: orderBy='value_usd', orderByDirection='DESC'. - Which tokens have the most fund holders: orderBy='holders_count', orderByDirection='DESC'. - Broad fund overview: also call with orderBy='value_usd' and with orderBy='holders_count', because the largest percentage changes can be small positions or one wallet. - Fund holdings of one token: do not use this tool. Use token_current_top_holders with labelType='top_100_holders' and includeLabels=['Fund'], then add up the balances. A sum of one page covers only the listed wallets.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
general_searchGeneral search tool.Reads text others writeNo findings
Why it is in this group
- The name "general_search" says "search": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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_market_lookup` instead. Nansen MCP does not support NFTs, however check using this tool if the query relates to a token. Regular tokens and NFTs can have the same name. This tool allows you to: - Check if a (fungible) token exists by name, symbol, or contract address - Search information about a token - Trading volume - Contract address and chain information - Market cap and supply data when available - Search information about an entity - Find the address behind a Nansen label (public figure, fund, exchange wallet) - Resolve a domain (.eth, .sol) to its address - Look up premium address labels only on the Nansen research agent
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
get_feedbackRead a Nansen feedback receipt for the same authenticated account.No findings
Why it is in this group
- The name "get_feedback" says "get": a word for reading.
Description, as the server wrote it Read a Nansen feedback receipt for the same authenticated account. Costs zero credits. Lookup uses feedback_id, consumes no report slot, and returns fresh status. Received means saved; reviewed means triaged; closed has a public disposition. No fix or delivery date is promised. Unknown, expired, and other-account IDs return the same not-found response. Never create a replacement report or use another account or an internal server key when lookup fails. Do not redirect failed lookups to unrelated feedback channels.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_feedback_preferencesRead the authenticated account's saved automatic feedback preference.No findings
Why it is in this group
- The name "get_feedback_preferences" says "get": a word for reading.
Description, as the server wrote it Read the authenticated account's saved automatic feedback preference. Free; no report quota. Before a new automatic report about useful Nansen friction, draft a concise report without secrets or unnecessary conversation details and call this tool. Enabled permits sending subject to host and local-deny controls and account rollout. If off, unconfigured or unavailable, show the report and ask first. Refusal, host denial or inability to ask means no submission. An explicit request or approval permits only that report. Never enable the preference automatically. Direct lasting changes to Superapp settings. Reads are fresh, use this account only, and do not authorize another account or server key.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
growth_chain_rankGet chain growth rankings by active addresses, transactions, gas fees and DEX volume.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Get chain growth rankings by active addresses, transactions, gas fees and DEX volume.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
hyperliquid_leaderboardGet Hyperliquid perpetual futures trader leaderboard with performance metrics.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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): realized + unrealized over the date range - **Realized PnL** (USD): net, from positions closed in the range. Being a net total it shows no per-trade outcome, so no win rate can be derived from it or any other column here - **Unrealized PnL** (USD): on positions still open, at the current mark price - **ROI** (%): Total PnL / (traded notional + open notional) — PnL per dollar traded, not return on capital - **Volume** (USD): traded notional; both fills of a position count - **Trades**: number of fills - **Account Value** (USD): only available for the top 500K traders This is an overview of top traders and their headline stats. For a trader's open positions, call `address_portfolio` with `mode='hyperliquid'`. **Sorting**: total_pnl, realized_pnl_usd, unrealized_pnl_usd, roi, volume_usd, total_trades, account_value **Filtering** (from/to): totalPnl (USD), accountValue (USD), roi (a fractional ratio, not the percent shown — pass 0.1 for "10% or better", not 10) Example: ``` { "date": {"from": "7D_AGO", "to": "NOW"}, "accountValue": {"from": 100000, "to": 1000000}, "totalPnl": {"from": 10000}, "order_by": "total_pnl", "orderByDirection": "DESC" } ``` Rank by traded volume instead: `"order_by": "volume_usd"` Notes: - Hyperliquid perpetual futures only - Dates use UTC calendar boundaries, not rolling timestamps. Calendar end dates retain the next-day API boundary. - Null/empty means data is not available — do not read it as zero
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
prediction_market_lookupSearch Polymarket for events and markets by name, topic, URL, or slug.Reads text others writeNo findings
Why it is in this group
- The name "prediction_market_lookup" says "lookup": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "search" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it 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`. - Example: `2026 NCAA Tournament Winner` is an event; `Will Duke win the 2026 NCAA Tournament?` is a market. Detail tools require `marketId`, not `eventId`. **When to use:** - First tool when the user asks about a specific PM topic, event, slug, or Polymarket URL but does not provide `marketId`. - Optionally provide `queryVariant` as a cleaner short keyword version. - Set `includeEventMarkets` to true to also return child markets for the best-matching event. - Do NOT use `general_search` for prediction markets. - Results include current outcome prices, last trade price, and bid/ask inline — for a quick probability check you may not need `prediction_market_ohlcv`. For price *history* or dated moves, still use `prediction_market_ohlcv`. **Query tips:** - Uses Polymarket's search API — natural language queries work well. - Prefer short 1–3 keyword queries for best results. - Avoid broad multi-topic queries like `bitcoin ethereum politics`. **Output rules:** - If lookup returns no suitable market or a mismatched timeframe, say so explicitly — do not silently substitute a nearby market.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
prediction_market_screenerBrowse and sort Polymarket markets, events, or categories.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "browse": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "browse": it reads web pages, which anyone can write.
Description, as the server wrote it 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` instead. **Query tips:** - Literal-style matching on text and slugs, not fuzzy web search. - Prefer one short topic or slug fragment (e.g. `fed cuts`, `zelensky`, `ncaa tournament`). - Do not bundle unrelated topics (e.g. `bitcoin ethereum politics weather`). If a broad question spans several topics, run separate screener queries for each. - If a query returns no rows, do not invent a nearest match — try a narrower topic or say no data was returned. **Output rules:** - Superlatives (highest, leading, biggest, top, trending) must match the shown metric exactly. - Do not infer end dates, rankings, or category leadership from titles alone.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
smart_traders_and_funds_dcasGet Jupiter DCA (dollar-cost-averaging) orders opened by smart traders on Solana, including deposit size, amount spent so far and order status.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Get Jupiter DCA (dollar-cost-averaging) orders opened by smart traders 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 one-off swaps.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
smart_traders_and_funds_dex_tradesGet individual (per wallet, per transaction) DEX trades made by smart traders (EXCLUDES whales, large holders, influencers, etc.) across all chains (default is ['all']) or specific…Reads text others writeNo findings
Why it is in this group
- The description's first verb is "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Get individual (per wallet, per transaction) DEX trades made by smart traders (EXCLUDES whales, large holders, influencers, etc.) across all chains (default is ['all']) or specific chain(s). Use this to see exactly which wallet bought or sold what; use smart_traders_and_funds_netflow for the aggregated view.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
smart_traders_and_funds_historical_token_balancesGet the day-by-day history of aggregated smart trader token balances (EXCLUDES whales, large holders, influencers, etc.) for a date range on base, bnb, ethereum, monad, robinhood o…Reads text others writeNo findings
Why it is in this group
- The description's first verb is "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Get the day-by-day history of aggregated smart trader 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 changed over time; use smart_traders_and_funds_token_balances for the current snapshot. This endpoint uses inclusive UTC calendar dates, not rolling timestamps.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
smart_traders_and_funds_netflowGet aggregated (not per wallet) smart trader (EXCLUDES whales, large holders, influencers, etc.) net USD flow per token over 1h/24h/7d/30d, per chain for all chains (default is ['a…Reads text others writeNo findings
Why it is in this group
- The description's first verb is "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Get aggregated (not per wallet) smart trader (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 money is buying or selling right now; use smart_traders_and_funds_token_balances for what they hold.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
smart_traders_and_funds_perp_tradesGet recent Hyperliquid perpetual futures trades from Smart Money addresses across all tokens.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Get recent Hyperliquid perpetual futures trades from Smart Money addresses across all tokens. For a broad view of Smart Money activity across all tokens, use token_discovery_screener with traderType="sm". **Note:** This endpoint is Hyperliquid-only (perpetual futures data). It returns recent trades only (no date filtering available). Columns returned: - **Time**: Timestamp when the trade occurred (datetime: YYYY-MM-DD HH:MM:SS) - **Side**: Position direction - Long or Short - **Action**: Order action - Add, Reduce, Open, Close - **Token**: Symbol of the perpetual contract - **Size**: Quantity of the perpetual contract (numeric) - **Price USD**: Price per token at time of trade (price formatted) - **Value USD**: Total USD value of the trade (currency formatted) - **Trader**: Nansen label of the trading address - **Address**: Full trading wallet address - **Tx Hash**: Blockchain transaction hash for verification Sorting Options (all fields support "asc"/"desc"): Available for sorting: timestamp, amount, price_usd Examples: # Get recent smart money perp trades (sorted by amount) ``` { "orderBy": "amount", "order_by_direction": "desc" } ``` # Filter by action and side ``` { "action": "Open", "side": "Long" } ```
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
smart_traders_and_funds_token_balancesGet aggregated (not per wallet) smart trader (EXCLUDES whales, large holders, influencers, etc.) token balances and 24h change per chain for all chains (default is ['all'], which q…Reads text others writeNo findings
Why it is in this group
- The description's first verb is "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Get aggregated (not per wallet) smart trader (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). Use filters to narrow down the results.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
token_current_top_holdersGet upto 25 (per page) top holders information for a specific token.Reads text others write2 findings
Why it is in this group
- The description's first verb is "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The description contains a 43-character base64 string.
What this check looks forMatched text
description: "...mode (tokenAddress So11111111111111111111111111111111111111112). For SOL analysis,..."
- Info
The description is 4,969 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...1111111111111111111111111111111111112). For SOL analysis, use perps mode instead."
Description, as the server wrote it 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 money data. **Modes:** - `onchain_tokens` (default): Analyze on-chain tokens by contract address - `perps`: Analyze Hyperliquid perpetual futures by symbol (chain auto-set to "hyperliquid") Columns returned (onchain_tokens mode): - **Address**: Wallet/contract address of the token holder - **Label**: Nansen label (e.g., exchange, whale, etc.) - **Balance**: Current balance held (numeric with K/M/B formatting) - **Balance USD**: USD value of token holdings (currency formatted) - **Ownership %**: Percentage of total token supply owned (percentage, 2 decimal places) - **Sent**: Total tokens sent from this address historically (numeric) - **Received**: Total tokens received by this address historically (numeric) - **24h Change**: Balance change in last 24 hours (numeric, can be negative) - **7d Change**: Balance change in last 7 days (numeric, can be negative) - **30d Change**: Balance change in last 30 days (numeric, can be negative) Columns returned (perps mode): - **Trader Address**: Address of the trader - **Trader Label**: Nansen label for the trader - **Side**: Position direction (Long/Short) - **Position Value USD**: Total USD value of the position (currency formatted) - **Position Size**: Size of the position in tokens (numeric) - **Leverage**: Leverage multiplier (e.g., "20X") - **Leverage Type**: Type of leverage (cross/isolated) - **Entry Price**: Average entry price (price formatted) - **Mark Price**: Current mark price (price formatted) - **Liquidation Price**: Liquidation price (price formatted) - **Funding USD**: Cumulative funding payments (currency formatted) - **Unrealized PnL USD**: Unrealized profit/loss (currency formatted) Sorting Options (default: holding_size desc): onchain_tokens mode: holding_size, total_outflow, total_inflow, balance_change_24h, balance_change_7d, balance_change_30d perps mode: holding_size, side, entry_price, leverage, liquidation_price, funding_usd, upnl_usd Use only a value listed for the selected mode. A value from the wrong mode is not an error: the call falls back to holding_size and the output notes the changed sort. Examples: # On-chain tokens (default mode) ``` { "mode": "onchain_tokens", "chain": "ethereum", "token_address": "0xa0b86a33e6b6c4b3add000b44b3a1234567890ab", "label_type": "top_100_holders" } ``` # Fund holders (general labels; Fund is not a Smart Money label) ``` { "mode": "onchain_tokens", "chain": "ethereum", "token_address": "0xa0b86a33e6b6c4b3add000b44b3a1234567890ab", "label_type": "top_100_holders", "includeLabels": ["Fund"] } ``` # Hyperliquid perpetual futures ``` { "mode": "perps", "token_address": "PENGU", "label_type": "smart_money" } ``` # Find most active senders using filters ``` { "mode": "onchain_tokens", "chain": "ethereum", "token_address": "0xa0b86a33e6b6c4b3add000b44b3a1234567890ab", "label_type": "smart_money", "includeSmartMoneyLabels": ["Smart Trader"], "orderBy": "total_outflow", "order_by_direction": "desc" } ``` # Find biggest accumulators (who received most tokens) ``` { "mode": "onchain_tokens", "chain": "ethereum", "token_address": "0xa0b86a33e6b6c4b3add000b44b3a1234567890ab", "label_type": "whale", "orderBy": "total_inflow", "order_by_direction": "desc" } ``` # Perps mode with filters ``` { "mode": "perps", "token_address": "ETH", "label_type": "smart_money", "side": "Long", "upnlUsd": {"from": 10000}, "positionValueUsd": {"from": 100000}, "orderBy": "holding_size", "order_by_direction": "desc" } ``` **Native-token / stablecoin `orderBy` restriction:** With `labelType='top_100_holders'` (the default), native tokens (`0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee` and native SUI) and stablecoins/pegged tokens support `orderBy='holding_size'` only. To sort such a token by another onchain field, use `labelType='whale'`, `smart_money`, `exchange` or `public_figure` instead. An unsupported combination is not an error: the call falls back to `holding_size` and the output notes the changed sort. **Other `top_100_holders` limits for native tokens:** limited filters (holding_size, total_outflow, total_inflow, address, smart money labels). For advanced filters use a different `labelType` or set `aggregateByEntity=true`. **Does not** work for SOL in onchain_tokens mode (tokenAddress So11111111111111111111111111111111111111112). For SOL analysis, use perps mode instead.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
token_dex_tradesGet DEX trades for a specific token.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Get DEX trades for a specific token. For the trades of one wallet, also on Hyperliquid, use `address_dex_trades`. **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_tokens mode, only ETH is supported among native tokens. For other native tokens (SOL, BTC, BNB, etc.), use perps mode instead.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
token_discovery_screenerGet comprehensive token screening data across multiple blockchain networks with advanced filtering.Reads text others write1 finding
Why it is in this group
- The description's first verb is "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The description is 8,296 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...ERING only, not sorting) Default: orderBy="netflow", orderByDirection="desc""
Description, as the server wrote it 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 mixed spot + hyperliquid request, `page` applies to both the spot and perps sections. A maximum of 5 chains can be specified per request (excess chains are automatically trimmed). This tool helps with token discovery and finding trending tokens by combining different metrics: volume, liquidity, market cap, smart money activity, and token age. **IMPORTANT - Hyperliquid Special Case:** - Hyperliquid chain queries perpetual futures (perps), not spot tokens - When hyperliquid is mixed with other chains, two sections of up to 25 results each are returned - one for spot tokens and one for perps. - For perps, only these filters are supported: volume, buyVolume, sellVolume, openInterest, netflow, nofTraders, traderType - Perps support orderBy='price_change' for every traderType. Prices use completed 5-minute buckets at the timeframe boundaries. - Additional orderBy fields for perps: open_interest, funding (e.g. orderBy 'funding' ascending finds perps that pay longs) - Unsupported filters/orderBy will fallback to defaults INPUT EXAMPLES: # Find tokens which are going up in price. # Added some liquidity filter to remove spam and low quality tokens. ``` { "chains": ["ethereum", "solana", "bnb", "base"], "timeframe": "24h", "liquidity": {"from": 100000}, "nofTraders": {"from": 10}, "orderBy": "price_change", "orderByDirection": "desc" } ``` # Find top stablecoins by market cap ``` { "chains": ["ethereum", "solana", "bnb", "base"], "timeframe": "7d", "sectors": ["Stablecoin"], "orderBy": "market_cap_usd", "orderByDirection": "desc" } ``` # Find AI memecoins with high trading activity { "chains": ["ethereum", "solana", "bnb", "base"], "timeframe": "7d", "sectors": ["AI Meme"], "liquidity": {"from": 100000}, "volume": {"from": 1000000} } # Find DeFi lending tokens { "chains": ["ethereum", "solana", "bnb", "base"], "timeframe": "24h", "sectors": ["DeFi Lending (Money Markets)"], "netflow": {"from": 1000000} } # Find tokens which have a lot of buying activity (high nofBuyers and buyVolume) # Note that we added some filters to remove spam and low quality tokens. We added liquidity filter so that we only surface tokens which we can buy or sell. # We sort by `netflow` descending to get tokens with the most net buying activity. ``` { "chains": ["ethereum", "solana", "bnb", "base"], "timeframe": "24h", "liquidity": {"from": 100000}, "buyVolume": {"from": 1000000}, "marketCapUsd": {"from": 1000000}, "nofBuyers": {"from": 10}, "orderBy": "netflow", "orderByDirection": "desc" } ``` # Find Hyperliquid perps with high open interest and positive net flow ``` { "chains": ["hyperliquid"], "timeframe": "7d", "openInterest": {"from": 100000}, "volume": {"from": 1000000}, "netflow": {"from": 0}, "nofTraders": {"from": 10}, "orderBy": "netflow", "orderByDirection": "desc" } ``` WARNING: To avoid timeouts, it's recommended to: - Use 4 chains or less at a time (API tends to timeout with more chains) - Use shorter timeframes (e.g., 24h or 1h instead of 7d or 30d) Args: Returns: Comprehensive token metrics as markdown. Returns empty string if no tokens found. Columns returned: - **Token Address**: Token address (e.g., 0x1234567890123456789012345678901234567890) - **Symbol**: Token trading symbol (e.g., ETH, BTC, DOGE) - **Chain**: Blockchain network (ethereum, solana, polygon, etc.) - **Price Change**: Price change percentage over the date range (percentage, can be negative) - **Market Cap**: Current market capitalization (currency formatted) - **Fully Diluted Valuation (FDV)**: Market cap if all tokens were circulating (currency formatted) - **FDV/MC Ratio**: Ratio indicating how much supply is locked/vested (numeric, >1 means locked supply) - **USD Volume**: Total trading volume in USD (currency formatted) - **Buy USD Volume**: Total buy volume in USD (currency formatted) - **Sell USD Volume**: Total sell volume in USD (currency formatted) - **Net Flow USD**: Net flow (buys minus sells) in USD (currency formatted, can be negative) - **Traders**: Number of wallets of the selected traderType that traded the token. Without traderType, it counts all traders, not Smart Money (shown only with a nofTraders filter or sort). One wallet can cause most of the Net Flow USD also when Traders is more than 1. Use token_who_bought_sold before you report broad Smart Money buying. - **DEX Liquidity**: Available liquidity for trading (currency formatted) - **Inflow/FDV**: Inflow as percentage of FDV (percentage formatted) - **Outflow/FDV**: Outflow as percentage of FDV (percentage formatted) - **Token Age (Days)**: Days since token was first deployed - **Sectors**: List of token sectors/categories Hyperliquid perps columns (smart-money mode, when `onlySmartTradersAndFunds=true`): - **Net Position** (`LONG $X` / `SHORT $X` / `FLAT`): current net direction. Use this when answering long/short questions. - **Current Longs USD** / **Current Shorts USD**: gross notional on each side; sizing only, not direction. - **Net Position Change**: delta over the timeframe — can be positive while Net Position is still SHORT. Notes: - Positive Net Flow on spot tokens indicates more buying than selling - High FDV/MC Ratio suggests significant locked or vested tokens **Filtering Options** (filters parameter): - **Numeric Ranges**: volume, liquidity, marketCapUsd, netflow, tokenAgeDays, nofTraders, nofBuyers, nofSellers, nofBuys, nofSells, buyVolume, sellVolume, fdv, fdvMcRatio, inflowFdvRatio, outflowFdvRatio, priceChange (spot, in percent) - **Categories**: sectors … [2296 more characters not shown]
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
token_flowsGet hourly token-flow history for ONE holder segment over a date range.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 overall market view. Use it only if user explicitly requests it, or to combine it with other non smart money data. This is a **more granular** tool than `token_recent_flows_summary` and provides the TOTAL flows over the entire time frame broken down by segment. **Modes:** - `onchain_tokens` (default): Analyze on-chain tokens by contract address - `perps`: Analyze Hyperliquid perpetual futures by symbol (chain auto-set to "hyperliquid") — supports native tokens **NOTE:** Native tokens (0xeee…, So111…) cannot be queried in `onchain_tokens` mode. If a native placeholder address is supplied, this tool returns Hyperliquid perpetual-futures flows for that chain's native coin instead (e.g. hyperevm → HYPE, bnb → BNB, base → ETH) and prepends a prominent data-source warning. For native-token wallet-category flows on-chain, use `token_recent_flows_summary`.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
token_infoGet token information — spot on-chain details or Hyperliquid perpetual futures stats.Reads text others write1 finding
Why it is in this group
- The description's first verb is "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The description is 2,001 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...symbols (e.g. BTC, ETH, HYPE) - Both modes use the same `timeframe` parameter"
Description, as the server wrote it 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, buys/sells, buyers/sellers, holders, liquidity). Perps mode: Returns Hyperliquid perp stats — mark price, funding, open interest, buy/sell pressure, trader participation. Returns: Token information as markdown. On-chain tokens fields: - **Market Cap / FDV**: Market capitalization and fully diluted valuation - **Circulating / Total Supply**: Token supply metrics - **Deployed**: When the token was deployed - **DEX Volume (Total / Buy / Sell)**: On-chain DEX trading volume in USD. It does not include CEX volume. - **Buys / Sells**: Number of buy/sell transactions - **Unique Buyers / Sellers**: Distinct trading addresses - **Total Holders**: Number of token holders - **Liquidity**: Available liquidity in USD Perps fields: - **Mark Price**: Current perp mark price - **Price Change**: Change vs previous price - **Max Leverage**: Maximum leverage offered for the perp on Hyperliquid (e.g. "40x") - **Funding Rate (hourly/annualized)**: Current funding rate - **Open Interest**: Total current open interest in USD - **Volume (Total / Buy / Sell)**: Perp volume in USD - **Net Flow (Buy - Sell)**: Buy/sell pressure in USD - **Traders**: Number of traders Example: On-chain tokens (default mode): ``` { "mode": "onchain_tokens", "chain": "ethereum", "tokenAddress": "0xa0b86a33e6b6c4b3add000b44b3a1234567890ab", "timeframe": "1d" } ``` Hyperliquid perps: ``` { "mode": "perps", "tokenAddress": "BTC", "timeframe": "7d" } ``` Notes: - On-chain tokens mode uses contract addresses - Perps mode uses token symbols (e.g. BTC, ETH, HYPE) - Both modes use the same `timeframe` parameter
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
token_jup_dcaGet Jupiter DCA (dollar-cost-averaging) orders opened against a Solana token, with deposit size, amount spent so far, amount accumulated and order status.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 pressure that has not hit the market yet; use token_dex_trades for trades already executed. Solana tokens only.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
token_ohlcvGet OHLCV (Open, High, Low, Close, Volume) price data for a token with automatic interval resolution.Reads text others write1 finding
Why it is in this group
- The description's first verb is "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The description is 2,412 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...: { "from": "7D_AGO", "to": "NOW" } } ```"
Description, as the server wrote it 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"` and use the perp symbol as `tokenAddress` (e.g. "BTC", "HYPE" for native perps; "XYZ:ORDI" for XYZ-namespaced perps — prefix is normalized automatically). Use this tool for current and historical prices. The output starts with the current price. To get **LATEST** price set from to '5MIN_AGO' and to to 'NOW'. Resolution is automatically calculated based on the date range - < 6 hours: 5 minutes - 6 hours - 1 day: 15 minutes - 1-3 days: 30 minutes - 3-7 days: 60 minutes (1 hour) - 7-90 days: Daily - 90+ days: Weekly Columns returned: - **Interval Start**: Timestamp of the start of the interval (datetime: YYYY-MM-DD HH:MM:SS) - **Open**: Opening price of the interval - **High**: Highest price of the interval - **Low**: Lowest price of the interval - **Close**: Closing price of the interval - **Volume USD**: Volume in USD of the interval Additional columns (when includeMarketCap=true): - **Open Market Cap**: Opening market cap in USD - **Close Market Cap**: Closing market cap in USD - **High Market Cap**: Highest market cap in USD - **Low Market Cap**: Lowest market cap in USD Example Usage: Get OHLCV for WETH over the past week (auto-resolution): ``` { "chain": "ethereum", "tokenAddress": "0xba5ddd1f9d7f570dc94a51479a000e3bce967196", "date": { "from": "7D_AGO", "to": "NOW" } } ``` Get OHLCV for WETH over 30 days (will use daily resolution): ``` { "chain": "ethereum", "tokenAddress": "0xba5ddd1f9d7f570dc94a51479a000e3bce967196", "date": { "from": "30D_AGO", "to": "NOW" } } ``` Get OHLCV for WETH for last 20 minutes (will use 5 minute resolution): ``` { "chain": "ethereum", "tokenAddress": "0xba5ddd1f9d7f570dc94a51479a000e3bce967196", "date": { "from": "20MIN_AGO", "to": "NOW" } } ``` Get OHLCV for the BTC Hyperliquid perp over 7 days: ``` { "chain": "hyperliquid", "tokenAddress": "BTC", "date": { "from": "7D_AGO", "to": "NOW" } } ```
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
token_quant_scoresGet Nansen Score Indicators for a token - quantitative risk and reward signals.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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. Returns: Token risk/reward indicators as markdown with interpretation guidance. Token info: - **Market Cap**: Current market cap in USD - **Market Cap Group**: largecap (>$1B), midcap ($100M-$1B), or lowcap (<$100M) - **Is Stablecoin**: Whether token is a stablecoin (some indicators don't apply to stablecoins) Fields returned per indicator: - **Score**: Signal classification (bullish/neutral/bearish for reward; low/medium/high for risk) - **Signal**: Raw numeric value of the indicator - **Percentile**: Rank vs same market cap group (0-100%) - **Last Trigger**: Date when signal was last calculated Indicator types: - **Reward Indicators**: price-momentum, funding-rate, chain-fees, chain-tvl, protocol-fees, trading-range - **Risk Indicators**: btc-reflexivity, liquidity-risk, token-supply-inflation, concentration-risk, cex-flows Notes: - Not all indicators available for every token/chain combination - Percentile compares against same market cap group (largecap >$1B, midcap $100M-$1B, lowcap <$100M)
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
token_recent_flows_summaryGet an on-chain flow snapshot across **ALL** wallet categories in one call.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 segment: 1. Public Figures 2. Top PnL Traders 3. Whales 4. Smart Traders 5. Exchanges 6. Fresh Wallets Inflow and outflow of tokens between the segments is CRITICAL in identifying token price trends. The values provided are **aggregated over the specific lookback period (last 5min, 1d, 7d etc) specified**. If you have SPECIFIC date ranges in mind, use `token_flows` instead. **NOTE** Use `token_flows` for more granular data as it can filter between exact dates and provides HOURLY breakdowns. Returns: Categorized token flow analysis as markdown. For each segment, returns: - Flow amount in USD - Ratio compared to average flow - Number of wallets Format: "{Segment} wallet flow of {amount} ({ratio}x average, from {count} wallets)" Notes: - Positive flow = net buying, negative flow = net selling - For Exchange Flow, positive means more inflow to exchanges, negative means more outflow from exchanges - Categorizes market participants by their historical behavior and characteristics - A wallet can be in more than one segment or perps cohort. Do not add segment flows, cohort exposures or wallet counts as if each segment has different wallets. NOTE: Bitcoin is not supported. DO NOT use this tool for bitcoin. **Modes:** - `onchain_tokens` (default): On-chain token flow intelligence across cohorts - `perps`: Hyperliquid perpetual futures — returns position intelligence (current aggregate long/short/total USD by cohort: Smart Money, Whales, Public Figures). Native tokens (SOL, ETH, BTC etc) are fully supported in perps mode.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
token_sectorsList valid token sectors for token discovery filters.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "list": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it List valid token sectors for token discovery filters.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
token_technical_indicatorsGet a technical-analysis snapshot for a token: SMA(20/50/200), EMA(12/26) and EMA(20/50/200), RSI(14), MACD(12,26,9), Bollinger Bands(20, 2σ), ATR(14), and rolling VWAP(20), comput…Reads text others write1 finding
Why it is in this group
- The description's first verb is "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The description is 2,226 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...erliquid", "tokenAddress": "BTC", "timeframe": "4h" } ```"
Description, as the server wrote it Get a technical-analysis snapshot for a token: SMA(20/50/200), EMA(12/26) and EMA(20/50/200), RSI(14), MACD(12,26,9), Bollinger Bands(20, 2σ), ATR(14), and rolling VWAP(20), computed from the last 1,000 closed candles at an explicit timeframe. Supports EVM chains and Solana for on-chain tokens, AND Hyperliquid perpetual futures. For Hyperliquid perps, pass `chain="hyperliquid"` and use the perp symbol as `tokenAddress` (e.g. "BTC", "HYPE" for native perps; "XYZ:ORDI" for XYZ-namespaced perps — prefix is normalized automatically). **YOU MUST USE THIS** for technical analysis instead of computing indicators from raw `token_ohlcv` candles — it uses far more history (1,000 closed candles) and charting-platform conventions (SMA-seeded EMA, Wilder RSI/ATR, population-σ Bollinger). Timeframes (explicit, no auto-resolution): - 5m / 15m / 30m / 1h / 4h: intraday and short-horizon analysis - 1d (default): swing/position horizon - 1w: long-term trend Output: a snapshot header (candles used, date range, last close, 5-candle price change) plus one row per indicator, each with a 5-candle trend delta so you can read direction, not just level: - **SMA 20/50/200**: values, price vs each, MA slopes - **EMA 12/26**: values, spread %, widening/narrowing - **EMA 20/50/200**: values, price vs each - **RSI(14)**: level, prior candle, 5-candle change - **MACD(12,26,9)**: line/signal/histogram, rising/falling, candles since signal cross - **Bollinger(20,2σ)**: bands, %B, bandwidth and its change - **ATR(14)**: value and % of price (volatility), rising/falling - **VWAP(20)**: value, price vs VWAP Indicators without enough closed-candle history render as n/a (e.g. SMA200 on young tokens); the candle count used is always reported. VWAP is n/a on Hyperliquid 5m-1h timeframes (volume is NULL in those views) — use 4h or 1d for Hyperliquid VWAP. Example Usage: Daily technical snapshot for WETH: ``` { "chain": "ethereum", "tokenAddress": "0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2", "timeframe": "1d" } ``` 4-hour snapshot for the BTC Hyperliquid perp: ``` { "chain": "hyperliquid", "tokenAddress": "BTC", "timeframe": "4h" } ```
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
token_who_bought_soldGet net buyers or net sellers of a token on DEX (Decentralised Exchanges) only.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Get net buyers or net sellers of 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 more. Returns: Aggregated buyer/seller activity as markdown. Returns empty string if no trading data found. Columns returned: - **Address**: Trader's wallet address - **Label**: Nansen label of the address - **Bought Token Volume**: Total quantity of tokens purchased - **Sold Token Volume**: Total quantity of tokens sold - **Total Token Volume**: Bought plus sold - **Net Bought / Net Sold Token Volume**: Bought minus sold for BUY results, or sold minus bought for SELL results - **Bought Volume USD**: USD value of all token purchases - **Sold Volume USD**: USD value of all token sales - **Total Volume USD**: Bought plus sold - **Net Bought / Net Sold Volume USD**: Bought minus sold for BUY results, or sold minus bought for SELL results Sorting Options: Sort ASC or DESC by net_token_volume (default: biggest net buyers or sellers first), token_trade_volume (total volume: most active traders, such as market-making bots), bought_token_volume, or sold_token_volume. Notes: - buy_or_sell parameter filters for "BUY" (net buyers) or "SELL" (net sellers), decided by net token amount - Net USD volume can be negative while net token volume is zero or positive, because USD is priced per trade - min_trade_volume_usd applies to the requested side: bought USD for BUY, sold USD for SELL - Machine-readable rows: token_trade_volume / trade_volume_usd are total volume (bought + sold); net_token_volume / net_volume_usd are net volume. - Aggregates all trading activity within the specified time range
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
transaction_lookupGet transaction details and token transfers for a transaction hash.Reads text others writeNo findings
Why it is in this group
- The name "transaction_lookup" says "lookup": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Get transaction details and token transfers for a transaction hash. No contract function is shown. For it, use the Method column of `address_transactions` for the From address. Returns a markdown table with transaction details and token transfers. Only EVM transaction hashes are supported.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
wallet_pnl_for_tokenGet PnL stats for a specific token traded by the input address during a specific date range.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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. Provide exactly one of `walletAddress` or `trader_id`. For a trader, send `trader_id`: the result adds up all wallets of the trader and lists the newest buys and sells of the token. Chain: pass 'hyperliquid' for a perp coin — there `tokenAddress` is the perp SYMBOL (e.g. 'BTC', 'HYPE', 'xyz:CL'), not a contract address. Every other chain expects a token contract address.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
wallet_pnl_summaryGet aggregate stats of overall realized PnL for the input address.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 address, reports spot/on-chain and Hyperliquid perp results as separate sections (never summed). For a single named chain, this tool covers realized PnL only. Use this tool for analysing the performance of the wallet over a time period. For a trader, send trader_id instead of walletAddress: the spot PnL of all wallets of the trader and a separate Hyperliquid perp section. # Query by trader {"trader_id": "5482f9aeb02f67b7", "dateRange": {"from": "30D_AGO", "to": "NOW"}}
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write51
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:08 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 15
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://mcp.nansen.ai/.well-known/oauth-protected-resource
- Authorization servers
- https://idp.nansen.ai
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- no
- Client ID metadata documents
- yes
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 15 tools that change things (2 irreversible, 13 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.nansen.ai/ra/mcp/: tools/list returned 54 tools to an anonymous client, including token_transfers (irreversible), token_pnl_leaderboard (irreversible), submit_feedback (write), smart_traders_and_funds_pnl_leaderboard (write), nansen_score_top_tokens (write) and 10 more
Findings
Matches of fixed checks, with the text they matched.
The description contains a 43-character base64 string.
What this check looks forMatched text
description: "...mode (tokenAddress So11111111111111111111111111111111111111112). For SOL analysis,..."
- Warntoken_transfers
The description contains a 42-character base64 string.
What this check looks forMatched text
description: "..."fromAddress": "0x2b060b9c89B8aD04e5E1fD40F1f327e41DD32c72", "columns":..."
- Warntoken_transfers
The description contains a 42-character base64 string.
What this check looks forMatched text
description: "..."toAddress": "0x2b060b9c89B8aD04e5E1fD40F1f327e41DD32c72", "min_amount..."
- Warntoken_transfers
The description contains a 42-character base64 string.
What this check looks forMatched text
description: "..."fromAddress": "0x2b060b9c89B8aD04e5E1fD40F1f327e41DD32c72", "orderBy":..."
- Warntoken_transfers
The server marks "token_transfers" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "token_transfers" says "transfer": a word for a change that another call does not undo.
The server marks "token_pnl_leaderboard" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The input addresses people (input.request.dateRange.to): what it sends cannot be taken back.
Show 10 more findingsShow fewer
- Warnaddress_labels
The server marks "address_labels" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "address_labels" says "label": a word for a change.
- Infosubmit_feedback
The input schema at properties.request.properties.endpoint.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.request.properties.endpoint.description: "...about. Do not include a query string or credentials."
The description is 4,969 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...1111111111111111111111111111111111112). For SOL analysis, use perps mode instead."
- Infotoken_transfers
The description is 7,329 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...*Smart Money*) - transferValueUsd filters by USD value at time of transaction"
The description is 4,040 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...otherwise you will miss data. ** This tool does not support hyperevm as chain **"
The description is 8,296 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...ERING only, not sorting) Default: orderBy="netflow", orderByDirection="desc""
- Infotoken_ohlcv
The description is 2,412 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...: { "from": "7D_AGO", "to": "NOW" } } ```"
The description is 2,226 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...erliquid", "tokenAddress": "BTC", "timeframe": "4h" } ```"
- Infotoken_info
The description is 2,001 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...symbols (e.g. BTC, ETH, HYPE) - Both modes use the same `timeframe` parameter"
The description is 2,399 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "..., "columns": ["closed_pnl", "fee_usd"], "aggregations": ["sum"] }"
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools54 changed.~54 changedView diff
- Changed:address_counterpartiesOnly readsdescriptioninputSchemaannotations
- Changed:address_counterparties_batchOnly readsinputSchemaannotations
- Changed:address_dex_tradesOnly readsdescriptioninputSchemaannotations
- Changed:address_first_funderOnly readsannotations
- Changed:address_historical_balancesOnly readsdescriptioninputSchemaannotations
- Changed:address_labelsChanges thingsannotations
- Changed:address_perp_positionsOnly readsannotations
- Changed:address_portfolioOnly readsdescriptioninputSchemaannotations
- Changed:address_related_addressesOnly readsinputSchemaannotations
- Changed:address_transactionsOnly readsdescriptioninputSchemaannotations
- Changed:entity_name_searchOnly readsannotations
- Changed:fund_token_balancesOnly readsdescriptionannotations
- Changed:general_searchOnly readsdescriptioninputSchemaannotations
- Changed:get_feedbackOnly readsinputSchemaannotations
- Changed:get_feedback_preferencesOnly readsinputSchemaannotations
- Changed:growth_chain_rankOnly readsannotations
- Changed:hyperliquid_leaderboardOnly readsinputSchemaannotations
- Changed:nansen_score_top_tokensChanges thingsannotations
- Changed:prediction_market_address_pnlChanges thingsannotations
- Changed:prediction_market_address_summaryChanges thingsannotations
- Changed:prediction_market_address_tradesChanges thingsannotations
- Changed:prediction_market_lookupOnly readsannotations
- Changed:prediction_market_ohlcvChanges thingsannotations
- Changed:prediction_market_orderbookChanges thingsannotations
- Changed:prediction_market_pnl_leaderboardChanges thingsannotations
- Changed:prediction_market_position_detailChanges thingsannotations
- Changed:prediction_market_screenerOnly readsannotations
- Changed:prediction_market_top_holdersChanges thingsannotations
- Changed:prediction_market_tradesChanges thingsannotations
- Changed:smart_traders_and_funds_dcasOnly readsinputSchemaannotations
- Changed:smart_traders_and_funds_dex_tradesOnly readsinputSchemaannotations
- Changed:smart_traders_and_funds_historical_token_balancesOnly readsinputSchemaannotations
- Changed:smart_traders_and_funds_netflowOnly readsinputSchemaannotations
- Changed:smart_traders_and_funds_perp_tradesOnly readsdescriptioninputSchemaannotations
- Changed:smart_traders_and_funds_pnl_leaderboardChanges thingsinputSchemaannotations
- Changed:smart_traders_and_funds_token_balancesOnly readsinputSchemaannotations
- Changed:submit_feedbackChanges thingsinputSchema
- Changed:token_current_top_holdersOnly readsdescriptioninputSchemaannotations
- Changed:token_dex_tradesOnly readsdescriptioninputSchemaannotations
- Changed:token_discovery_screenerOnly readsdescriptioninputSchemaannotations
- Changed:token_flowsOnly readsinputSchemaannotations
- Changed:token_infoOnly readsdescriptioninputSchemaannotations
- Changed:token_jup_dcaOnly readsinputSchemaannotations
- Changed:token_ohlcvOnly readsdescriptioninputSchemaannotations
- Changed:token_pnl_leaderboardCan't be undoneinputSchemaannotations
- Changed:token_quant_scoresOnly readsannotations
- Changed:token_recent_flows_summaryOnly readsinputSchemaannotations
- Changed:token_sectorsOnly readsannotations
- Changed:token_technical_indicatorsOnly readsdescriptioninputSchemaannotations
- Changed:token_transfersCan't be undoneinputSchemaannotations
- Changed:token_who_bought_soldOnly readsinputSchemaannotations
- Changed:transaction_lookupOnly readsdescriptioninputSchemaannotations
- Changed:wallet_pnl_for_tokenOnly readsdescriptioninputSchemaannotations
- Changed:wallet_pnl_summaryOnly readsdescriptioninputSchemaannotations
Tools1 added, 47 changed.+1 added~47 changedView diff
- Added:fund_token_balancesOnly reads
- Changed:address_counterpartiesOnly readsinputSchema
- Changed:address_counterparties_batchOnly readsinputSchema
- Changed:address_dex_tradesOnly readsdescriptioninputSchema
- Changed:address_first_funderOnly readsinputSchema
- Changed:address_historical_balancesOnly readsinputSchema
- Changed:address_perp_positionsOnly readsinputSchema
- Changed:address_portfolioOnly readsdescriptioninputSchema
- Changed:address_related_addressesOnly readsinputSchema
- Changed:address_transactionsOnly readsdescriptioninputSchema
- Changed:general_searchOnly readsdescription
- Changed:growth_chain_rankOnly readsinputSchema
- Changed:hyperliquid_leaderboardOnly readsinputSchema
- Changed:nansen_score_top_tokensChanges thingsinputSchema
- Changed:prediction_market_address_pnlChanges thingsinputSchema
- Changed:prediction_market_address_summaryChanges thingsinputSchema
- Changed:prediction_market_address_tradesChanges thingsinputSchema
- Changed:prediction_market_lookupOnly readsinputSchema
- Changed:prediction_market_ohlcvChanges thingsinputSchema
- Changed:prediction_market_orderbookChanges thingsinputSchema
- Changed:prediction_market_pnl_leaderboardChanges thingsinputSchema
- Changed:prediction_market_position_detailChanges thingsinputSchema
- Changed:prediction_market_screenerOnly readsinputSchema
- Changed:prediction_market_top_holdersChanges thingsinputSchema
- Changed:prediction_market_tradesChanges thingsinputSchema
- Changed:smart_traders_and_funds_dcasOnly readsdescriptioninputSchema
- Changed:smart_traders_and_funds_dex_tradesOnly readsdescriptioninputSchema
- Changed:smart_traders_and_funds_historical_token_balancesOnly readsdescriptioninputSchema
- Changed:smart_traders_and_funds_netflowOnly readsdescriptioninputSchema
- Changed:smart_traders_and_funds_perp_tradesOnly readsinputSchema
- Changed:smart_traders_and_funds_pnl_leaderboardChanges thingsdescriptioninputSchema
- Changed:smart_traders_and_funds_token_balancesOnly readsdescriptioninputSchema
- Changed:submit_feedbackChanges thingsdescriptioninputSchema
- Changed:token_current_top_holdersOnly readsdescriptioninputSchema
- Changed:token_dex_tradesOnly readsinputSchema
- Changed:token_discovery_screenerOnly readsdescriptioninputSchema
- Changed:token_flowsOnly readsinputSchema
- Changed:token_infoOnly readsinputSchema
- Changed:token_jup_dcaOnly readsinputSchema
- Changed:token_ohlcvOnly readsinputSchema
- Changed:token_pnl_leaderboardCan't be undoneinputSchema
- Changed:token_quant_scoresOnly readsinputSchema
- Changed:token_recent_flows_summaryOnly readsdescriptioninputSchema
- Changed:token_technical_indicatorsOnly readsinputSchema
- Changed:token_transfersCan't be undonedescriptioninputSchema
- Changed:token_who_bought_soldOnly readsdescriptioninputSchema
- Changed:wallet_pnl_for_tokenOnly readsinputSchema
- Changed:wallet_pnl_summaryOnly readsinputSchema
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http nansen https://mcp.nansen.ai/ra/mcp/ --header 'NANSEN-API-KEY: <your-nansen-api-key>'claude mcp add --transport http nansen https://mcp.nansen.ai/ra/mcp/ --header 'NANSEN-API-KEY: <your-nansen-api-key>'Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__nansen__get_feedback_preferences",
"mcp__nansen__get_feedback",
"mcp__nansen__smart_traders_and_funds_token_balances",
"mcp__nansen__smart_traders_and_funds_perp_trades",
"mcp__nansen__smart_traders_and_funds_netflow",
"mcp__nansen__smart_traders_and_funds_dex_trades",
"mcp__nansen__smart_traders_and_funds_dcas",
"mcp__nansen__smart_traders_and_funds_historical_token_balances",
"mcp__nansen__fund_token_balances",
"mcp__nansen__token_current_top_holders",
"mcp__nansen__token_dex_trades",
"mcp__nansen__token_flows",
"mcp__nansen__token_who_bought_sold",
"mcp__nansen__token_recent_flows_summary",
"mcp__nansen__token_discovery_screener",
"mcp__nansen__token_ohlcv",
"mcp__nansen__token_technical_indicators",
"mcp__nansen__token_info",
"mcp__nansen__token_quant_scores",
"mcp__nansen__hyperliquid_leaderboard",
"mcp__nansen__token_jup_dca",
"mcp__nansen__address_historical_balances",
"mcp__nansen__address_related_addresses",
"mcp__nansen__address_counterparties",
"mcp__nansen__address_counterparties_batch",
"mcp__nansen__address_transactions",
"mcp__nansen__address_dex_trades",
"mcp__nansen__address_perp_positions",
"mcp__nansen__wallet_pnl_for_token",
"mcp__nansen__wallet_pnl_summary",
"mcp__nansen__address_first_funder",
"mcp__nansen__address_portfolio",
"mcp__nansen__general_search",
"mcp__nansen__entity_name_search",
"mcp__nansen__token_sectors",
"mcp__nansen__growth_chain_rank",
"mcp__nansen__transaction_lookup",
"mcp__nansen__prediction_market_lookup",
"mcp__nansen__prediction_market_screener"
],
"ask": [
"mcp__nansen__submit_feedback",
"mcp__nansen__smart_traders_and_funds_pnl_leaderboard",
"mcp__nansen__token_transfers",
"mcp__nansen__token_pnl_leaderboard",
"mcp__nansen__nansen_score_top_tokens",
"mcp__nansen__address_labels",
"mcp__nansen__prediction_market_ohlcv",
"mcp__nansen__prediction_market_orderbook",
"mcp__nansen__prediction_market_top_holders",
"mcp__nansen__prediction_market_trades",
"mcp__nansen__prediction_market_pnl_leaderboard",
"mcp__nansen__prediction_market_position_detail",
"mcp__nansen__prediction_market_address_trades",
"mcp__nansen__prediction_market_address_summary",
"mcp__nansen__prediction_market_address_pnl"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as nansen. Review it before you use it.
Capability tags behind 52 rules
- mcp__nansen__submit_feedback outbound
- mcp__nansen__smart_traders_and_funds_token_balances untrusted-input
- mcp__nansen__smart_traders_and_funds_perp_trades untrusted-input
- mcp__nansen__smart_traders_and_funds_netflow untrusted-input
- mcp__nansen__smart_traders_and_funds_dex_trades untrusted-input
- mcp__nansen__smart_traders_and_funds_dcas untrusted-input
- mcp__nansen__smart_traders_and_funds_historical_token_balances untrusted-input
- mcp__nansen__smart_traders_and_funds_pnl_leaderboard untrusted-input
- mcp__nansen__fund_token_balances untrusted-input
- mcp__nansen__token_current_top_holders untrusted-input
- mcp__nansen__token_dex_trades untrusted-input
- mcp__nansen__token_transfers untrusted-input
- mcp__nansen__token_flows untrusted-input
- mcp__nansen__token_pnl_leaderboard untrusted-input
- mcp__nansen__token_who_bought_sold untrusted-input
- mcp__nansen__token_recent_flows_summary untrusted-input
- mcp__nansen__token_discovery_screener untrusted-input
- mcp__nansen__token_ohlcv untrusted-input
- mcp__nansen__token_technical_indicators untrusted-input
- mcp__nansen__token_info untrusted-input
- mcp__nansen__token_quant_scores untrusted-input
- mcp__nansen__nansen_score_top_tokens untrusted-input
- mcp__nansen__hyperliquid_leaderboard untrusted-input
- mcp__nansen__token_jup_dca untrusted-input
- mcp__nansen__address_historical_balances untrusted-input
- mcp__nansen__address_labels untrusted-input
- mcp__nansen__address_related_addresses untrusted-input
- mcp__nansen__address_counterparties untrusted-input
- mcp__nansen__address_counterparties_batch untrusted-input
- mcp__nansen__address_transactions untrusted-input
- mcp__nansen__address_dex_trades untrusted-input
- mcp__nansen__address_perp_positions untrusted-input
- mcp__nansen__wallet_pnl_for_token untrusted-input
- mcp__nansen__wallet_pnl_summary untrusted-input
- mcp__nansen__address_first_funder untrusted-input
- mcp__nansen__address_portfolio untrusted-input
- mcp__nansen__general_search untrusted-input
- mcp__nansen__entity_name_search untrusted-input
- mcp__nansen__token_sectors untrusted-input
- mcp__nansen__growth_chain_rank untrusted-input
- mcp__nansen__transaction_lookup untrusted-input
- mcp__nansen__prediction_market_lookup untrusted-input
- mcp__nansen__prediction_market_screener untrusted-input
- mcp__nansen__prediction_market_ohlcv untrusted-input
- mcp__nansen__prediction_market_orderbook untrusted-input
- mcp__nansen__prediction_market_top_holders untrusted-input
- mcp__nansen__prediction_market_trades untrusted-input
- mcp__nansen__prediction_market_pnl_leaderboard untrusted-input
- mcp__nansen__prediction_market_position_detail untrusted-input
- mcp__nansen__prediction_market_address_trades untrusted-input
- mcp__nansen__prediction_market_address_summary untrusted-input
- mcp__nansen__prediction_market_address_pnl untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.nansen-ai/nansen-mcp/verify?hash=f8ff6ea638c89b812dcdba426583ccf802f085de282a2642ac6fbcecd4a54cd7" | jq -e '.changed == false'Pinned hash f8ff6ea638c8, from Nov 21, 2026, 01:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.nansen-ai/nansen-mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.nansen-ai/nansen-mcp)Source: MCP Registry. Synced Oct 21, 2026, 18:42 UTC.
Nansen MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Nansen MCP server safe?
- No scan can promise that. What its definitions show: 54 tools, 15 of which can change, send or delete something, and 16 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Nansen MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Nansen MCP server do things that cannot be undone?
- Yes. 2 tools can send, pay, publish or merge: token_transfers and token_pnl_leaderboard.
What tools does the Nansen MCP server have?
- 54 tools: 2 irreversible, 13 write, 39 read. token_transfers, token_pnl_leaderboard, submit_feedback, smart_traders_and_funds_pnl_leaderboard, nansen_score_top_tokens, address_labels, prediction_market_ohlcv, prediction_market_orderbook and 46 more.
Does the Nansen MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Nansen MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): submit_feedback.
Has the Nansen MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 21, 2026. Every change is on this page and in its Atom feed.