Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
CryptoAPIs-io avatar

Mcp Simulate

  • Updated March 13, 2026
  • CryptoAPIs-io/cryptoapis-mcp-simulate

mcp-simulate is a MCP server that dry-runs EVM transactions through Crypto APIs for pre-broadcast testing.

About

io.github.CryptoAPIs-io/mcp-simulate is an MCP server that dry-runs EVM transactions using Crypto APIs simulation endpoints. developers hook it up when smart-contract interactions are too risky to guess from static code review alone and they want the coding agent to validate execution paths before signing. The published server is version 0.3.0, distributed as @cryptoapis-io/mcp-simulate over stdio, and requires CRYPTOAPIS_API_KEY like the other cloud-backed CryptoAPIs MCP packages. It focuses on EVM simulation rather than every chain family, so it complements prepare-transactions and transactions-data when your stack is Ethereum-compatible. Typical flow: prepare unsigned tx, simulate with this server, adjust calldata or gas strategy, then sign locally. That ordering saves failed broadcasts and support tickets during ship.

  • 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

Mcp Simulate by the numbers

  • Data as of Jul 7, 2026 (Skillselion catalog sync)
terminal
claude mcp add --env CRYPTOAPIS_API_KEY=YOUR_CRYPTOAPIS_API_KEY mcp-simulate -- npx -y @cryptoapis-io/mcp-simulate

Add your badge

Show developers this MCP server is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Package@cryptoapis-io/mcp-simulate
TransportSTDIO
AuthRequired
Last updatedMarch 13, 2026
RepositoryCryptoAPIs-io/cryptoapis-mcp-simulate

What it does

Dry-run EVM transactions through Crypto APIs so your agent catches revert risk before you sign or pay gas on mainnet.

Who is it for?

Best when you're shipping EVM features and 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 you get

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

By the numbers

  • Server version 0.3.0
  • EVM-focused simulation scope per package description
  • npm package @cryptoapis-io/mcp-simulate
README.md

@cryptoapis-io/mcp-simulate

MCP server for Crypto APIs Simulate product. Dry-run EVM transactions to preview results without broadcasting.

API Version: Compatible with Crypto APIs version 2024-12-12

Features

  • Simulate EVM transactions before broadcasting
  • Preview transaction results, gas usage, and state changes
  • Supports all EVM-compatible blockchains (Ethereum, Ethereum Classic, BSC, Polygon, Avalanche (C-Chain), Arbitrum, Base, Optimism, Tron)

Prerequisites

Installation

npm install @cryptoapis-io/mcp-simulate

Or install all Crypto APIs MCP servers: npm install @cryptoapis-io/mcp

Usage

# Run with API key
npx @cryptoapis-io/mcp-simulate --api-key YOUR_API_KEY

# Or use environment variable
export CRYPTOAPIS_API_KEY=YOUR_API_KEY
npx @cryptoapis-io/mcp-simulate

# HTTP transport
npx @cryptoapis-io/mcp-simulate --transport http --port 3000 --api-key YOUR_API_KEY

Claude Desktop

Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS, %APPDATA%\Claude\claude_desktop_config.json on Windows):

{
  "mcpServers": {
    "cryptoapis-simulate": {
      "command": "npx",
      "args": ["-y", "@cryptoapis-io/mcp-simulate"],
      "env": {
        "CRYPTOAPIS_API_KEY": "your_api_key_here"
      }
    }
  }
}

Cursor

Add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):

{
  "mcpServers": {
    "cryptoapis-simulate": {
      "command": "npx",
      "args": ["-y", "@cryptoapis-io/mcp-simulate"],
      "env": {
        "CRYPTOAPIS_API_KEY": "your_api_key_here"
      }
    }
  }
}

MCP Inspector

npx @modelcontextprotocol/inspector npx @cryptoapis-io/mcp-simulate --api-key YOUR_API_KEY

n8n

  1. Start the server in HTTP mode:
    npx @cryptoapis-io/mcp-simulate --transport http --port 3000 --api-key YOUR_API_KEY
    
  2. In your n8n workflow, add an AI Agent node
  3. Under Tools, add an MCP Client Tool and set the URL to http://localhost:3000/mcp

All servers default to port 3000. Use --port to assign different ports when running multiple servers.

Available Tools

simulate_evm

Simulate an EVM transaction (dry run).

Parameter Description
blockchain Target blockchain (ethereum, binance-smart-chain, polygon, etc.)
network Network (mainnet, sepolia, testnet, etc.)
fromAddress Sender address
toAddress Recipient address
value Amount to send (in native coin)
data Contract call data (hex)
gasLimit Gas limit
gasPrice Gas price

CLI Arguments

Argument Description Default
--api-key Crypto APIs API key CRYPTOAPIS_API_KEY env var
--transport Transport type: stdio or http stdio
--host HTTP host 0.0.0.0
--port HTTP port 3000
--path HTTP path /mcp
--stateless Enable stateless HTTP mode false

HTTP API Key Modes

When using HTTP transport, the server supports two API key modes:

  • With --api-key: The key is used for all requests. x-api-key request headers are ignored.
  • Without --api-key: Each request must include an x-api-key header with a valid Crypto APIs key. This enables hosting a public server where each user provides their own key.
# Per-request key mode (multi-tenant)
npx @cryptoapis-io/mcp-simulate --transport http --port 3000
# Clients send x-api-key header with each request

Stdio transport always requires an API key at startup.

Important: API Key Required

Warning: Making requests without a valid API key — or with an incorrect one — may result in your IP being banned from the Crypto APIs ecosystem. Always ensure a valid API key is configured before starting any server.

Remote MCP Server

Crypto APIs provides an official remote MCP server with all tools available via HTTP Streamable transport at https://ai.cryptoapis.io/mcp. Pass your API key via the x-api-key header — no installation required.

License

MIT

Recommended MCP Servers

How it compares

EVM simulation MCP integration, not a full testnet faucet or local Hardhat replacement.

FAQ

Who is mcp-simulate for?

It is for developers 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.

Developer Toolsintegrationstesting

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.