Skip to main content
Glama

EVM-Web3MCP

Web3MCP for EVM chains. A protocol publishes the tools it wants AI agents to use under its own ENS name. One generic MCP server, installed as a Claude Code plugin or added to Codex, discovers those tools, reads contracts, simulates every write, and hands signing to the user's own wallet. There's no MCP server per protocol, and the agent never holds a key.

Sibling of Solana-Web3MCP. Built at ETHGlobal Mumbai 2026.

How it works

  1. Publish. The protocol stores a manifest in text records on its ENS name. With ENSv2 per-record roles, its release key can update tools but can't change address records.

  2. Discover. The host resolves the name, validates the manifest, and checks it both ways: the name points to the contract, and the contract's primary name points back (owner-verified). Third-party contracts get a publisher-only label.

  3. Use. Reads are plain contract calls. Writes are simulated, shown on a local signing page with the exact balance changes, and signed in the user's wallet.

Details: spec/SPEC.md.

Related MCP server: gulltoppr

Layout

Path

What

packages/sdk

@web3mcp/evm: manifest validation now; ENS discovery, reads and writes next

packages/mcp

@web3mcp/mcp: the generic MCP server

packages/approve-ui

Local signing page (planned)

plugins/claude-code

Claude Code plugin: MCP server, skill, and a hook that confirms every write

plugins/codex

Codex setup

apps/publisher

web3mcp-publish CLI: validate now, publish to ENS next

apps/explorer

Hosted read-only explorer (planned)

contracts

Foundry: DemoVault

spec

Specification and shared test fixtures

Install

Claude Code:

claude plugin marketplace add Team-Managed/EVM-Web3MCP
claude plugin install web3mcp@evm-web3mcp

Codex: see plugins/codex.

Both run @web3mcp/mcp from npm, which isn't published yet. Until then, use the development setup below.

Develop

Needs Node 24 (nvm use reads .nvmrc).

npm ci
npm test

Claude Code opened in this repo picks up .mcp.json, which runs the local build against the manifests in spec/fixtures/valid. Try: "discover vault.web3mcp-demo.eth".

Contracts need Foundry:

cd contracts && forge test

Status

Scaffold. Working: manifest validation, and an MCP server whose discover registers a protocol's tools and notifies the client. Next: ENS discovery and the trust check, reads and writes, the signing page, Uniswap tools, and Arkiv search.

License

Apache-2.0

Related MCP Connectors

Related MCP Servers

  • F
    license
    C
    quality
    B
    maintenance
    Enables AI agents to interact with any EVM-compatible blockchain through natural language, supporting token swaps, cross-chain bridges, staking, lending, governance, gas optimization, and portfolio tracking across networks like Ethereum, BSC, Polygon, Arbitrum, and more.
    100
    22 npm
    44
    -
  • F
    license
    Not graded
    quality
    D
    maintenance
    Enables AI agents to resolve smart contract ABIs, read, encode, simulate, and prepare transactions across multiple blockchains via a REST API or MCP server, with no signing required.
    -
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI agents to perform complex crypto operations like cross-chain routing, contract decoding, portfolio management, and anti-rug security checks, returning unsigned transactions for safe signing by the agent.
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI agents to analyze Ethereum wallets, simulate transactions, and draft transfers with deterministic policy and risk scoring, requiring human approval before on-chain execution.
    12 npm
    ISC