Mcp Simulate
Dry-run EVM transactions through Crypto APIs so your agent catches revert risk before you sign or pay gas on mainnet.
Overview
mcp-simulate is a Ship-phase MCP server that dry-runs EVM transactions through Crypto APIs for pre-broadcast testing.
What is this MCP server?
- Dry-run EVM transaction simulation via Crypto APIs
- npm @cryptoapis-io/mcp-simulate v0.3.0 with stdio MCP transport
- Requires CRYPTOAPIS_API_KEY for simulation endpoints
- Fits between mcp-prepare-transactions and mcp-signer in a safe broadcast pipeline
- Surfaces revert and execution outcomes without spending real gas
- Server version 0.3.0
- EVM-focused simulation scope per package description
- npm package @cryptoapis-io/mcp-simulate
What problem does it solve?
Shipping contract calls without simulation means expensive reverts and opaque failures you only discover after signing.
Who is it for?
Indie devs shipping EVM features who already use Crypto APIs and want agent-driven dry-runs on prepared transactions.
Skip if: Non-EVM-only stacks with no simulation need, or teams skipping API-backed infra entirely.
What do I get? / Deliverables
You see simulated EVM execution results in the agent loop and fix txs before local signing and broadcast.
- Simulation results for EVM transactions
- Agent-visible revert and execution feedback
- Safer handoff to mcp-signer after QA
Recommended MCP Servers
Journey fit
How it compares
EVM simulation MCP integration, not a full testnet faucet or local Hardhat replacement.
Common Questions / FAQ
Who is mcp-simulate for?
It is for builders using AI agents to validate EVM transactions through Crypto APIs before they sign and send them on-chain.
When should I use mcp-simulate?
Use it during ship testing after you have an unsigned EVM transaction and before you invoke local signing or broadcast.
How do I add mcp-simulate to my agent?
Install @cryptoapis-io/mcp-simulate, set CRYPTOAPIS_API_KEY, add the stdio MCP server to your agent, and run simulation tools on prepared txs.