@cryptoapis-io/mcp-prepare-transactions
MCP server for Crypto APIs Prepare Transactions product. Build unsigned transactions for EVM, Tezos, Solana, Kaspa, XRP, UTXO, and Tron.
API Version: Compatible with Crypto APIs version 2024-12-12
接入你的智能体
發布者自己的指令。不是 PlugMCP 端點。
用我們的金鑰與日誌託管一份副本。
npx -y @cryptoapis-io/[email protected]Claude Code 沒有本機指令的安裝連結。複製下方指令並在終端機中執行。
CRYPTOAPIS_API_KEY=<secret> claude mcp add io.github.cryptoapis-io-mcp-prepare-transactions -- npx -y @cryptoapis-io/mcp-prepare-transactions@0.6.0在終端機中執行。
{ "mcpServers": { "io.github.cryptoapis-io-mcp-prepare-transactions": { "command": "npx", "args": [ "-y", "@cryptoapis-io/[email protected]" ], "env": { "CRYPTOAPIS_API_KEY": "<secret>" } } }}claude_desktop_config.json
遠端 URL 還是本機指令? 兩種安裝方式的差異
來自發布者
MCP server for Crypto APIs Prepare Transactions product. Build unsigned transactions for EVM, Tezos, Solana, Kaspa, XRP, UTXO, and Tron.
API Version: Compatible with Crypto APIs version 2024-12-12
MCP server for building unsigned transactions on EVM, Tezos, Solana, Kaspa, XRP, UTXO, Tron
npm install @cryptoapis-io/mcp-prepare-transactions
Or install all Crypto APIs MCP servers: npm install @cryptoapis-io/mcp
# Run with API key
npx @cryptoapis-io/mcp-prepare-transactions --api-key YOUR_API_KEY
# Or use environment variable
export CRYPTOAPIS_API_KEY=YOUR_API_KEY
npx @cryptoapis-io/mcp-prepare-transactions
# HTTP transport (listens on 127.0.0.1; see "Exposing the server beyond localhost")
npx @cryptoapis-io/mcp-prepare-transactions --transport http --port 3000 --api-key YOUR_API_KEY
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-prepare-transactions": {
"command": "npx",
"args": ["-y", "@cryptoapis-io/mcp-prepare-transactions"],
"env": {
"CRYPTOAPIS_API_KEY": "your_api_key_here"
}
}
}
}
Add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):
{
"mcpServers": {
"cryptoapis-prepare-transactions": {
"command": "npx",
"args": ["-y", "@cryptoapis-io/mcp-prepare-transactions"],
"env": {
"CRYPTOAPIS_API_KEY": "your_api_key_here"
}
}
}
}
npx @modelcontextprotocol/inspector npx @cryptoapis-io/mcp-prepare-transactions --api-key YOUR_API_KEY
npx @cryptoapis-io/mcp-prepare-transactions --transport http --port 3000 --api-key YOUR_API_KEY
http://localhost:3000/mcpn8n in Docker:
localhostinside the container is not your machine. Start the server with--host 0.0.0.0andMCP_AUTH_TOKENset (see Exposing the server beyond localhost), usehttp://host.docker.internal:3000/mcpas the URL, and add anAuthorization: Bearer <token>header to the MCP Client Tool credential.
All servers default to port 3000. Use
--portto assign different ports when running multiple servers.
prepare_transactions_evmPrepare unsigned EVM transactions.
prepare_transactions_tezosPrepare unsigned Tezos operations (mainnet, shadownet).
prepare_transactions_solanaPrepare unsigned Solana transactions (mainnet, devnet).
prepare_transactions_kaspaPrepare unsigned Kaspa transactions (mainnet only).
prepare_transactions_xrpPrepare unsigned XRP transactions (mainnet, testnet).
prepare_transactions_utxoPrepare unsigned UTXO transactions (Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash; mainnet, testnet).
prepare_transactions_tronPrepare unsigned Tron transactions via Tron's dedicated prepare-transactions endpoints (mainnet, nile).
When using HTTP transport, the server supports two API key modes:
--api-key: The key is used for all requests. x-api-key request headers are ignored.--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-prepare-transactions --transport http --port 3000
# Clients send x-api-key header with each request
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-prepare-transactions --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-prepare-transactions --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.
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
MCP server for building unsigned transactions on EVM, Tezos, Solana, Kaspa, XRP, UTXO, Tron
{ "mcpServers": { "io.github.cryptoapis-io-mcp-prepare-transactions": { "command": "npx", "args": [ "-y", "@cryptoapis-io/[email protected]" ], "env": { "CRYPTOAPIS_API_KEY": "<secret>" } } }}工具
尚無工具清單。遠端伺服器會在首次健康檢查後取得工具清單。
常見問題
在本頁複製適用於 Cursor、Claude Desktop、Claude Code 或 VS Code 的 stdio 設定。它使用發布者的安裝方式,而不是 PlugMCP 代理伺服器。
發布者列出了以下環境變數:CRYPTOAPIS_API_KEY。
MCP Prepare Transactions 透過 stdio 在本機執行。
上次檢查時間:2026-11-19。 MCP server for building unsigned transactions on EVM, Tezos, Solana, Kaspa, XRP, UTXO, Tron