Cryptoapis MCP Simulate MCP Server

MCP server for dry-run EVM transaction simulation via Crypto APIs

Local serverstdio

What is the Cryptoapis MCP Simulate MCP server?

Most developer tooling work still happens through a UI a human drives. Cryptoapis MCP Simulate MCP server moves it into the conversation instead. MCP server for dry-run EVM transaction simulation via Crypto APIs.

The short version

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

  • 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)

The tools it exposes

The server publishes 2 tools. What each one is for:

  • Cursor — The Cursor tool exposed by this server
  • simulate_evm — The simulate_evm tool exposed by this server

Getting it running

Installation goes through your MCP client rather than a global install: point it at @cryptoapis-io/mcp-simulate on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

What it needs from you

Configuration is passed through the environment: CRYPTOAPIS_API_KEY, YOUR_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Cryptoapis MCP Simulate's toolset — Cursor, simulate_evm — is a fair guide to whether it matches your workflow. It is maintained by cryptoapis-io; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Cryptoapis MCP Simulate's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
CursorThe Cursor tool exposed by this server.
simulate_evmThe simulate_evm tool exposed by this server.

How to install the Cryptoapis MCP Simulate MCP server

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

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
CRYPTOAPIS_API_KEYCredential the server authenticates with.Yes
YOUR_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Cryptoapis MCP Simulate to Cursor.
  • Use Cryptoapis MCP Simulate to simulate evm.

Frequently asked questions

It connects Cryptoapis MCP Simulate to MCP-compatible AI assistants such as Claude and Cursor, exposing 2 tools (Cursor, simulate_evm) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Cryptoapis MCP Simulate directly.