Capabilities

Status: Gateway v0.1 live (stdio) — describe_capabilities + simulate_evm_bytecode. Remote HTTP planned.

The MCP server exposes intent-driven tools — verbs that match how agents and integrators think about protocol work, not raw library APIs one-to-one.

Query shapes

Shape	MCP tool	What it does	Status
Probe	describe_capabilities	Supported forks, EIPs, ceilings, presets	Live (stdio)
Simulate	simulate_evm_bytecode	Run raw bytecode under a fork; optional trace	Live (stdio)
Compare	—	N variants (each with own fork + bytecode) → diff	Engine only (MCP tool planned)
Generate	—	Block-level access lists (EIP-7928)	Planned (Step 6)

Scope boundaries

• Stateless / BYOS — You supply bytecode and state overrides. No archive node, no mainnet sync.
• Raw bytecode, base-layer only — No Solidity compilation in the service. ERC/application-layer concerns are out of scope.
• Observability first — Rich execution traces (stack, gas, opcodes) are a primary deliverable.
• Hard wall — No sequential multi-block historical backtesting (archive-node / revm territory).

See Guarantees for limits and provenance details.

Changelog

Capabilities Changelog

1. v0.42026-07-22Probe + simulate MCP tools live on stdio gateway v0.1.
2. v0.32026-07-20Split from overview — end-user capability summary under use/.