{
  "markdown": "# @cryptoapis-io/mcp-hd-wallet\n\nMCP server for [Crypto APIs](https://cryptoapis.io/) 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.\n\n> **API Version:** Compatible with Crypto APIs version **2024-12-12**\n\n## How It Works\n\nHD (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.\n\n1. **Sync your xPub** — provide your extended public key (xPub, yPub, or zPub) to start tracking\n2. **Derive addresses** — generate new receiving and change addresses from the xPub\n3. **Query wallet data** — get balances, list transactions, list UTXOs, and view assets across all derived addresses\n4. **Prepare transactions** — build unsigned transactions ready for local signing with `@cryptoapis-io/mcp-signer`\n\nYour private keys are **never** sent to or stored by Crypto APIs. Only the extended public key is used for address derivation and balance tracking.\n\n## Features\n\n- Sync wallets by extended public key (xPub/yPub/zPub)\n- Derive receiving and change addresses from the xPub\n- Query aggregated balances, transactions, and assets across all derived addresses\n- List UTXOs for UTXO-based wallets\n- Prepare unsigned transactions directly from wallet\n- Supports EVM (Ethereum, Ethereum Classic, BSC, Polygon, Avalanche (C-Chain), Arbitrum, Base, Optimism, Tron), UTXO (Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash), and XRP\n\n## Prerequisites\n\n- Node.js 18+\n- [Crypto APIs](https://cryptoapis.io/) account and API key ([sign up](https://app.cryptoapis.io/signup) | [get API key](https://app.cryptoapis.io/api-keys))\n\n## Installation\n\n```bash\nnpm install @cryptoapis-io/mcp-hd-wallet\n```\n\nOr install all Crypto APIs MCP servers: `npm install @cryptoapis-io/mcp`\n\n## Usage\n\n```bash\n# Run with API key\nnpx @cryptoapis-io/mcp-hd-wallet --api-key YOUR_API_KEY\n\n# Or use environment variable\nexport CRYPTOAPIS_API_KEY=YOUR_API_KEY\nnpx @cryptoapis-io/mcp-hd-wallet\n\n# HTTP transport\nnpx @cryptoapis-io/mcp-hd-wallet --transport http --port 3000 --api-key YOUR_API_KEY\n```\n\n### Claude Desktop\n\nAdd to your Claude Desktop config (`~/Library/Application Support/Claude/claude_desktop_config.json` on macOS, `%APPDATA%\\Claude\\claude_desktop_config.json` on Windows):\n\n```json\n{\n  \"mcpServers\": {\n    \"cryptoapis-hd-wallet\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"@cryptoapis-io/mcp-hd-wallet\"],\n      \"env\": {\n        \"CRYPTOAPIS_API_KEY\": \"your_api_key_here\"\n      }\n    }\n  }\n}\n```\n\n### Cursor\n\nAdd to `.cursor/mcp.json` (project) or `~/.cursor/mcp.json` (global):\n\n```json\n{\n  \"mcpServers\": {\n    \"cryptoapis-hd-wallet\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"@cryptoapis-io/mcp-hd-wallet\"],\n      \"env\": {\n        \"CRYPTOAPIS_API_KEY\": \"your_api_key_here\"\n      }\n    }\n  }\n}\n```\n\n### MCP Inspector\n\n```bash\nnpx @modelcontextprotocol/inspector npx @cryptoapis-io/mcp-hd-wallet --api-key YOUR_API_KEY\n```\n\n### n8n\n\n1. Start the server in HTTP mode:\n   ```bash\n   npx @cryptoapis-io/mcp-hd-wallet --transport http --port 3000 --api-key YOUR_API_KEY\n   ```\n2. In your n8n workflow, add an **AI Agent** node\n3. Under **Tools**, add an **MCP Client Tool** and set the URL to `http://localhost:3000/mcp`\n\n> All servers default to port 3000. Use `--port` to assign different ports when running multiple servers.\n\n## Available Tools\n\n### `manage_hd_wallet`\n\nManage HD wallets (sync, activate, delete, list, status).\n\n| Action | Description |\n|--------|-------------|\n| `sync-wallet` | Sync an HD wallet by extended public key (xPub/yPub/zPub) |\n| `list-wallets` | List all synced HD wallets |\n| `activate-wallet` | Activate a previously synced wallet |\n| `delete-wallet` | Delete a synced wallet |\n| `get-status` | Get sync status of a wallet |\n\n### `hd_wallet_data_utxo`\n\nQuery UTXO HD wallet data (Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash).\n\n| Action | Description |\n|--------|-------------|\n| `get-details` | Get wallet balance and details |\n| `derive-receiving-address` | Derive next receiving address |\n| `derive-change-address` | Derive next change address |\n| `list-addresses` | List all derived addresses |\n| `list-transactions` | List wallet transactions |\n| `list-utxos` | List unspent transaction outputs |\n| `list-assets` | List assets held by wallet |\n| `prepare-transaction` | Prepare an unsigned transaction from wallet |\n\n### `hd_wallet_data_evm`\n\nQuery EVM HD wallet data (Ethereum, Ethereum Classic, BSC, Polygon, Avalanche (C-Chain), Arbitrum, Base, Optimism, Tron).\n\n| Action | Description |\n|--------|-------------|\n| `get-details` | Get wallet balance and details |\n| `derive-receiving-address` | Derive next receiving address |\n| `list-addresses` | List all derived addresses |\n| `list-transactions` | List wallet transactions |\n| `list-assets` | List tokens held by wallet |\n| `prepare-transaction` | Prepare an unsigned transaction from wallet |\n\n### `hd_wallet_data_xrp`\n\nQuery XRP HD wallet data.\n\n| Action | Description |\n|--------|-------------|\n| `get-details` | Get wallet balance and details |\n| `derive-receiving-address` | Derive next receiving address |\n| `list-addresses` | List all derived addresses |\n| `list-transactions` | List wallet transactions |\n| `list-assets` | List assets held by wallet |\n\n## CLI Arguments\n\n| Argument | Description | Default |\n|----------|-------------|---------|\n| `--api-key` | Crypto APIs API key | `CRYPTOAPIS_API_KEY` env var |\n| `--transport` | Transport type: `stdio` or `http` | `stdio` |\n| `--host` | HTTP host | `0.0.0.0` |\n| `--port` | HTTP port | `3000` |\n| `--path` | HTTP path | `/mcp` |\n| `--stateless` | Enable stateless HTTP mode | `false` |\n\n### HTTP API Key Modes\n\nWhen using HTTP transport, the server supports two API key modes:\n\n- **With `--api-key`:** The key is used for all requests. `x-api-key` request headers are ignored.\n- **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.\n\n```bash\n# Per-request key mode (multi-tenant)\nnpx @cryptoapis-io/mcp-hd-wallet --transport http --port 3000\n# Clients send x-api-key header with each request\n```\n\n> Stdio transport always requires an API key at startup.\n\n## Important: API Key Required\n\n> **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.\n\n## Remote MCP Server\n\nCrypto APIs provides an official remote MCP server with all tools available via HTTP Streamable transport at [https://ai.cryptoapis.io/mcp](https://ai.cryptoapis.io/mcp). Pass your API key via the `x-api-key` header — no installation required.\n\n## License\n\nMIT\n",
  "bytes": 6956,
  "sha": "eaca2cb7e1159694bb5d2ca01cc452c7344ec9edd18925f051b25098b37bb732",
  "repo_slug": "cryptoapis-io/cryptoapis-mcp-hd-wallet",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_cryptoapis_io_mcp_hd_wallet_fa3d44e9/readme"
}