Gaode

Created By
tumfa year ago
Overview

what is Web3 MCP?

Web3 MCP is a server implementation that wraps Ankr's Advanced API, allowing access to blockchain data across multiple chains such as Ethereum, BSC, Polygon, and Avalanche.

how to use Web3 MCP?

To use Web3 MCP, clone the repository, install the necessary dependencies, set up the required environment variables, and run the server using the provided Python script.

key features of Web3 MCP?

  • Complete wrapper for all Ankr Advanced API endpoints
  • NFT API for accessing NFT metadata, holders, and transfers
  • Query API for blockchain statistics and transaction data
  • Token API for token balances and price information
  • Support for multiple blockchain networks

use cases of Web3 MCP?

  1. Accessing NFT data for various blockchain networks.
  2. Querying blockchain statistics and transaction history.
  3. Integrating blockchain data into decentralized applications.

FAQ from Web3 MCP?

  • What blockchain networks does Web3 MCP support?

Web3 MCP supports multiple networks including Ethereum, BSC, Polygon, and Avalanche.

  • Is Web3 MCP free to use?

Yes! Web3 MCP is open-source and free to use.

  • How do I set up Web3 MCP?

Follow the installation instructions in the documentation to clone the repository and configure the environment variables.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
tumf
Star
-
Language
-
License
-

Recommend Servers

View All
Payai X402 Tools

2 hours ago
Payai X402 Tools

2 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