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.
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.
- 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
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.
One command plus a key — npm install @cryptoapis-io/mcp-hd-wallet, then supply credentials