manage_hd_walletLABSCO SUMMARY
Watch a whole wallet without handing over the keys to it.
An xPub is enough to see everything a wallet has ever received, and not enough to spend a satoshi of it. That split is the entire point: an agent gets full read of balances, history and UTXOs across chains, and the ability to spend stays on your side of the line.
What it is
An MCP server for Crypto APIs' HD Wallet (Wallet as a Service) product. You hand it an extended public key — xPub, yPub or zPub — and Crypto APIs derives and watches every address underneath it. Built against a dated Crypto APIs release.
What you get
- A wallet synced from its extended public key, and activated for tracking
- Every wallet you have synced, listed, and the sync status of any one of them
- New receiving and change addresses derived from the xPub
- Balances, transactions and assets aggregated across all derived addresses
- UTXOs listed for UTXO-based wallets
- Unsigned transactions prepared straight from the wallet, ready to sign locally
- Coverage across EVM chains (Ethereum, Ethereum Classic, BSC, Polygon, Avalanche C-Chain, Arbitrum, Base, Optimism, Tron), UTXO chains (Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash) and XRP
Requirements
Node.js 18 or newer, a Crypto APIs account and an API key — passed on the launch command or set in CRYPTOAPIS_API_KEY. Only the extended public key is sent: private keys are never transmitted to or stored by Crypto APIs. Signing is a separate step — pair it with @cryptoapis-io/mcp-signer to turn a prepared transaction into a broadcastable one.
Setup effort
One command plus a key — npm install @cryptoapis-io/mcp-hd-wallet, then supply credentials
USE CASES
01
Putting a wallet under watch for the first time
Sync the extended public key and activate tracking, so Crypto APIs starts deriving addresses under it.
02
Knowing when the numbers are safe to read
Check the sync status before quoting a balance — a half-synced wallet reads low.
03
Keeping track of which wallets you are watching
List the wallets synced under your account, so a stale xPub does not sit there unnoticed.
04
Working out which coins are spendable
Read the UTXOs across the wallet's derived addresses rather than address by address.
05
Running the wallet day to day
Derive a fresh receiving or change address and manage the wallet's tracked state as it changes.
06
Retiring a wallet you no longer follow
Remove it so it stops being derived and counted.
4 tools
Listed in project docs. Your client may show a different list.
hd_wallet_data_utxohd_wallet_data_evmhd_wallet_data_xrpBEFORE YOU INSTALL
What to know first
Tools you get
4 tools named in the project's documentation.
Requires
- npx on PATH
- Node.js 18+
- CRYPTOAPIS_API_KEY in your environment
INSTALLATION
Connect your client
Server setup
TERMINAL
npm install @cryptoapis-io/mcp-hd-walletMCP Clients
Claude Desktop, Cursor
JSON
{
"mcpServers": {
"cryptoapis-hd-wallet": {
"command": "npx",
"args": [
"-y",
"@cryptoapis-io/mcp-hd-wallet"
],
"env": {
"CRYPTOAPIS_API_KEY": "<YOUR_CRYPTOAPIS_API_KEY>"
}
}
}
}n8n — HTTP server
Start the server in HTTP mode. All Crypto APIs servers default to port 3000, so give each one its own --port if you run more than one:
N8N — HTTP SERVER · TERMINAL
npx @cryptoapis-io/mcp-hd-wallet --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, using the port you started this server on.
