mcpField
C
contract-guard-mcp

contract-guard-mcp

Local
github.com/eltociearSecurity0Updated 10w ago
Repository

About contract-guard-mcp

contract-guard-mcp is an MCP server for checking EVM contracts and ERC20 approvals before an agent interacts with them. It uses public JSON-RPC without signing or external dependencies, and also offers the same check through a pay-per-call x402 endpoint.

Key features

  1. 01Detects contracts, EOAs, and EIP-7702 delegation
  2. 02Identifies upgradeable proxy patterns
  3. 03Returns ERC20 metadata and risk flags
  4. 04Audits allowances and flags unlimited approvals
  5. 05Supports Base and Ethereum

Use cases

  1. 01Check a token address before approving or swapping
  2. 02Review a spender’s ERC20 allowance
  3. 03Inspect proxy or delegated-EOA risks before trusting an address

MCP support

Exposes `check_contract` for contract and token risk checks and `check_approval` for ERC20 allowance audits to MCP clients. The server uses public JSON-RPC and does not sign transactions.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "eltociear-contract-guard": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/eltociear/contract-guard-mcp:mcp-1.1.0"
      ]
    }
  }
}
Run commanddocker run -i --rm ghcr.io/eltociear/contract-guard-mcp:mcp-1.1.0

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
ocighcr.io/eltociear/contract-guard-mcp:mcp-1.1.0

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

contract-guard-mcp

smithery badge MCP Registry

MCP server for a pre-interaction risk check on any EVM contract/token — what an agent needs before it approves, swaps, or trusts an address.

Tool: check_contract(address, chain="base") →

  • is-contract vs EOA / self-destructed
  • EIP-7702 delegated-EOA detection
  • upgradeable proxy detection (EIP-1967 + legacy zeppelinos)
  • ERC20 metadata (name / symbol / decimals / totalSupply)
  • risk score + actionable flags

Chains: Base, Ethereum. Pure public JSON-RPC, zero dependencies, no signing.

Also available as a pay-per-call x402 HTTP endpoint: https://eltociear-contract-guard.hf.space (POST /check, $0.005 USDC on Base).

Run

docker run -i --rm ghcr.io/eltociear/contract-guard-mcp:mcp-latest
# or
python3 server.py

MIT licensed.

Tools

  • check_contract(address, chain) — is-contract/EOA, EIP-7702, proxy, ERC20 metadata, risk score
  • check_approval(token, owner, spender, chain) — ERC20 allowance audit; flags unlimited approvals (the #1 drain vector)

Free MCP vs paid x402

This MCP server is free (run it locally / via your client). For server-side, batch, or no-install use, the same engine is a pay-per-call x402 HTTP API — POST https://eltociear-contract-guard.hf.space/check ($0.005 USDC on Base, no signup). Your agent's wallet pays per call.

Professional audit services

Maintained by the same author — paid services on Polar (Stripe checkout):

Full catalog: polar.sh/eltociear

Also live: clean-read ($0.005 / call)

Same operator, same x402 rails: clean-read turns any URL into clean Markdown for AI agents — fetches the page, strips nav/ads/boilerplate (trafilatura), returns the main content with title and word count. POST https://eltociear-skill-audit.hf.space/read — $0.005 USDC on Base, no signup.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.