Blockscout MCP Server

Created By
karacurta year ago
Overview

what is Blockscout MCP Server?

Blockscout MCP Server is a Model Context Protocol (MCP) server implementation designed for seamless interaction with the Blockscout API, providing a standardized interface for AI models.

how to use Blockscout MCP Server?

To use the Blockscout MCP Server, clone the repository, install the necessary dependencies, build the project, and configure the server with the Blockscout API endpoint URL.

key features of Blockscout MCP Server?

  • Supports any Blockscout API endpoint
  • Retrieves current block number
  • Checks account balances
  • Gets transaction counts (nonces)
  • Retrieves block and transaction details
  • Makes contract calls

use cases of Blockscout MCP Server?

  1. Integrating AI models with blockchain data.
  2. Automating blockchain data retrieval for applications.
  3. Enhancing blockchain analytics and reporting tools.

FAQ from Blockscout MCP Server?

  • What are the prerequisites for using Blockscout MCP Server?

Node.js (v16 or higher) and npm are required.

  • How do I configure the server?

You need to set the BLOCKSCOUT_API_URL environment variable and update your mcp.json file accordingly.

  • Is there a global installation required?

Yes, a global installation is necessary to make the blockscout-mcp command available system-wide.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
karacurt
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago