Capabilities

Status: Six tools implemented (describe_capabilities, run_bytecode, run_transaction, run_block, generate, inspect). Public MCP not launched.

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, runnable EIP modules, opcodes, encoding	Implemented — public launch pending
Run bytecode	run_bytecode	Run raw bytecode as a message-call; optional trace and accounts	Implemented — public launch pending
Run transaction	run_transaction	Paid tx gas, receipt logs, EIP-8037 dimensions	Implemented — public launch pending
Run block	run_block	1–8 txs as a lab block; header snapshot (optional slot)	Implemented — public launch pending
Generate	generate	Derive lab artifacts (BAL / EIP-7928 first)	Implemented — public launch pending
Inspect	inspect	Structure + hash on caller blobs (BAL, 7702 auth, typed tx, withdrawals, requests)	Implemented — public launch pending

To optionally compare baseline vs preview, call the same verb twice — osaka (current mainnet EL), then amsterdam (preview) — and diff gas, success, traces, or logs. One run on Amsterdam only is fully supported — you do not need to name an EIP.

Scope boundaries

• Isolated lab / BYOS — You supply bytecode or transaction fields and any constructed prestate. No archive node, no mainnet or L2 sync. Prefund / code / storage / a short lab block in one call is in scope.
• Call isolation (default) — The next prompt does not see the last run’s EVM unless you pass that prestate again (or a future snapshot handle).
• 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.152026-09-16generate + inspect — BAL from lab block; inspect without chain state.
2. v0.142026-09-16Generic hardfork runs (Amsterdam default) are first-class — EIP modules remain the per-change catalogue.
3. v0.122026-09-14BYOS clarified: isolated from chain, demand-built prestate in-call; not an empty-world rule.
4. v0.112026-09-10Fourth tool run_block — lab header snapshot and per-tx receipts.
5. v0.102026-09-08Third tool run_transaction; renamed run_evm_bytecode → run_bytecode.
6. v0.92026-09-02Status is implemented vs public launch — no stdio / self-host product path.
7. v0.82026-08-27Renamed simulate_evm_bytecode → run_evm_bytecode.
8. v0.62026-08-27Probe lists opcode/encoding facts; no demo scenarios on the catalog.
9. v0.42026-07-22Probe + simulate MCP tools live on stdio gateway v0.1.
10. v0.32026-07-20Split from overview — end-user capability summary under use/.