The Model Context Protocol (MCP) is an open protocol designed to allow AI agents, IDEs, and automation tools to consume, query, and analyze structured data through context-aware APIs.
This server wraps Blockscout APIs and exposes blockchain data—balances, tokens, NFTs, contract metadata—via MCP so that AI agents and tools (like Claude, Cursor, or IDEs) can access and analyze it contextually.
Key Features:
- Contextual blockchain data access for AI tools
- Multi-chain support via getting Blockscout instance URLs from Chainscout
- Custom instructions for MCP host to use the server
- Supports MCP progress notifications for multi-step tool operations, allowing clients to track execution status
- Enhanced User Experience: Provides periodic progress updates for long-running API queries (e.g., fetching extensive transaction histories) when requested by the client, improving responsiveness
Refer to SPEC.md for the technical details.
Refer to AGENTS.md for the repository structure.
Refer to TESTING.md for comprehensive instructions on running both unit and integration tests.
__get_instructions__()- Provides custom instructions for the MCP host to use the server. This tool is required since the fieldinstructionsof the MCP server initialization response is not used by the MCP host so far (tested on Claude Desktop).get_chains_list()- Returns a list of all known chains.get_address_by_ens_name(name)- Converts an ENS domain name to its corresponding Ethereum address.lookup_token_by_symbol(chain_id, symbol)- Searches for token addresses by symbol or name, returning multiple potential matches.get_contract_abi(chain_id, address)- Retrieves the ABI (Application Binary Interface) for a smart contract.get_address_info(chain_id, address)- Gets comprehensive information about an address including balance, ENS association, contract status, token details, and public tags.get_tokens_by_address(chain_id, address, cursor=None)- Returns detailed ERC20 token holdings for an address with enriched metadata and market data.get_latest_block(chain_id)- Returns the latest indexed block number and timestamp.get_transactions_by_address(chain_id, address, age_from, age_to, methods)- Gets transactions for an address within a specific time range with optional method filtering.get_token_transfers_by_address(chain_id, address, age_from, age_to, token)- Returns ERC-20 token transfers for an address within a specific time range.transaction_summary(chain_id, hash)- Provides human-readable transaction summaries using Blockscout Transaction Interpreter.nft_tokens_by_address(chain_id, address, cursor=None)- Retrieves NFT tokens owned by an address, grouped by collection.get_block_info(chain_id, number_or_hash, include_transactions=False)- Returns block information including timestamp, gas used, burnt fees, and transaction count. Can optionally include a list of transaction hashes.get_transaction_info(chain_id, hash, include_raw_input=False)- Gets comprehensive transaction information with decoded input parameters and detailed token transfers.get_transaction_logs(chain_id, hash, cursor=None)- Returns transaction logs with decoded event data.get_address_logs(chain_id, address, cursor=None)- Gets logs emitted by a specific address with decoded event data.
On which popular networks is `ens.eth` deployed as a contract?
What are the usual activities performed by `ens.eth` on the Ethereum Mainnet?
Since it is a contract, what is the most used functionality of this contract?
Which address interacts with the contract the most?
Calculate the total gas fees paid on Ethereum by address `0xcafe...cafe` in May 2025.
Clone the repository and install dependencies:
git clone https://github.com/blockscout/mcp-server.git
cd mcp-server
uv pip install -e . # or `pip install -e .`The server runs in stdio mode by default:
python -m blockscout_mcp_serverHTTP Streamable Mode:
To run the server in HTTP Streamable mode (stateless, JSON responses):
python -m blockscout_mcp_server --httpYou can also specify the host and port for the HTTP server:
python -m blockscout_mcp_server --http --http-host 0.0.0.0 --http-port 8080CLI Options:
--http: Enables HTTP Streamable mode.--http-host TEXT: Host to bind the HTTP server to (default:127.0.0.1).--http-port INTEGER: Port for the HTTP server (default:8000).
Build the Docker image with the official tag:
docker build -t ghcr.io/blockscout/mcp-server:latest .Pull the pre-built image:
docker pull ghcr.io/blockscout/mcp-server:latestHTTP Streamable Mode:
To run the Docker container in HTTP mode with port mapping:
docker run --rm -p 8000:8000 ghcr.io/blockscout/mcp-server:latest python -m blockscout_mcp_server --http --http-host 0.0.0.0With custom port:
docker run --rm -p 8080:8080 ghcr.io/blockscout/mcp-server:latest python -m blockscout_mcp_server --http --http-host 0.0.0.0 --http-port 8080Note: When running in HTTP mode with Docker, use --http-host 0.0.0.0 to bind to all interfaces so the server is accessible from outside the container.
Stdio Mode: The default stdio mode is designed for use with MCP hosts/clients (like Claude Desktop, Cursor) and doesn't make sense to run directly with Docker without an MCP client managing the communication.
To use this MCP server with Claude Desktop:
-
Open Claude Desktop and click on Settings
-
Navigate to the "Developer" section
-
Click "Edit Config"
-
Open the file
claude_desktop_config.jsonand configure the server:{ "mcpServers": { "blockscout": { "command": "docker", "args": [ "run", "--rm", "-i", "ghcr.io/blockscout/mcp-server:latest" ] } } } -
Save the file and restart Claude Desktop
-
When chatting with Claude, you can now enable the Blockscout MCP Server to allow Claude to access blockchain data
This project is primarily distributed under the terms of the MIT license. See LICENSE for details.