CryptoAPIs MCP HD Wallet

by cryptoapis-io

Not rated
GitHub

About

MCP server for HD wallet management, balance retrieval, and sync on EVM, UTXO, and XRP blockchains via Crypto APIs

Details

Author
cryptoapis-io
Categories
Other, Finance

Setup

Install CryptoAPIs MCP HD Wallet in your MCP client (Claude Desktop, Cursor, Windsurf, and others).

Repository: https://github.com/cryptoapis-io/cryptoapis-mcp-hd-wallet

Follow the installation instructions in the repository README, then restart your MCP client.

MCP server for HD wallet management, balance retrieval, and sync on EVM, UTXO, and XRP blockchains via Crypto APIs

MCP server forCrypto APIsHD Wallet (Wallet as a Service) product. Track and manage HD wallets by theirextended public key (xPub/yPub/zPub)— no private keys ever leave your device.

API Version:Compatible with Crypto APIs version2024-12-12

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

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

- 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

- Node.js 18+
-
Crypto APIsaccount and API key (sign up|get API key)

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

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

# 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 npx @cryptoapis-io/mcp-hd-wallet --transport http --port 3000 --api-key YOUR_API_KEY

Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.jsonon macOS,%APPDATA%\Claude\claude_desktop_config.jsonon Windows):

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

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" } } } }
npx @modelcontextprotocol/inspector npx @cryptoapis-io/mcp-hd-wallet --api-key YOUR_API_KEY

- Start the server in HTTP mode:

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

All servers default to port 3000. Use--portto assign different ports when running multiple servers.

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

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

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

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-hd-wallet --transport http --port 3000 # Clients send x-api-key header with each request

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 athttps://ai.cryptoapis.io/mcp. Pass your API key via thex-api-keyheader — no installation required.

MCP to interface with multiple blockchains, staking, DeFi, swap, bridging, wallet management, DCA, Limit Orders, Coin Lookup, Tracking and more.

Bitcoin-native MCP server for AI agents: BTC/STX wallets, DeFi yield, sBTC peg, NFTs, and x402 payments.

MCP server for dry-run EVM transaction simulation via Crypto APIs

Pool data, swap rates, and liquidity info on Curve Finance.

Official deBridge protocol MCP Server. Finds optimal cross-chain swap routes, checks fees and conditions, initiates trades across major blockchain networks

MCP server for DeFi data — real-time crypto prices, token analytics, wallet balances, and on-chain data across multiple chains.

Cross-protocol DeFi yield opportunities with risk metrics via DefiLlama. 16,000+ pools across 60+ chains. Risk classification, APY trends, and yield comparison.

MCP server for DeFi execution — lets AI agents swap, provide liquidity, lend, bridge, and run yield strategies across 22 chains in a single transaction.

MCP server exposing 90+ crypto API tools with automatic x402 USDC micropayment handling — gas oracle, token lookup, wallet risk analysis, market mood, and more on Base.

MCP server for Limitless Exchange prediction markets on Base. 34 tools for market access, limit order trading, wallet management, and position tracking.

No reviews yet — be the first

Sign in to leave a review

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.