Web3 Stats Enhanced - Dune + Blockscout MCP Server

This project implements a Model Context Protocol (MCP) server that combines the power of Dune Analytics and Blockscout APIs, providing comprehensive blockchain data analysis capabilities for LLM agents and MCP clients.

🚀 What's New in Version 2.0

This enhanced version adds Blockscout integration alongside the existing Dune API, enabling:

• Real-time blockchain data from Blockscout (transactions, contracts, logs)

• Aggregated analytics from Dune (holder distributions, price trends)

• Compound tools that intelligently combine both data sources

• Support for 9+ blockchain networks with more coming

Related MCP server: Beyond MCP Server

Features

🔷 Dune API Tools (Aggregated Analytics)

EVM Tools:

• get_evm_balances: Fetches EVM token balances for a wallet

• get_evm_activity: Fetches EVM account activity

• get_evm_collectibles: Fetches EVM NFT collectibles

• get_evm_transactions: Retrieves granular EVM transaction details

• get_evm_token_info: Fetches metadata and price for EVM tokens

• get_evm_token_holders: Discovers EVM token holder distributions

SVM Tools:

• get_svm_balances: Fetches SVM token balances

• get_svm_transactions: Fetches SVM transactions (Solana only)

🔶 Blockscout API Tools (Real-time Data)

Search & Discovery:

• blockscout_search: Universal search across addresses, tokens, blocks, transactions

• ping_blockscout: Test connectivity to Blockscout instances

Address Analysis:

• blockscout_address_info: Get address details, balance, type (EOA/contract)

• blockscout_address_transactions: Get all transactions for an address

• blockscout_address_internal_txs: Get internal transactions

• blockscout_address_logs: Get event logs

• blockscout_address_token_balances: Get all token balances

Transaction Analysis:

• blockscout_transaction_details: Get full transaction details

• blockscout_transaction_logs: Get event logs from a transaction

• blockscout_transaction_internal_txs: Get internal transactions

• blockscout_transaction_raw_trace: Get raw execution trace

• blockscout_transaction_state_changes: Get state changes

Block Explorer:

• blockscout_block_details: Get block information

• blockscout_block_transactions: Get all transactions in a block

• blockscout_latest_blocks: Get recent blocks

Smart Contracts:

• blockscout_contract_info: Get verified contract details, ABI, source

• blockscout_contract_methods: Get readable/writable methods

• blockscout_read_contract: Call contract read methods

• blockscout_verified_contracts: List recently verified contracts

Token & NFT Tools:

• blockscout_token_info: Get token details, supply, decimals

• blockscout_token_transfers: Get token transfer history

• blockscout_token_holders: Get token holder list

• blockscout_nft_instances: Get NFT instances for a collection

• blockscout_nft_metadata: Get specific NFT metadata

🔥 Compound Tools (Best of Both APIs)

• investigate_smart_contract: Deep contract analysis with source code and analytics

• analyze_transaction_impact: Full transaction forensics with traces and context

• token_deep_analysis: Comprehensive token risk assessment

• profile_wallet_behavior: Behavioral profiling with historical patterns

📊 Resources

• dune://evm/supported-chains: Dune supported chains

• web3-stats://supported-networks: Unified network support across both APIs

💬 Enhanced Prompts

• /comprehensive_wallet_analysis: Deep wallet investigation

• /smart_contract_deep_dive: Thorough contract investigation

• /token_risk_assessment: Multi-source token risk analysis

• /transaction_post_mortem: Transaction impact analysis

• /compare_networks: Network capability comparison

Legacy prompts still supported:

• /evm_wallet_overview: Basic wallet overview

• /analyze_erc20_token: Basic token analysis

• /svm_address_check: Solana address check

Quick Start

# Clone the repository
git clone https://github.com/crazyrabbitLTC/mcp-web3-stats.git
cd mcp-web3-stats

# Install dependencies
bun install

# Create .env file with your Dune API key
echo "DUNE_API_KEY=your_actual_dune_api_key_here" > .env

# Start the server (default stdio mode for CLI tools)
bun start

# Or start with modern HTTP transport (recommended for HTTP clients)
bun start -- --transport http --port 3000

# In a separate terminal, run the MCP Inspector to test the tools
npx @modelcontextprotocol/inspector bun run index.ts

Installation from npm

# Install globally
npm install -g mcp-web3-stats-enhanced

# Set your Dune API key as an environment variable
export DUNE_API_KEY=your_actual_dune_api_key_here

# Run the server
mcp-web3-stats

# In a separate terminal, test with the MCP Inspector
npx @modelcontextprotocol/inspector mcp-web3-stats

Transport Modes

This server supports multiple transport modes for different deployment scenarios:

🚀 Modern Streamable HTTP (Recommended for HTTP)

# MCP Specification: 2025-03-26
mcp-web3-stats --transport http --port 3000

Features:

• ✅ Single /mcp endpoint for all operations

• ✅ Proper session management with Mcp-Session-Id header

• ✅ SSE support for server-to-client notifications

• ✅ Protocol version negotiation (MCP-Protocol-Version header)

• ✅ Session termination via DELETE request

• ✅ DNS rebinding protection

• ✅ Localhost-only binding for security

Endpoints:

• POST /mcp - Send requests, initialize sessions

• GET /mcp - Receive notifications via Server-Sent Events

• DELETE /mcp - Terminate sessions

• GET /health - Health check

💻 stdio (Default)

# For CLI tools and desktop integrations (Claude Desktop, etc.)
mcp-web3-stats

Best for: Desktop applications, CLI tools, subprocess integrations

🔄 Hybrid Mode

# Support both modern and legacy clients simultaneously
mcp-web3-stats --transport hybrid --port 3000

Provides both /mcp (modern) and /sse + /message (legacy) endpoints.

⚠️ Legacy SSE (Deprecated)

# Only for backwards compatibility - will be removed in future version
mcp-web3-stats --transport sse-legacy --port 3000

Migration Notice: The legacy SSE transport uses the deprecated 2024-11-05 specification. Please migrate to --transport http for modern protocol support.

Testing the HTTP Transport

Initialize a Session

curl -X POST http://127.0.0.1:3000/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "MCP-Protocol-Version: 2025-03-26" \
  -d '{
    "jsonrpc": "2.0",
    "method": "initialize",
    "params": {
      "protocolVersion": "2025-03-26",
      "capabilities": {},
      "clientInfo": {"name": "test-client", "version": "1.0.0"}
    },
    "id": 1
  }'

Extract the Mcp-Session-Id from response headers.

List Available Tools

curl -X POST http://127.0.0.1:3000/mcp \
  -H "Content-Type: application/json" \
  -H "Mcp-Session-Id: YOUR_SESSION_ID" \
  -H "MCP-Protocol-Version: 2025-03-26" \
  -d '{"jsonrpc":"2.0","method":"tools/list","params":{},"id":2}'

Open SSE Stream for Notifications

curl -N http://127.0.0.1:3000/mcp \
  -H "Mcp-Session-Id: YOUR_SESSION_ID" \
  -H "Accept: text/event-stream"

Terminate Session

curl -X DELETE http://127.0.0.1:3000/mcp \
  -H "Mcp-Session-Id: YOUR_SESSION_ID" \
  -H "MCP-Protocol-Version: 2025-03-26"

Security Considerations

When running in HTTP mode, this server implements several security measures:

• Localhost-only binding: Server binds to 127.0.0.1 only

• Origin validation: Validates Origin header on requests

• DNS rebinding protection: Enforces allowed hosts list

• Session security: Cryptographically secure session IDs (UUID v4)

• Protocol version validation: Ensures client/server compatibility

For production deployments, consider:

• Running behind a reverse proxy (nginx, Caddy)

• Implementing additional authentication (OAuth2, API keys)

• Using HTTPS with valid certificates

• Rate limiting and request size limits

Migration Guide: Legacy SSE → Modern HTTP

If you're currently using the deprecated SSE transport:

Before:

mcp-web3-stats --transport sse --port 3000
# Endpoints: /sse (GET), /message (POST)
# Header: X-Session-Id

After:

mcp-web3-stats --transport http --port 3000
# Endpoint: /mcp (POST, GET, DELETE)
# Header: Mcp-Session-Id

Migration Steps:

1. Update client to use single /mcp endpoint

2. Change header from X-Session-Id to Mcp-Session-Id

3. Add MCP-Protocol-Version: 2025-03-26 header

4. Add Accept: application/json, text/event-stream header for POST requests

5. Update initialization to use POST instead of GET

6. Use DELETE for session termination instead of just closing connection

Transitional Period: Use --transport hybrid to support both old and new clients simultaneously during migration.

Supported Networks

The server supports multiple blockchain networks through Blockscout instances:

• Ethereum (Chain ID: 1)

• Optimism (Chain ID: 10)

• BNB Smart Chain (Chain ID: 56)

• Gnosis (Chain ID: 100)

• Polygon (Chain ID: 137)

• Fantom (Chain ID: 250)

• Base (Chain ID: 8453)

• Arbitrum (Chain ID: 42161)

• Avalanche (Chain ID: 43114)

More networks can be added by updating the BLOCKSCOUT_NETWORKS configuration.

Advanced Use Cases

1. Smart Contract Investigation

Combine source code verification with usage analytics:

Assistant: I'll investigate this smart contract using both Blockscout and Dune data.

[Uses investigate_smart_contract]

This contract is:
- Verified on Blockscout with Solidity 0.8.19
- Has 45 read methods and 12 write methods
- Processes $2.5M daily volume (from Dune)
- Top 10 holders control 65% of supply

2. Transaction Forensics

Analyze complex transactions with full context:

Assistant: Let me analyze this transaction's complete impact.

[Uses analyze_transaction_impact]

Transaction breakdown:
- Triggered 15 internal transactions
- Changed 8 storage slots
- Emitted 12 events
- Sender has 500+ previous transactions
- This was their largest transaction this month

3. Token Risk Assessment

Comprehensive token analysis across both platforms:

Assistant: I'll perform a deep risk assessment of this token.

[Uses token_deep_analysis]

Risk Assessment:
⚠️ High concentration: Top 10 holders own 78%
✅ Verified contract with clean code
⚠️ Low liquidity: $50k daily volume
✅ Active development: 50+ transfers in last hour

4. Wallet Behavioral Analysis

Profile wallets using combined historical and real-time data:

Assistant: Let me create a behavioral profile for this wallet.

[Uses profile_wallet_behavior]

Wallet Profile:
- Type: DeFi Power User
- 1,250 total transactions
- Interacts with 45 unique contracts
- Portfolio: 60% stablecoins, 30% DeFi tokens, 10% NFTs
- Activity level: High (50+ tx/month)

Configuration

Environment Variables

• DUNE_API_KEY: Required API key from Dune Analytics

Command Line Options

• --transport <mode>: Transport mode (stdio, http, sse-legacy, hybrid)

• --port <number>: Port for HTTP transports (default: 3000)

• --help: Show help message

• --version: Show version information

Adding New Blockscout Networks

Edit the BLOCKSCOUT_NETWORKS object in index.ts:

const BLOCKSCOUT_NETWORKS = {
  "1": { name: "Ethereum", url: "https://eth.blockscout.com", chainId: "1" },
  // Add new networks here
};

Integrating with Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "web3_stats_enhanced": {
      "command": "node",
      "args": [
        "/path/to/mcp-web3-stats/dist/index.js"
      ],
      "env": {
        "DUNE_API_KEY": "your_actual_dune_api_key_here"
      }
    }
  }
}

Development

# Build TypeScript to JavaScript
bun run build

# Run tests (when available)
bun test

# Run in development mode
bun run index.ts

API Rate Limits

• Dune API: Rate limits depend on your plan

• Blockscout: Most public instances have generous rate limits (typically 100+ requests/second)

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

License

MIT License - see LICENSE file for details

Acknowledgments

• Dune Analytics for aggregated blockchain analytics

• Blockscout for real-time blockchain data

• Anthropic MCP for the protocol specification