Blockscout MCP Server

The Model Context Protocol (MCP) is an open protocol designed to allow AI agents, IDEs, and automation tools to consume, query, and analyze

Remote serverstreamable-httpPython

What is the Blockscout MCP MCP server?

Blockscout MCP MCP server exists for a simple reason — assistants are far more useful when they can act on Blockscout MCP directly instead of describing what you should do. 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.

What the assistant can call

Once Blockscout MCP is connected, these are the calls the assistant has available:

Configuration and credentials

You will need 5 environment variables: BLOCKSCOUT_PRO_API_KEY, BLOCKSCOUT_DEV_JSON_RESPONSE, BLOCKSCOUT_MCP_ALLOWED_HOSTS, BLOCKSCOUT_MCP_ALLOWED_ORIGINS, BLOCKSCOUT_DISABLE_COMMUNITY_TELEMETRY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Blockscout MCP's toolset — Installation — is a fair guide to whether it matches your workflow. It is maintained by blockscout; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the blockscout mcp mcp server does with a few real requests.

Available tools

ToolWhat it does
InstallationVisit [claude.com/connectors/blockscout](https://claude.com/connectors/blockscout) and click links in "Used in" section to install the Blockscout connector.

How to install the Blockscout MCP MCP server

{
      "mcpServers": {
        "blockscout": {
          "command": "docker",
          "args": [
            "run",
            "--rm",
            "-i",
            "sparfenyuk/mcp-proxy:latest",
            "--transport",
            "streamablehttp",
            "--headers",
            "Blockscout-MCP-Pro-Api-Key",
            "proapi_your_key_here",
            "--headers",
            "Blockscout-MCP-Intermediary",
            "ClaudeDesktop",
            "https://mcp.blockscout.com/mcp"
          ]
        }
      }
    }

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
BLOCKSCOUT_PRO_API_KEYCredential the server authenticates with.Yes
BLOCKSCOUT_DEV_JSON_RESPONSEConfiguration value read at startup.Optional
BLOCKSCOUT_MCP_ALLOWED_HOSTSEndpoint or connection string the server talks to.Optional
BLOCKSCOUT_MCP_ALLOWED_ORIGINSConfiguration value read at startup.Optional
BLOCKSCOUT_DISABLE_COMMUNITY_TELEMETRYConfiguration value read at startup.Optional

Example prompts to try

  • Use Blockscout MCP to Installation.

Frequently asked questions

It connects Blockscout MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 1 tool (Installation) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Blockscout MCP directly.