Blockscout MCP Server

Created By
blockscouta year ago
Wraps Blockscout APIs and exposes blockchain data by Model Context Protocol
Overview

what is Blockscout MCP Server?

Blockscout MCP Server is a server that wraps Blockscout APIs to expose blockchain data through the Model Context Protocol (MCP), enabling AI agents and tools to access and analyze structured blockchain data.

how to use Blockscout MCP Server?

To use the Blockscout MCP Server, clone the repository, install dependencies, and configure it with tools like Claude Desktop to access blockchain data contextually.

key features of Blockscout MCP Server?

  • Contextual access to blockchain data for AI tools
  • Multi-chain support via Blockscout instance URLs
  • Custom instructions for MCP host
  • Progress notifications for multi-step operations
  • Enhanced user experience with periodic updates for long-running queries

use cases of Blockscout MCP Server?

  1. Accessing balances and token information for various blockchain addresses.
  2. Analyzing transaction histories and contract metadata.
  3. Integrating with AI tools for automated blockchain data analysis.

FAQ from Blockscout MCP Server?

  • What is the Model Context Protocol (MCP)?

MCP is an open protocol that allows AI agents and tools to consume and analyze structured data through context-aware APIs.

  • Is there multi-chain support?

Yes, the server supports multiple chains by fetching instance URLs from Chainscout.

  • How can I install the Blockscout MCP Server?

You can clone the repository and install dependencies using pip, or build a Docker image for deployment.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
blockscout
Star
2
Language
Python
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago