Adaption
Import, adapt and expand training datasets, then launch AutoScientist fine-tuning runs from an AI agent.
Track Smart Money, token flows and wallet PnL across chains from Claude.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Nansen MCP server brings Nansen's onchain analytics into Claude: token data and risk scores, Smart Money and whale flows, wallet portfolios, PnL and counterparties across chains including Ethereum, Solana, Base and Hyperliquid. Its 13 data tools read and spend Nansen API credits. One feedback tool saves reports with Nansen. Nothing can trade or move funds.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
nansen:read, yet submit_feedback writes a report to Nansen.Nansen credits. Nansen's Claude guide says data-tool calls spend the API credits of the Nansen account you sign in with, not your Claude subscription, and are subject to Nansen rate limits. One prompt can trigger several calls, and costs vary widely: search is free, most lookups cost one credit, and on-chain top-holder queries cost 150 and need Pro. The three feedback tools cost nothing.
No. Nansen's connector documentation says connectors cannot trade, sign transactions, move assets or change your saved feedback preference. The 13 data tools read public on-chain data and Nansen labels. The only write is a feedback tool that saves a product report with Nansen. The connector requests one OAuth scope, read-only by name, and asks for no wallet keys.
Because the operation costs more than the balance on the account used at sign-in. Nansen's troubleshooting table says to check that account's API credits on the Nansen API page. Expensive calls are the usual cause: on-chain top-holder lookups cost 150 credits each. If you signed in with the wrong Nansen account, reconnect and choose the account whose credits you intend to use.
Usually because Nansen is not switched on for that conversation. Nansen's troubleshooting advice is to turn it on in the conversation's tools menu and explicitly ask Claude to use Nansen. Its guide adds that a visible tool list or a general answer about a token does not prove account access; a real check is a token lookup that returns Nansen data or a tool error.
Because connectors use a curated server. Nansen's documentation says Claude, ChatGPT and Grok all connect to the same curated endpoint with 13 data tools and three feedback tools. The full Nansen MCP catalog is only available through a separate endpoint authenticated with a Nansen API key. You can add both in Claude Code under different server names if you need the wider set.
POST initialize against https://mcp.nansen.ai/ra/connector-curated/mcp (2026-11-18): HTTP 401 with WWW-Authenticate carrying scope nansen:read. The RFC 9728 descriptor at https://mcp.nansen.ai/.well-known/oauth-protected-resource/ra/connector-curated/mcp returned HTTP 200 naming https://idp.nansen.ai as the authorization server. · retrieved 2026-11-18docs/marketing/data/anthropic-directory-2026-11-17.json. Source for the partner tier, the 2026-09-25 listing date, the endpoint and the 16 tool names. Its documentation value, https://docs.nansen.ai/mcp/claude, returned HTTP 307 to the Claude connector guide above. · retrieved 2026-11-17Connect Nansen once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.