Gateway

Status: v0.1 — six tools implemented (development transport). HTTP on AWS planned (Steps 4–5). Public product path is the hosted endpoint — see Connect.

The mcp-gateway repo is the public face of the MCP server:

• MCP transport — stdio as development transport today; HTTP /mcp on EC2 for the public product
• Tool registry — intent-driven tools → mcp-execution-engine
• TaskProcessor seam — LocalTaskProcessor now; worker pool / queue later
• Observability — planned (Step 7)
• x402 payments — planned (Steps 8–9)

It depends one-way on mcp-execution-engine. End-user connection (hosted): Connect.

Live tools (v0.1)

MCP tool	Engine call
describe_capabilities	describeCapabilities()
run_bytecode	simulateBytecode()
run_transaction	runTransaction()
run_block	runBlock()

Server name: FeelYourProtocol v0.1.0. Entry: node dist/index.js (bin: fyp-mcp).

Repository layout

mcp-gateway/
├── src/
│   ├── index.ts                 # stdio entry
│   ├── engine/TaskProcessor.ts  # scaling seam
│   ├── tools/                   # MCP tool registration
│   └── schemas/                 # zod (mirrored in public/schemas on docs site)
└── schemas/                     # JSON Schema copies for docs

Changelog

Gateway Changelog

1. v0.1.72026-09-16Server instructions claim generic hardfork prompts; named forks stay on the same verbs.
2. v0.1.52026-09-08Added run_transaction; renamed run_evm_bytecode → run_bytecode.
3. v0.1.42026-09-02Stdio framed as development transport; public path is hosted Connect.
4. v0.1.32026-08-27Renamed simulate_evm_bytecode → run_evm_bytecode.
5. v0.1.12026-08-27compare_evm_variants live on stdio.
6. v0.1.02026-07-22Stdio gateway — describe_capabilities + run_evm_bytecode, TaskProcessor seam, integration tests.
7. v0.32026-07-20Placeholder under internals/.