Skip to content
MCP profile

Smithery Blockscout Mcp Server

Provide AI agents and automation tools with contextual access to blockchain data including balance…

Developer ToolsRemoteOpen SourceExternal
Last updated
April 1, 2026
Visibility
Public
ByRegistry

About This 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 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.

Specifications

Status
live
Industry
Developer Tools
Category
General
Server type
Remote
License
Open Source
Verified
Yes

Requirements

  • Clone the repository and install dependencies:
  • To customize the leading part of the User-Agent header used for RPC requests, set the BLOCKSCOUT_MCP_USER_AGENT environment variable (defaults to "Blockscout MCP"). The server version is appended automatically.

Hosting


Hosting Options

  • Remote

API


Integrate this server into your application. Choose a connection method below.

1

Install

Install command
bash
uv pip install -e . # or `pip install -e .`
2

Configure

Configuration
json
{
      "mcpServers": {
        "blockscout": {
          "httpUrl": "https://mcp.blockscout.com/mcp",
          "timeout": 180000
        }
      }
    }

Performance


Usage


Quick Reference


Name
Smithery Blockscout Mcp Server
Function
Provide AI agents and automation tools with contextual access to blockchain data including balance…
Transport
Remote
Install
uv pip install -e . # or `pip install -e .`
Source
External (Registry)
License
Open Source
Get started

Ready to integrate this MCP server?

Book a demo to see how this server fits your workflow, or explore the full catalog.

Related MCP Servers


Catalog Workspace

Discover agents, MCP servers, and skills in one governed surface

Use structured catalog views to compare readiness, ownership, integrations, and deployment posture before rollout.