Compatible with every major AI agent and IDE
What is the Nansen (Blockchain Analytics) MCP Server?
Connect your Nansen API to any AI agent to unlock deep on-chain insights through natural language. Nansen provides the data that helps investors and teams identify opportunities and perform due diligence on-chain.
Key Capabilities
- Smart Money Tracking — Monitor where the most sophisticated on-chain entities are moving their capital with netflow and holdings tools.
- Wallet Profiling — Inspect any address or entity to see current balances, historical snapshots, and behavioral labels.
- PnL Analysis — Calculate aggregate profit and loss for specific wallets or deep dive into performance for individual tokens.
- DEX & Perp Activity — Track real-time trading on decentralized exchanges and perpetual platforms like Hyperliquid.
- Entity Search — Quickly find tokens, entities, or contract addresses by name or symbol.
How it works
- Subscribe to this server
- Enter your Nansen API Key
- Start querying blockchain data from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Crypto Researchers — identify emerging trends and whale movements without manual dashboard navigation.
- Traders — monitor Smart Money flows and PnL metrics directly from their workspace.
- Developers — integrate on-chain labels and balance data into their development workflow.
Built-in capabilities (48)
Deep multi-step analysis and synthesis
Low-latency streamed answers for simple research questions
Most profitable Hyperliquid traders
Tier lookup for a wallet on the Nansen points leaderboard
Paginated Nansen points leaderboard
Track DeFi positions across protocols
Win rate, PnL, and wallet age in prediction markets
Stats for market categories (Politics, Crypto, etc.)
Browse groups of related prediction markets
Browse and filter all prediction markets
1-hour price history candles for prediction markets
Real-time bid/ask depth for prediction markets
Total PnL for a trader in prediction markets
Profitability rankings for a prediction market
Granular holder positions for prediction markets
Largest conviction holders in prediction markets
All trades for a specific wallet in prediction markets
Recent trades for a specific prediction market
Top addresses/entities interacted with
Current token balances for an address or entity
Historical holding snapshots for an address
Non-premium labels (ENS, behavioral)
Real-time Hyperliquid positions
Hyperliquid trade history
Detailed PnL for a specific address and token
Aggregate PnL and top profitable tokens
All labels including Smart Money
Wallets related by on-chain behavior
Recent blockchain transactions for an address
Search for tokens and entities by name, symbol, or contract address
DCA strategies on Jupiter (Solana)
Real-time DEX trading activity (last 24h)
Daily snapshots of smart money holdings (Beta)
Aggregated token balances held by smart money
Net capital flows (inflows vs outflows) for tokens
Perpetual trading on Hyperliquid
Individual DEX transactions for a token
Segmented flows (Exchanges, Whales, Smart Money)
Hourly snapshots of inflows/outflows by category
Top holders with balance change tracking
Risk and Reward scores for a token
Jupiter DCA orders for a token (Solana)
Rank traders by profit for a specific token
Metadata, market metrics, and spot trading stats
Unified price/volume candles (1m to 1M timeframes)
Top token transfers (ERC-20)
Summary of net buyers/sellers
Discover trending tokens across chains
Why CrewAI?
When paired with CrewAI, Nansen (Blockchain Analytics) becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Nansen (Blockchain Analytics) tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
Nansen (Blockchain Analytics) in CrewAI
Nansen (Blockchain Analytics) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Nansen (Blockchain Analytics) to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Nansen (Blockchain Analytics) in CrewAI
The Nansen (Blockchain Analytics) MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 48 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Nansen (Blockchain Analytics) for CrewAI
Every tool call from CrewAI to the Nansen (Blockchain Analytics) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How can I track where Smart Money is moving capital?
Use the smart_money_netflow tool to see net capital flows (inflows vs outflows) for tokens, or smart_money_holdings to see aggregated balances held by these sophisticated entities.
Can I identify the behavior or identity of a specific wallet?
Yes, use profiler_labels or profiler_premium_labels to retrieve behavioral tags (like 'Smart Money', 'Heavy DEX User', or ENS names) associated with any blockchain address.
How do I analyze the performance of a specific address?
Use profiler_pnl_summary to get an aggregate view of profits and losses, or profiler_pnl for a detailed breakdown of performance for a specific address and token pair.
How does CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.
Explore More MCP Servers
View all →
Freshcaller
12 toolsManage your cloud phone system, track calls, and oversee agents via AI agents with Freshcaller.

USPS Developer Portal
8 toolsManage US mail — audit addresses, tracking, and ZIP codes via AI.

Classy.org
8 toolsManage fundraising and donations via Classy (GoFundMe Pro) — track campaigns, monitor transactions, and manage supporters directly from any AI agent.

Epic Fhir
10 toolsAccess patient records via Epic's FHIR R4 API — search patients, review encounters, pull lab results and medications from any AI agent.
