Skip to content

Connect

Status: Public MCP — not launched. Launch week target: 5–9 October 2026. Planned URL: https://mcp.feelyourprotocol.org/mcp. Roadmap launch details.

Looking to explore EIPs in the browser?

Go to feelyourprotocol.org — no MCP setup required. Come back here when the hosted MCP endpoint ships.

What is available today

URL / transportPurposeStatus
feelyourprotocol.orgInteractive explorationsLive — start here
https://mcp-docs.feelyourprotocol.orgThis documentation siteLive
https://mcp.feelyourprotocol.org/mcpRemote MCP over HTTPNot launched

There is no public URL to connect an agent today. Launch week: 5–9 October 2026 — see the roadmap launch page.

This page documents the hosted product. It is not a self-host guide.

What agents will connect to (at launch)

The hosted server will expose:

MCP toolShapePurpose
describe_capabilitiesprobeRegistry: named fork capabilities, runnable EIP modules, opcodes, encoding
run_bytecodesimulateRun raw bytecode under a fork config
run_transactiontransactionPaid tx gas, receipt logs, first-touch / wallet gasLimit
run_blockblock1–8 txs as a lab block; optional header slot / number / timestamp

To optionally compare baseline vs preview, call the same verb twice — osaka then amsterdam — and diff gas or outcomes. A single run on Amsterdam alone is fine.

Payments (x402) and the exact client config for Cursor, Claude, and other MCP hosts will be documented here when the endpoint ships. Same tools; remote HTTP — no local build required.

Example prompts (when the public server is connected)

You do not need to memorize tool names. Examples:

  • "Simulate bytecode 0x600100 under Amsterdam and tell me the gas used."
  • "What can I run under Amsterdam on this server without picking an EIP?"
  • "What EIPs does the Feel Your Protocol MCP server support?"
  • "Run a 1 wei transfer to an empty account on Amsterdam vs Osaka — what gas would a wallet need?"
  • "Run two transfers as one Amsterdam block and show the receipts."
  • "Run ModExp gas compare on Prague vs Osaka."

The agent should route these to run_bytecode, run_transaction, run_block, or describe_capabilities.

Changelog

Connect Changelog
  1. v0.122026-09-16Example prompt for a generic Amsterdam run with no EIP named.
  2. v0.102026-09-08Added run_transaction; renamed run_evm_bytecode → run_bytecode.
  3. v0.92026-09-02Launch week countdown — 5–9 Oct 2026 target; link to roadmap launch page.
  4. v0.72026-08-31Not publicly launched — reframe page as developer early access; point most users to website explorations.
  5. v0.62026-08-27Two live tools — compare_evm_variants removed.
  6. v0.52026-08-27Third live tool: compare_evm_variants; catalog is EIP-8024 only.
  7. v0.42026-07-22Local stdio gateway live — Cursor config, tool list, restart notes, agent guidance.
  8. v0.32026-07-20Split from overview — connection placeholder under use/.

Use = end-user reference. Internals = architecture and operations. Each section carries its own micro-changelog.