EVM MCP Server

An MCP (Model Context Protocol) server that gives autonomous coding agents deterministic, schema-validated tools for EVM smart contract development — security scanning, gas profiling, compiler diagnostics, and transaction simulation.

Why This Exists

Raw CLI output from tools like Slither and Foundry is noisy, non-deterministic, and often causes LLMs to hallucinate. This server intercepts the output, validates it through Zod schemas, and returns clean JSON that any agent can reliably parse.

Related MCP server: foundry-mcp

Tools

Tool	Annotations	Description
`evm_scan_vulnerabilities`	`readOnly`, `idempotent`	Run Slither analysis. Returns severity-rated findings with extracted code snippets. Supports `severityFilter` and `maxFindings`.
`evm_analyze_gas_profile`	`readOnly`, `idempotent`	Run `forge test --gas-report`. Returns structured per-function gas data.
`evm_compile_and_diagnose`	`readOnly`, `idempotent`	Run `forge build`. Returns structured compiler diagnostics on failure.
`evm_simulate_transaction`	`readOnly`, `idempotent`	Run `cast call`. Returns decoded return data or revert reasons.
`evm_inspect_storage_layout`	`readOnly`, `idempotent`	Run `forge inspect storage-layout`. Returns slot/offset/type per state variable — proxy-collision and packing checks.
`evm_trace_call`	`readOnly`, `idempotent`	Run `cast call --trace`. Returns structured call tree with gas, call types, events, and revert frames.
`evm_decode_calldata`	`readOnly`, `idempotent`	Decode hex calldata via `cast calldata-decode` (offline with signature) or `cast 4byte-decode` (selector lookup).
`evm_run_tests`	`readOnly`	Run `forge test` (optional `matchTest`/`matchPath`). Returns per-suite results with gas, fuzz runs, and failure counterexamples.
`evm_toolchain_versions`	`readOnly`, `idempotent`	Report installed/missing status and exact versions of `slither`, `forge`, `cast`.

Resources

URI	Description
`evm://patterns/vulnerabilities`	Security vulnerability pattern library
`evm://gas/optimizations`	Gas optimization pattern library
`evm://patterns/arbitrage`	Arbitrage strategy reference

Prompts

Skill workflows exposed as MCP prompts for clients without native skill support. Each embeds the full SKILL.md workflow.

Prompt	Args	Description
`audit_contract`	`contractPath`	Severity-rated security audit (vulnerability-scanning workflow)
`optimize_gas`	`projectPath`	Measured gas-optimization pass (gas-optimization workflow)
`analyze_arbitrage`	`scenario`	Opportunity ledger net of fees/gas/slippage (arbitrage-analysis workflow)

Architecture

evm-agent-toolkit/
├── src/
│   ├── mcp/            # MCP server entry point (stdio transport)
│   ├── tools/          # Zod-validated CLI output parsers
│   │   ├── slither.ts  # Slither JSON → SanitizedFinding[]
│   │   ├── forge.ts    # Forge gas tables → ContractGas[]
│   │   ├── compiler.ts # Forge build errors → CompilerDiagnostic[]
│   │   ├── simulator.ts# Cast call output → SimulatorDiagnostic
│   │   ├── storage.ts  # Forge storage layout → StorageEntry[]
│   │   ├── trace.ts    # Cast call traces → TraceEvent[]
│   │   ├── decoder.ts  # Cast calldata decode → DecodedCalldata
│   │   ├── testrunner.ts # Forge test output → TestSuite[]
│   │   └── versions.ts # Toolchain --version output → ToolVersion
│   ├── rules/          # Agent system prompt injections
│   └── hooks/          # Lifecycle hooks (UserPromptSubmit, Statusline)
├── tests/              # Vitest unit tests for all parsers
├── bench/              # Performance benchmarks
├── evals/              # Agent evaluation framework (vulnerable contracts + eval XML)
├── skills/             # Markdown reference libraries
├── .claude-plugin/     # Claude Code plugin manifest
└── gemini-extension.json # Antigravity plugin manifest

Setup

npm install
npm run build

Agent Configuration

This is a stdio MCP server. It is spawned by the MCP client, not started manually.

Claude Desktop / Cursor:

{
  "mcpServers": {
    "evm-agent-toolkit": {
      "command": "npx",
      "args": ["-y", "@0xendale/evm-agent-toolkit"]
    }
  }
}

Prerequisites: slither, forge, and cast must be installed on the host machine.

Development

npm run dev       # Watch mode with tsx
npm run test      # Run all unit tests
npm run bench     # Run parser benchmarks
npm run build     # Compile TypeScript → build/

Performance

Parser throughput (measured on Apple Silicon):

Parser	Iterations	Time	Per-call
Slither (100 detectors)	1,000	~109ms	~0.1ms
Forge Gas Table	10,000	~32ms	~0.003ms

License

MIT

Install Server

A

license - permissive license

A

quality

A

maintenance

How are these scores calculated?

Maintenance

–Maintainers

–Response time

0dRelease cycle

2Releases (12mo)

Commit activity

Resources

GitHub Repository

Need Help?

Related Servers

Tools

View all tools

evm-agent-toolkit

EVM MCP Server

Why This Exists

Tools

Resources

Prompts

Architecture

Setup

Agent Configuration

Development

Performance

License

Maintenance

Resources

Tools

Latest Blog Posts

MCP directory API