Blockscout MCP Server

What blockscout-mcp-server MCP server does

The blockscout-mcp-server MCP server connects MCP-compatible clients to Blockscout APIs and exposes selected blockchain data as callable tools. Its documented capabilities include listing supported chains, resolving ENS names to Ethereum addresses, finding token addresses by symbol or name, retrieving smart-contract ABIs, inspecting source files for verified contracts, and obtaining address information such as balances and related metadata.

The server is intended for AI agents, IDEs, and automation systems that need contextual access to blockchain information. It supports multiple chains through Blockscout PRO API configuration, with Chainscout metadata enrichment.

How it works

Call __unlock_blockchain_analysis__() once at the start of a session. This initializes the MCP session and returns server reference information, a pointer to the blockscout-analysis skill, and the rule used to resolve its URI. Other tools can then query the configured Blockscout services.

Responses use a standardized structured model. The server can send progress notifications for longer operations and periodic updates while work is in progress. To keep responses within model context limits, it supports configurable page sizes, opaque Base64URL cursors for pagination, and truncation of large fields with indicators explaining how to retrieve more data.

A versioned REST API is also provided for the MCP tools. The repository refers to API.md for its full documentation.

Setup and configuration

The hosted endpoint is https://mcp.blockscout.com/mcp. Clients send the PRO API credential in the Blockscout-MCP-Pro-Api-Key header. Claude can alternatively send the key as x-api-key; the server accepts that header as an alias. Keys are obtained through the Blockscout Developer Portal and use the proapi_ prefix.

The README documents setup for Claude, Claude Code, Cursor, Codex, ChatGPT Apps, and a local Docker-based development configuration. For local use, the provided configuration starts ghcr.io/blockscout/mcp-server:latest with Docker and standard input. Cursor and other remote configurations use the hosted Streamable HTTP endpoint.

Tools and capabilities

Documented tools include:

• Initialize the blockchain analysis session.
• Filter supported chains by name, chain ID, native currency, or ecosystem.
• Convert an ENS name into an Ethereum address.
• Search for token addresses by symbol or name.
• Retrieve a contract ABI for a chain and address.
• Read source files from verified contracts, optionally by file name.
• Retrieve comprehensive information for an address.

Limitations and notes

Most data tools route requests through the authenticated Blockscout PRO API and fail before an upstream request when a valid key is missing. The blockscout-mcp-server MCP server therefore requires credential configuration for typical data queries.

The Claude Connectors Directory option uses a shared access key and may have different access restrictions or capabilities. Claude organization owners configure connector credentials for Team and Enterprise plans, and changing those credentials requires removing and recreating the connector. The repository points to separate specification, testing, and structure documents for implementation details beyond this listing.