Nansen
REMOTE · MCP.NANSEN.AI
Blockchain analytics API for AI agents. Smart Money signals, wallet profiling, token analytics.
Available components
Last scanned (5 hours ago)
Scores higher than 69% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability53
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 18998 tokens (~358/item across 53 items; 53 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 93% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 53 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 54 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 4 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “address_portfolio” rewrote its description, which is the text the model reads security
- 3 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “address_dex_trades” rewrote its description, which is the text the model reads security
- Tool “address_transactions” rewrote its description, which is the text the model reads security
- 2 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “token_transfers” rewrote its description, which is the text the model reads security
- 1 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 31 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “smart_traders_and_funds_dcas” rewrote its description, which is the text the model reads security
- Tool “smart_traders_and_funds_dex_trades” rewrote its description, which is the text the model reads security
- Tool “smart_traders_and_funds_historical_token_balances” rewrote its description, which is the text the model reads security
- Tool “smart_traders_and_funds_netflow” rewrote its description, which is the text the model reads security
- Tool “smart_traders_and_funds_pnl_leaderboard” rewrote its description, which is the text the model reads security
- Tool “smart_traders_and_funds_token_balances” rewrote its description, which is the text the model reads security
- Tool “token_current_top_holders” rewrote its description, which is the text the model reads security
- Tool “token_who_bought_sold” rewrote its description, which is the text the model reads security
- 30 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “token_discovery_screener” rewrote its description, which is the text the model reads security
- Tool “token_recent_flows_summary” rewrote its description, which is the text the model reads security
- 29 Oct 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- Tool coverage: 28% → 93% ▲ functional
- “address_dex_trades” reworded the description of “request” cosmetic
- “address_first_funder” reworded the description of “request” cosmetic
- “address_portfolio” reworded the description of “request” cosmetic
- “address_transactions” reworded the description of “request” cosmetic
- “hyperliquid_leaderboard” reworded the description of “request” cosmetic
- “nansen_score_top_tokens” reworded the description of “request” cosmetic
- “prediction_market_address_pnl” reworded the description of “request” cosmetic
- “prediction_market_address_summary” reworded the description of “request” cosmetic
- “prediction_market_address_trades” reworded the description of “request” cosmetic
- “prediction_market_lookup” reworded the description of “request” cosmetic
- “prediction_market_ohlcv” reworded the description of “request” cosmetic
- “prediction_market_orderbook” reworded the description of “request” cosmetic
- “prediction_market_pnl_leaderboard” reworded the description of “request” cosmetic
- “prediction_market_position_detail” reworded the description of “request” cosmetic
- “prediction_market_screener” reworded the description of “request” cosmetic
- “prediction_market_top_holders” reworded the description of “request” cosmetic
- “prediction_market_trades” reworded the description of “request” cosmetic
- “smart_traders_and_funds_dcas” reworded the description of “request” cosmetic
- “smart_traders_and_funds_dex_trades” reworded the description of “request” cosmetic
- “smart_traders_and_funds_historical_token_balances” reworded the description of “request” cosmetic
- “smart_traders_and_funds_netflow” reworded the description of “request” cosmetic
- “smart_traders_and_funds_perp_trades” reworded the description of “request” cosmetic
- “smart_traders_and_funds_pnl_leaderboard” reworded the description of “request” cosmetic
- “smart_traders_and_funds_token_balances” reworded the description of “request” cosmetic
- “token_current_top_holders” reworded the description of “request” cosmetic
- “token_discovery_screener” reworded the description of “request” cosmetic
- “token_info” reworded the description of “request” cosmetic
- “token_jup_dca” reworded the description of “request” cosmetic
- “token_ohlcv” reworded the description of “request” cosmetic
- “token_pnl_leaderboard” reworded the description of “request” cosmetic
- “token_quant_scores” reworded the description of “request” cosmetic
- “token_recent_flows_summary” reworded the description of “request” cosmetic
- “token_technical_indicators” reworded the description of “request” cosmetic
- “token_transfers” reworded the description of “request” cosmetic
- “token_who_bought_sold” reworded the description of “request” cosmetic
- “wallet_pnl_for_token” reworded the description of “request” cosmetic
- “wallet_pnl_summary” reworded the description of “request” cosmetic
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://mcp.nansen.ai/ra/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.nansen.ai | CN=WR3,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | RSA 2048 | SHA256-RSA | 2155a5ee509bbab6120e0b7e3ad20e82 |
| SANs: mcp.nansen.ai | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.nansen.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| nansen.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.nansen.ai/ra/mcp/ | Verified | 200 | |
| http (plaintext) | http://mcp.nansen.ai/ra/mcp/ | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
transaction_lookup Looking up transaction details ~31
Get comprehensive transaction details including token transfers.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
| transaction_hash | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
wallet_pnl_for_token Calculating token performance ~124
Get PnL stats for a specific token traded by the input address during a specific date range. Use this tool for analysing the performance of the wallet for the specific token over a time period. Chain: pass 'hyperliquid' for a perp coin — there `tokenAddress` is the perp SYMBOL (e.g. 'BTC', 'HYPE', 'xyz:CL'), not a contract address. Every other chain expects a token contract address.
| Name | Type | Req | Description |
|---|---|---|---|
| request | object | yes | Complete request for wallet PnL for token (flattened). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
wallet_pnl_summary Analyzing wallet performance ~136
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.
| Name | Type | Req | Description |
|---|---|---|---|
| request | object | yes | Complete request for wallet PnL summary (flattened). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the Nansen MCP server?
Nansen is a hosted endpoint at https://mcp.nansen.ai/ra/mcp/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.nansen.ai
claude mcp add --transport http nansen-ai-nansen-mcp 'https://mcp.nansen.ai/ra/mcp/'
What is the Nansen MCP server?
Nansen is an MCP server listed in the public MCP registry as io.github.nansen-ai/nansen-mcp. Blockchain analytics API for AI agents. Smart Money signals, wallet profiling, token analytics. This page covers its hosted endpoint (https://mcp.nansen.ai/ra/mcp/).
Is the Nansen MCP server safe to use?
Nansen scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Nansen MCP server expose?
Nansen exposes 53 tools: get_feedback_preferences, submit_feedback, get_feedback, smart_traders_and_funds_token_balances, smart_traders_and_funds_perp_trades, and 48 more. Their descriptions and schemas cost roughly 18,906 tokens of context every time the server is loaded.
Does the Nansen MCP server require authentication?
No. We connected to Nansen without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Nansen MCP server still maintained?
Nansen is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.