Provide AI agents and automation tools with contextual access to blockchain data including balance…
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
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:
For more powerful and efficient blockchain analysis, install the Blockscout Analysis skill from the agent-skills repository. This skill provides AI agents with structured guidance for execution strategies, response handling, security best practices, and workflow orchestration.
Learn more: See the agent-skills README for full capabilities and installation instructions.
Configuring the Blockscout MCP server with an AI agent requires a Blockscout PRO API key. Most of the data tools route their requests through the authenticated Blockscout PRO API gateway, so without a valid key those tools fail fast before making any upstream request.
To obtain a key, register on the Blockscout Developer Portal (the free tier does not require a credit card) and generate an API key; keys are prefixed proapi_. Then supply it when configuring your client, as shown in the sections below.
The easiest way to use the Blockscout MCP server with Claude is the official hosted server: a native, managed installation experience with automatic updates and nothing to run yourself. Add it as a Custom Connector with your own PRO API key. Claude sends the key on every request in an x-api-key header, which the server accepts as an alias for its Blockscout-MCP-Pro-Api-Key header.
Blockscout and the URL to https://mcp.blockscout.com/mcp, then continue.None (Claude detects it). A warning that the connector has no credentials is expected: the key is supplied in the next step.x-api-key from the list, and paste your PRO API key as the value. Pick exactly this name; the server does not read the other similar-looking names in the list.Note: The Request headers section is in beta and is not yet available to every organization. If your dialog does not show it, use the Connectors Directory below.
Note: On Team and Enterprise plans the key is entered once by the Owner and shared by the whole organization. Authentication settings cannot be edited after a connector is added: to change the key, remove the connector and add it again.
If the Custom Connector dialog has no Request headers section, install the Blockscout connector from the official Anthropic Connectors Directory. It connects to the same hosted server but uses a shared access key.
Visit claude.com/connectors/blockscout and click links in "Used in" section to install the Blockscout connector.
Limitations: Due to the use of a shared access key, there may be restrictions on connector access and capabilities.
Pass your PRO API key via the Blockscout-MCP-Pro-Api-Key header when adding the server:
After running this command, Blockscout will be available as an MCP server in Claude Code, allowing you to access and analyze blockchain data directly from your coding environment.
Install the Blockscout app from the ChatGPT Apps marketplace:
Blockscout, select the Streamable HTTP tab, and set URL to https://mcp.blockscout.com/mcp.Blockscout-MCP-Pro-Api-Key and value proapi_your_key_here.Codex CLI cannot attach a custom header from the command line, so configure it in two steps:
Scaffold the server entry:
Edit ~/.codex/config.toml to add the PRO API key header and enable the streamable-HTTP MCP client (required for remote MCP servers to connect). The resulting configuration should look like this:
Add the server to your Cursor MCP configuration — either the project-level .cursor/mcp.json or the global ~/.cursor/mcp.json — supplying your PRO API key via the Blockscout-MCP-Pro-Api-Key header:
If you want to run the server locally for development purposes:
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.
Factual signals from GitHub, npm, and our automated checks — not a rating.
No reviews yet — be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/blockscout-mcp-server)<a href="https://allmcps.com/mcp/blockscout-mcp-server"><img src="https://allmcps.com/api/badge/blockscout-mcp-server?style=directory" alt="Blockscout MCP Server on AllMCPs" /></a>