MCP Hd Wallet

@cryptoapis-io/mcp-hd-wallet

MCP 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.

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

How It Works

HD (Hierarchical Deterministic) wallets derive all addresses from a single extended public key (xPub). You sync your xPub with Crypto APIs, and the service tracks all derived addresses, balances, and transactions on your behalf.

1. Sync your xPub — provide your extended public key (xPub, yPub, or zPub) to start tracking
2. Derive addresses — generate new receiving and change addresses from the xPub
3. Query wallet data — get balances, list transactions, list UTXOs, and view assets across all derived addresses
4. Prepare transactions — build unsigned transactions ready for local signing with @cryptoapis-io/mcp-signer

Your private keys are never sent to or stored by Crypto APIs. Only the extended public key is used for address derivation and balance tracking.

Features

• Sync wallets by extended public key (xPub/yPub/zPub)
• Derive receiving and change addresses from the xPub
• Query aggregated balances, transactions, and assets across all derived addresses
• List UTXOs for UTXO-based wallets
• Prepare unsigned transactions directly from wallet
• Supports EVM (Ethereum, Ethereum Classic, BSC, Polygon, Avalanche (C-Chain), Arbitrum, Base, Optimism, Tron), UTXO (Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash), and XRP

Prerequisites

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

Installation

npm install @cryptoapis-io/mcp-hd-wallet

Or install all Crypto APIs MCP servers: npm install @cryptoapis-io/mcp

Usage

# Run with API key

npx @cryptoapis-io/mcp-hd-wallet --api-key YOUR_API_KEY

Or use environment variable

export CRYPTOAPIS_API_KEY=YOUR_API_KEY npx @cryptoapis-io/mcp-hd-wallet

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

npx @cryptoapis-io/mcp-hd-wallet --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-hd-wallet": { "command": "npx", "args": ["-y", "@cryptoapis-io/mcp-hd-wallet"], "env": { "CRYPTOAPIS_API_KEY": "your_api_key_here" } } } }

Cursor

Add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):

{

"mcpServers": { "cryptoapis-hd-wallet": { "command": "npx", "args": ["-y", "@cryptoapis-io/mcp-hd-wallet"], "env": { "CRYPTOAPIS_API_KEY": "your_api_key_here" } } } }

MCP Inspector

npx @modelcontextprotocol/inspector npx @cryptoapis-io/mcp-hd-wallet --api-key YOUR_API_KEY

n8n

1. Start the server in HTTP mode:

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

1. In your n8n workflow, add an AI Agent node
2. 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

manage_hd_wallet

Manage HD wallets (sync, activate, delete, list, status).

hd_wallet_data_utxo

Query UTXO HD wallet data (Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash).

hd_wallet_data_evm

Query EVM HD wallet data (Ethereum, Ethereum Classic, BSC, Polygon, Avalanche (C-Chain), Arbitrum, Base, Optimism, Tron).

hd_wallet_data_xrp

Query XRP HD wallet data.

CLI Arguments

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-hd-wallet --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-hd-wallet --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-hd-wallet --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