Architecture

Status: MCP docs site live. Execution engine v0.1. Public MCP not launched (HTTP — Step 5). Gateway stdio exists as a development transport in the gateway repo — not a public product path.

What we are building

Piece	Role
mcp-execution-engine	Pure TypeScript library — isolated EthereumJS lab simulations (bytecode, transactions, BALs, traces). No chain RPC, no HTTP, no payments, no agent protocol.
mcp-gateway	MCP transport + tool registry (+ later observability, x402). Depends one-way on the engine. HTTP public path planned; stdio is the current development transport.
mcp-docs (this site)	Public documentation — Use for end users, Internals for us and deep-divers.
server-config (private)	Nginx blocks, deploy scripts, secrets — not in this public repo.

Mental model (from the two-legs vision): the explorations website is the textbook; the MCP server is the lab equipment.

Roots in the website

The MCP server reuses the same EthereumJS v10 patterns already proven in the explorations website:

• EIP-8024 stack ops — createEVM + evm.runCode (see the EIP-8024 exploration)
• EIP-8037 state gas — createVM + runTx (see the EIP-8037 exploration)
• EIP-7708 transfer logs — createVM + runBlock (receipts; see the EIP-7708 exploration)
• EIP-7928 block-level access lists — createVM + runBlock + blockLevelAccessList (see the BAL exploration)

The browser eComponents layer and the server execution engine are separate code paths today; converging shared core logic is a future DRY seam. MCP simulateBytecode uses createVM plus a message-call, not detached runCode.

Endpoints

URL / transport	Purpose	Status
https://mcp-docs.feelyourprotocol.org	This documentation site	Live (static on Strato)
https://mcp.feelyourprotocol.org/mcp	Remote MCP over HTTP	Planned (Step 5, AWS EC2)

Status

Build sequence (see roadmap timeline):

1. MCP docs site — this site
2. Execution engine — simulateBytecode() + runTransaction() + runBlock() + capability registry (reference)
3. Gateway (stdio) — development transport / PoC — six tools implemented (incl. generate, inspect)
4. AWS bootstrap — EC2, nginx, TLS, deploy pipeline
5. HTTP transport — remote MCP endpoint
6. Further tools — observability, x402, … (EIP-7928 BAL generate/inspect shipped)

Changelog

Architecture Changelog

1. v0.122026-09-14MCP simulateBytecode is createVM plus a message-call, not detached runCode.
2. v0.112026-09-14Engine described as isolated lab (no chain RPC), not empty-world stateless.
3. v0.102026-09-10run_block lab verb — header snapshot and per-tx receipts; BAL generate still planned.
4. v0.92026-09-08Engine/gateway surface: run_transaction plus run_bytecode rename; 8037/7708 website primitives documented.
5. v0.82026-09-02Public endpoints table is hosted-only; stdio is development transport, not a user path.
6. v0.72026-08-27compare_evm_variants removed — probe + simulate only.
7. v0.62026-08-27EIP-8024 module is opcode/encoding support; callers supply bytecode.
8. v0.52026-08-27compare_evm_variants live; EIP-8024 module catalog (runnable only).
9. v0.42026-07-22Gateway stdio v0.1 live — Step 3 core tools shipped.
10. v0.32026-07-20Docs restructure — use/ vs internals/ split; architecture page replaces overview internals.
11. v0.22026-07-20Execution engine v0.1.0 — simulateBytecode, registry, provenance, compare composer (local repo).
12. v0.12026-07-15Initial MCP docs site — overview, roadmap relationship, terminal-green skin.