@cryptoapis-io/mcp-utils
OfficialProvides EVM utilities for Binance Smart Chain, including address validation, raw transaction decoding, and HD wallet address derivation.
Provides UTXO utilities for Bitcoin, including address validation, raw transaction decoding, and HD wallet address derivation.
Provides UTXO utilities for Bitcoin Cash, including address validation, raw transaction decoding, address format conversion (legacy/CashAddr), and HD wallet address derivation.
Provides UTXO utilities for Dash, including address validation, raw transaction decoding, and HD wallet address derivation.
Provides UTXO utilities for Dogecoin, including address validation, raw transaction decoding, and HD wallet address derivation.
Provides EVM utilities for Ethereum, including address validation, raw transaction decoding, and HD wallet address derivation.
Provides UTXO utilities for Litecoin, including address validation, raw transaction decoding, and HD wallet address derivation.
Provides XRP utilities, including address validation, X-Address encoding/decoding, and HD wallet address derivation.
Provides UTXO utilities for Zcash, including address validation, raw transaction decoding, and HD wallet address derivation.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@cryptoapis-io/mcp-utils Validate bitcoin address 1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@cryptoapis-io/mcp-utils
MCP server for Crypto APIs Utils product. Validate addresses, decode raw transactions, and XRP X-Address encode/decode.
API Version: Compatible with Crypto APIs version 2024-12-12
Features
UTXO utils: Validate address, decode raw transaction hex (bitcoin, bitcoin-cash, litecoin, dogecoin, dash, zcash)
EVM utils: Validate address, decode raw transaction hex
XRP utils: Validate address, decode X-Address, encode X-Address
Derive addresses: Derive HD wallet (xPub/yPub/zPub) change or receiving addresses without syncing
Related MCP server: @cryptoapis-io/mcp-prepare-transactions
Prerequisites
Installation
npm install @cryptoapis-io/mcp-utilsOr install all Crypto APIs MCP servers: npm install @cryptoapis-io/mcp
Usage
# Run with API key
npx @cryptoapis-io/mcp-utils --api-key YOUR_API_KEY
# Or use environment variable
export CRYPTOAPIS_API_KEY=YOUR_API_KEY
npx @cryptoapis-io/mcp-utils
# HTTP transport (listens on 127.0.0.1; see "Exposing the server beyond localhost")
npx @cryptoapis-io/mcp-utils --transport http --port 3000 --api-key YOUR_API_KEYClaude 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-utils": {
"command": "npx",
"args": ["-y", "@cryptoapis-io/mcp-utils"],
"env": {
"CRYPTOAPIS_API_KEY": "your_api_key_here"
}
}
}
}Cursor
Add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):
{
"mcpServers": {
"cryptoapis-utils": {
"command": "npx",
"args": ["-y", "@cryptoapis-io/mcp-utils"],
"env": {
"CRYPTOAPIS_API_KEY": "your_api_key_here"
}
}
}
}MCP Inspector
npx @modelcontextprotocol/inspector npx @cryptoapis-io/mcp-utils --api-key YOUR_API_KEYn8n
Start the server in HTTP mode:
npx @cryptoapis-io/mcp-utils --transport http --port 3000 --api-key YOUR_API_KEYIn 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:
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.
Available Tools
utxo_utils
Action | Description |
| Check if a UTXO address is valid. Requires blockchain, network, address |
| Decode a raw transaction hex. Requires blockchain, network, rawTransactionHex |
| Convert Bitcoin Cash address between legacy and CashAddr formats. Requires network, address (Bitcoin Cash only, no blockchain parameter) |
Supported Blockchains: bitcoin, bitcoin-cash, litecoin, dogecoin, dash, zcash
evm_utils
Action | Description |
| Check if an EVM address is valid. Requires blockchain, network, address |
| Decode a raw transaction hex. Requires blockchain, network, rawTransactionHex |
xrp_utils
Action | Description |
| Check if an XRP address is valid. Requires network, address |
| Decode X-Address to classic address and tag. Requires network, xAddress |
| Encode classic address and tag to X-Address. Requires network, classicAddress, addressTag |
derive_addresses
Derive HD wallet (xPub/yPub/zPub) change or receiving addresses without syncing. Derives up to 10 addresses per call.
Parameter | Description |
| Target blockchain |
| Network name |
| xPub/yPub/zPub for the HD wallet |
| Address format (optional): p2pkh, p2sh, p2wpkh, standard, p2sh-cash, p2pkh-cash, classic, base58 |
| Number of addresses to derive, up to 10 (optional) |
| If true, derive change address(es); if false, derive receiving/deposit (optional, UTXO only) |
| Starting index for derivation (optional) |
Supported Blockchains: bitcoin, bitcoin-cash, litecoin, dogecoin, dash, zcash, ethereum, ethereum-classic, binance-smart-chain, xrp, tron
CLI Arguments
Argument | Description | Default |
| Crypto APIs API key |
|
| Transport type: |
|
| HTTP host (use |
|
| Bearer token callers must send ( |
|
| Comma-separated | — |
| HTTP port |
|
| HTTP path |
|
| Enable stateless HTTP mode |
|
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-keyrequest headers are ignored.Without
--api-key: Each request must include anx-api-keyheader 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-utils --transport http --port 3000
# Clients send x-api-key header with each requestExposing 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-utils --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-utils --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
Available Tools
5 toolsderive_addressesDerive addresses from an extended public keyARead-onlyIdempotent
Utils: derive HD wallet (xPub, yPub, zPub) change or receiving addresses without syncing.
GET /utils/{blockchain}/{network}/xpubs/{extendedPublicKey}/derive-addresses Derives up to 10 addresses. By default creates receiving/deposit address; set isChange=true for change address (UTXO only).
Credits by action (source: OpenAPI): • binance-smart-chain: 25 • bitcoin: 10 • bitcoin-cash: 12 • dash: 11 • dogecoin: 11 • ethereum: 10 • ethereum-classic: 13 • litecoin: 11 • tron: 15 • xrp: 10 • zcash: 13
Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers.
Inputs: network (required), blockchain (required), extendedPublicKey (required), context, +4 more.
evm_utilsEVM address and transaction utilitiesARead-onlyIdempotent
EVM utils (Utils product): validate address, decode raw transaction hex.
Actions: • validate-address: Check if an EVM address is valid • decode-raw-transaction: Decode a raw transaction hex
Blockchain → Networks: • ethereum: mainnet, sepolia • ethereum-classic: mainnet, mordor • binance-smart-chain: mainnet, testnet • tron: mainnet, nile
Credits by action (source: OpenAPI): • decode-raw-transaction: binance-smart-chain 25, ethereum 10, ethereum-classic 13, tron 15 • validate-address: binance-smart-chain 25, ethereum 10, ethereum-classic 13, tron 15
Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers.
Inputs: action (required), network (required), blockchain (required), address, +2 more.
system_infoCryptoAPIs reference infoARead-onlyIdempotent
CryptoAPIs reference documentation — no API call, no credits consumed.
Actions: • blockchains — Supported blockchains, networks, products per chain, denominations, fiat currencies • errors — Complete error code table (HTTP status, error code, message) • credits — Credit charging structure, cost multipliers per blockchain, monitoring & operations taxes (xPub, synced addresses, blockchain events), pay-as-you-go • callbacks — Webhook mechanics: URL requirements, retry strategy (5 retries, exponential backoff), HMAC security, idempotency • limits — Throughput soft/hard limits per plan, 2.1x penalty multiplier, rate limiting behavior
Inputs: action (required), context.
utxo_utilsUTXO address and transaction utilitiesARead-onlyIdempotent
UTXO utils (Utils product): validate address, decode raw transaction hex, convert Bitcoin Cash address.
Actions: • validate-address: Check if a UTXO address is valid • decode-raw-transaction: Decode a raw transaction hex • convert-bitcoin-cash-address: Convert Bitcoin Cash address (legacy ↔ cash format); Bitcoin Cash only, no blockchain parameter (network + address)
Blockchain → Networks: • bitcoin: mainnet, testnet • bitcoin-cash: mainnet, testnet • litecoin: mainnet, testnet • dogecoin: mainnet, testnet • dash: mainnet, testnet • zcash: mainnet, testnet
Credits by action (source: OpenAPI): • convert-bitcoin-cash-address: bitcoin-cash 12 • decode-raw-transaction: bitcoin 10, bitcoin-cash 12, dash 11, dogecoin 11, litecoin 11, zcash 13 • validate-address: bitcoin 10, bitcoin-cash 12, dash 11, dogecoin 11, litecoin 11, zcash 13
Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers.
Inputs: action (required), network (required), address, context, +2 more.
xrp_utilsXRP address utilitiesARead-onlyIdempotent
XRP utils (Utils product): validate address, decode/encode X-Address.
Actions: • validate-address: Check if an XRP address is valid • decode-x-address: Decode X-Address to classic address and tag • encode-x-address: Encode classic address and tag to X-Address
Networks: mainnet, testnet
Credits by action (source: OpenAPI): • decode-x-address: 10 • encode-x-address: 10 • validate-address: 10
Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers.
Inputs: action (required), network (required), address, context, +3 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
The three chain-family utils tools (utxo, evm, xrp) each repeat the same validate-address/decode actions, but their descriptions explicitly enumerate which blockchains belong to each family, so an agent can route correctly. derive_addresses and system_info are clearly distinct. The only residual ambiguity is remembering which chain falls in which family bucket.
Four of five tools follow a predictable snake_case <domain>_utils / system_info noun pattern, which is coherent. derive_addresses breaks the pattern by being an action name rather than a utils family, a minor but noticeable deviation.
Five tools for an address/transaction utilities surface is well-scoped and each earns its place by bundling multiple actions. It sits at the lean end, with derive_addresses getting its own tool while validate/decode are grouped.
The surface covers address validation, raw tx decoding, HD address derivation, X-Address encode/decode, and reference docs across all supported chains — a solid utility lifecycle. Minor gaps exist in that derivation is exposed only for xpubs and other format conversions (beyond BCH) are absent, but agents can work around these.
Maintenance
Related MCP Connectors
Remote MCP server exposing 330 production AI-agent services for web/data processing, validation, AI utilities, blockchain/crypto utilities, and x402 pay-per-use access.
Combined Crypto APIs MCP server — all 14 products in one process
Free MCP server of security & dev API tools -- supply-chain, CVE, DNS, WHOIS, OFAC, Cosmos SDK.
Tenzro Network MCP server: wallet, identity, payments, inference, staking, bridges, verification.
Related MCP Servers
- AlicenseAqualityBmaintenanceMCP server for Crypto APIs Blockchain Fees product, providing fee recommendations and gas estimates for UTXO, EVM, and XRP blockchains.689 npmMIT
- AlicenseAqualityBmaintenanceMCP server for Crypto APIs Prepare Transactions product that builds unsigned EVM transactions for native coin, fungible token (ERC-20), and NFT (ERC-721) transfers.8305 npmMIT
- AlicenseNot gradedqualityBmaintenanceMCP server for Crypto APIs HD Wallet (Wallet as a Service) product. Track and manage HD wallets by their extended public key (xPub/yPub/zPub) — no private keys ever leave your device.181 npm1MIT
- AlicenseAqualityBmaintenanceMCP server for Crypto APIs Block Data product. Get block details by height or hash for EVM, UTXO, and XRP blockchains.4328 npmMIT