Blockchain MCP Server DEMO

Created By
darwintreea year ago
Overview

What is Blockchain MCP Server?

Blockchain MCP Server is a comprehensive Model Context Protocol (MCP) server designed for interacting with multiple EVM-compatible blockchains, providing tools and resources for blockchain data access and analysis.

How to use Blockchain MCP Server?

To use the Blockchain MCP Server, clone the repository, install the dependencies, build the project, and start the server. You can then access various tools and resources through API calls.

Key features of Blockchain MCP Server?

  • Multi-chain support for various EVM-compatible blockchains.
  • Tools for fetching blockchain data, including transaction details, block information, and address balances.
  • Support for standard Ethereum JSON-RPC methods.

Use cases of Blockchain MCP Server?

  1. Accessing transaction details across multiple blockchains.
  2. Fetching the latest block information for different chains.
  3. Analyzing address balances and transaction histories.

FAQ from Blockchain MCP Server?

  • What blockchains are supported?

The server supports Ethereum Mainnet and Conflux eSpace, with potential for more EVM-compatible chains.

  • How do I add support for new chains?

You can add new chains by updating the SUPPORTED_CHAINS object in the configuration file.

  • Is there a testing tool available?

Yes, you can test the server using the MCP Inspector.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
darwintree
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Payai X402 Tools

6 hours ago
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.

a day ago