Back to Browse

Cryptoapis Mcp Simulate MCP Server

FinanceLow Risk10.0Local
Free

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

About

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

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (2 strong, 3 medium validity signals). No known CVEs in dependencies. Package registry verified. Imported from the Official MCP Registry. Trust signals: trusted author (20/20 approved).

12 files analyzed · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

What You'll Need

Set these up before or after installing:

Crypto APIs API keyRequired

Environment variable: CRYPTOAPIS_API_KEY

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-cryptoapis-io-mcp-simulate": {
      "env": {
        "CRYPTOAPIS_API_KEY": "your-cryptoapis-api-key-here"
      },
      "args": [
        "-y",
        "@cryptoapis-io/mcp-simulate"
      ],
      "command": "npx"
    }
  }
}

Getting Started

Once installed, try these example prompts and explore these capabilities:

  • 1"Simulate sending 1 ETH from 0xABC to 0xDEF on Ethereum mainnet"
  • 2"What gas will this contract call use on Polygon?"
  • 3"Dry-run this EVM transaction before I broadcast it"
  • 4Tool: simulate_evm — Simulates an EVM transaction dry-run, returning gas usage, state changes, and result

Documentation

View on GitHub

From the project's GitHub README.

@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).

ParameterDescription
blockchainTarget blockchain (ethereum, binance-smart-chain, polygon, etc.)
networkNetwork (mainnet, sepolia, testnet, etc.)
fromAddressSender address
toAddressRecipient address
valueAmount to send (in native coin)
dataContract call data (hex)
gasLimitGas limit
gasPriceGas price

CLI Arguments

ArgumentDescriptionDefault
--api-keyCrypto APIs API keyCRYPTOAPIS_API_KEY env var
--transportTransport type: stdio or httpstdio
--hostHTTP host0.0.0.0
--portHTTP port3000
--pathHTTP path/mcp
--statelessEnable stateless HTTP modefalse

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

Reviews

No reviews yet

Be the first to review this server!

Version History

v0.2.3Mar 5, 2026Re-scanned

Added HTTP transport support and per-request API key mode for multi-tenant deployments.