The blockscout-mcp-server is a read-only multichain EVM blockchain analysis server that queries on-chain data through the Blockscout REST API, designed for LLM clients.
Key capabilities:
Onboarding guard — A mandatory first tool (__unlock_blockchain_analysis__) ensures agents understand usage rules before proceeding.
Chain discovery — List all supported chains (bundled + custom), filterable by name or chain ID.
Address lookup — Get balance, type (EOA vs. contract), and metadata for any address.
Token balances — Retrieve ERC-20/721/1155 token balances held by an address.
Token transfers — List token transfer events for an address or within a specific transaction.
Transaction history & details — Fetch native transactions by address or full details (status, value, gas, decoded input) by hash.
Block info — Retrieve block details by number or hash, or get the latest block height.
Event logs — Fetch event logs emitted by a contract/address (large fields truncated).
Smart contract analysis — Get verified contract ABIs, source code, and compiler metadata.
NFT holdings — List ERC-721/1155 NFTs owned by an address.
Token search — Look up tokens by symbol or name to find their contract addresses.
Raw API access — An escape hatch (direct_api_call) to call any Blockscout /api/v2 endpoint directly.
Pagination — All list tools support cursor-based pagination for efficient traversal of large datasets.
Custom chains — Register or override chains via a CHAINS_FILE environment variable.
Provides tools for querying on-chain data from EVM-compatible blockchains, including Ethereum, via the Blockscout API. Allows retrieving address balances, transaction details, token balances, block information, and more.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@blockscout-mcp-server show me the latest block on Ethereum"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A read-only stdio MCP server that gives AI agents multichain EVM on-chain data — addresses, transactions, blocks, logs, tokens, NFTs, and contract source — through the Blockscout REST API.
This isnot the official Blockscout MCP server. It is a custom, independently built server maintained by an individual developer, and it is not affiliated with or endorsed by the Blockscout team.
npx downloads the published package and runs it — nothing to install manually. Works from any
project; point CHAINS_FILE at that project's chains file (a relative ./chains.json resolves
against the client's working directory).
{
"mcpServers": {
"blockscout": {
"command": "npx",
"args": ["-y", "blockscout-mcp-server"],
"env": {
"CHAINS_FILE": "./chains.json",
"ONLY_CHAINS_FILE": "true"
}
}
}
}The chain registry and env are read once at startup. After changing config or code, restart (reconnect) the server in your MCP client. A ready-to-edit
.mcp.example.jsonis included.
Related MCP server: Onesource MCP
These chains are registered out of the box from the bundled snapshot
(src/chains/bundled.json) — no configuration required. The chain argument of
any tool accepts either the name (ethereum) or the numeric chain ID (1).
Chain name | Chain ID | Blockscout instance |
| 1 | |
| 10 | |
| 100 | |
| 8453 | |
| 42161 | |
| 534352 | |
| 11155111 |
Call the get_chains_list tool to see the chains actually registered on a running
server.
Point CHAINS_FILE at a JSON file describing extra chains (or overriding bundled ones).
Each entry needs a name, chainId, and Blockscout instance url:
[
{ "name": "my-l2", "chainId": 42, "url": "https://scan.my-l2.io" }
]If CHAINS_FILE is set but the file is missing or malformed, the server exits immediately (fail-fast).
Set ONLY_CHAINS_FILE=true to register only the chains from CHAINS_FILE and exclude the
bundled snapshot entirely. It requires CHAINS_FILE to be set (otherwise no chains would exist and
the server fails fast). The default (false) merges bundled chains with CHAINS_FILE.
The MCP Inspector is wired up as a dev dependency, so you can walk through the MCP handshake and call tools by hand without hooking the server into a real client.
git clone https://github.com/imelon2/blockscout-mcp-server.git
cd blockscout-mcp-server
pnpm install
pnpm run inspectpnpm run inspect builds first, then opens the Inspector UI — pick the stdio transport
and point it at node dist/index.js. Two shortcuts:
MIT
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
MCP server for Blockscout
Blockscout MCP — multi-chain block-explorer aggregate
Etherscan MCP — multichain block-explorer API (Etherscan V2)
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/imelon2/blockscout-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server