Cryptoapis Mcp Simulate — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Cryptoapis Mcp Simulate (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
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
npm install @cryptoapis-io/mcp-simulateOr install all Crypto APIs MCP servers: npm install @cryptoapis-io/mcp
# 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_KEYAdd 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"
}
}
}
}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"
}
}
}
}npx @modelcontextprotocol/inspector npx @cryptoapis-io/mcp-simulate --api-key YOUR_API_KEY npx @cryptoapis-io/mcp-simulate --transport http --port 3000 --api-key YOUR_API_KEYhttp://localhost:3000/mcpAll servers default to port 3000. Use --port to assign different ports when running multiple servers.simulate_evmSimulate 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 |
| 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 |
When using HTTP transport, the server supports two API key modes:
x-api-key request headers are ignored.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 requestStdio transport always requires an API key at startup.
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.
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.
MIT
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.