{
  "markdown": "# @cryptoapis-io/mcp-address-history\n\nMCP server for [Crypto APIs](https://cryptoapis.io/) Address History product. Query full blockchain address transaction history for synced addresses.\n\n> **API Version:** Compatible with Crypto APIs version **2024-12-12**\n\n## Features\n\n- Query complete EVM address history (Ethereum, Ethereum Classic, BSC, Polygon, Tron)\n- Query complete UTXO address history (Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash)\n- Manage address sync (activate, sync, delete, list)\n- Query by timestamp range\n- Cursor-based pagination for large result sets\n\n## Prerequisites\n\nTo use this MCP server, you need:\n1. [Register at Crypto APIs](https://app.cryptoapis.io/signup)\n2. [Generate an API key](https://app.cryptoapis.io/api-keys) from your dashboard\n\n## Installation\n\n```bash\nnpm install @cryptoapis-io/mcp-address-history\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-address-history --api-key YOUR_API_KEY\n\n# Or use environment variable\nexport CRYPTOAPIS_API_KEY=YOUR_API_KEY\nnpx @cryptoapis-io/mcp-address-history\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-address-history\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"@cryptoapis-io/mcp-address-history\"],\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-address-history\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"@cryptoapis-io/mcp-address-history\"],\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-address-history --api-key YOUR_API_KEY\n```\n\n### n8n\n\n1. Start the server in HTTP mode:\n   ```bash\n   npx @cryptoapis-io/mcp-address-history --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_address`\n\nManage synced addresses for historical data access. Supports all EVM and UTXO blockchains.\n\n**Actions:**\n\n| Action | Description |\n|--------|-------------|\n| `sync` | Sync a new address for historical data |\n| `activate` | Activate a previously synced address |\n| `delete` | Delete a synced address |\n| `list` | List all synced addresses |\n\n### `evm_address_history`\n\nQuery EVM address full history (requires synced address).\n\n**Actions:**\n\n| Action | Description |\n|--------|-------------|\n| `get-statistics` | Get address statistics |\n| `list-transactions` | List all transactions |\n| `list-transactions-by-timestamp` | List transactions from a timestamp |\n| `list-token-transfers` | List token transfers |\n| `list-internal-transactions` | List internal transactions |\n| `list-tokens` | List tokens held by address |\n\n**Supported Blockchains:** ethereum, ethereum-classic, binance-smart-chain, polygon, tron\n\n> **Note:** `get-statistics` and `list-transactions-by-timestamp` only support Ethereum and Ethereum Classic. Other actions support all five blockchains.\n\n### `utxo_address_history`\n\nQuery UTXO address full history (requires synced address).\n\n**Actions:**\n\n| Action | Description | Pagination |\n|--------|-------------|------------|\n| `get-statistics` | Get address statistics | - |\n| `list-transactions` | List all transactions | cursor |\n| `list-transactions-by-timestamp` | List transactions from timestamp | cursor |\n| `list-unspent-outputs` | List unspent outputs (UTXOs) | offset |\n\n**Supported Blockchains:** bitcoin, bitcoin-cash, litecoin, dogecoin, dash, zcash\n\n## Pagination\n\nMost endpoints use **cursor-based pagination**:\n\n```json\n// Response\n{\n  \"items\": [...],\n  \"limit\": 10,\n  \"hasMore\": true,\n  \"nextStartingAfter\": \"abc123\"\n}\n```\n\nUse `nextStartingAfter` value as `startingAfter` parameter in the next request.\n\n**Exception:** `list-unspent-outputs` uses **offset pagination**:\n\n```json\n// Response\n{\n  \"items\": [...],\n  \"limit\": 10,\n  \"offset\": 0,\n  \"total\": 150\n}\n```\n\n## Configuration\n\nFor **stdio** transport, provide the API key at startup via CLI argument or environment variable. For **HTTP** transport, it can also be provided per-request via `x-api-key` header (see [HTTP API Key Modes](#http-api-key-modes)).\n\n1. **Command-line argument** (recommended):\n   ```bash\n   npx @cryptoapis-io/mcp-address-history --api-key {your_api_key}\n   ```\n\n2. **Environment variable**:\n   ```bash\n   export CRYPTOAPIS_API_KEY={your_api_key}\n   ```\n\n### CLI Arguments\n\n| Argument | Description |\n|----------|-------------|\n| `--api-key` | Crypto APIs API key |\n| `--transport` | Transport type: `stdio` (default) or `http` |\n| `--host` | HTTP host (default: `0.0.0.0`) |\n| `--port` | HTTP port (default: `3000`) |\n| `--path` | HTTP path (default: `/mcp`) |\n| `--stateless` | Enable stateless mode for HTTP |\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-address-history --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": 6442,
  "sha": "5fdef24c6eddcff61952777cf36c1cbb01eb058b2e44dc5e4ca3d38a2bc09df0",
  "repo_slug": "cryptoapis-io/cryptoapis-mcp-address-history",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_cryptoapis_io_mcp_address_hist_07ab874a/readme"
}