MCP Simulate

Name: MCP Simulate
Author: CryptoAPIs-io

by CryptoAPIs-ioversion 0.4.0i★ –iRuns on your computer

Registry nameio.github.CryptoAPIs-io/mcp-simulate

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other
You need to fill in: CRYPTOAPIS_API_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: CRYPTOAPIS_API_KEY

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

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

Run this in your terminal

claude mcp add simulate --env CRYPTOAPIS_API_KEY=your-value -- npx -y @cryptoapis-io/mcp-simulate

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

CRYPTOAPIS_API_KEY secret required env
Crypto APIs API key

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account CryptoAPIs-io, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32572 servers in this category
Published to the registry more recently than 48% of the other 32572 servers in this category
Basic checks equal to or better than 100% of the other 32572 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is MCP Simulate safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: CRYPTOAPIS_API_KEY

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.4.0) reached the registry 43 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, AvaHR

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

AvaHR

by avahr.com

Read hiring data and create inactive assessment and questionnaire drafts for human review.

Runs in the cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

@cryptoapis-io/mcp-simulate

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

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

Features

Simulate Ethereum transactions before broadcasting
Preview transaction results, gas usage, and state changes
Ethereum only (mainnet, sepolia) — the underlying API endpoint has no blockchain parameter

Prerequisites

Node.js 18+
Crypto APIs account and API key (sign up | get API key)

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 (listens on 127.0.0.1; see "Exposing the server beyond localhost")

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

Start the server in HTTP mode:

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

In your n8n workflow, add an AI Agent node
Under Tools, add an MCP Client Tool and set the URL to http://localhost:3000/mcp

n8n in Docker: localhost inside the container is not your machine. Start the server with --host 0.0.0.0 and MCP_AUTH_TOKEN set (see Exposing the server beyond localhost), use http://host.docker.internal:3000/mcp as the URL, and add an Authorization: Bearer header to the MCP Client Tool credential.

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

Available Tools

`simulate_evm`

Simulate an Ethereum transaction (dry run). Ethereum only — the underlying endpoint has no blockchain parameter.

Parameter	Description
`network`	Network: `mainnet` or `sepolia`
`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 (use `0.0.0.0` to accept remote connections — requires an auth token with `--api-key`)	`127.0.0.1`
`--auth-token`	Bearer token callers must send (`Authorization: Bearer` ); prefer the `MCP_AUTH_TOKEN` env var	`MCP_AUTH_TOKEN` env var
`--allowed-hosts`	Comma-separated `Host` header allowlist for non-loopback binds	—
`--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

Exposing the server beyond localhost

HTTP mode listens on 127.0.0.1 by default, so only processes on the same machine can reach it. To accept connections from other machines or containers, bind explicitly and protect the port:

# Startup-key mode: callers must present the token (the server refuses to start without one)

export MCP_AUTH_TOKEN=$(openssl rand -hex 32) npx @cryptoapis-io/mcp-simulate --transport http --host 0.0.0.0 --port 3000 --api-key YOUR_API_KEY \ --allowed-hosts mcp.internal.example

Clients send: Authorization: Bearer $MCP_AUTH_TOKEN

Per-request key mode: no startup key, every request must carry the caller's own x-api-key

npx @cryptoapis-io/mcp-simulate --transport http --host 0.0.0.0 --port 3000

--allowed-hosts restricts the Host header (DNS rebinding protection) when not bound to loopback. Prefer MCP_AUTH_TOKEN over --auth-token: command-line arguments are visible in the process list.

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

MCP Simulate

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

AvaHR

README from the maker

@cryptoapis-io/mcp-simulate

Features

Prerequisites

Installation

Usage

Or use environment variable

HTTP transport (listens on 127.0.0.1; see "Exposing the server beyond localhost")

Claude Desktop

Cursor

MCP Inspector

n8n

Available Tools

simulate_evm

CLI Arguments

HTTP API Key Modes

Clients send x-api-key header with each request

Exposing the server beyond localhost

Clients send: Authorization: Bearer $MCP_AUTH_TOKEN

Per-request key mode: no startup key, every request must carry the caller's own x-api-key

Important: API Key Required

Remote MCP Server

License

`simulate_evm`