@cryptoapis-io/mcp-address-history
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CRYPTOAPIS_API_KEY | Yes | Your Crypto APIs API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| manage_addressA | Manage synced addresses for Address History APIs. Cursor pagination for 'list': use 'nextStartingAfter' as 'startingAfter'. Actions: • sync: Add new address to sync (requires 'address') • list: Get all synced addresses for blockchain/network • activate: Reactivate a paused address (requires 'address') • delete: Remove synced address (requires 'address') Blockchain → Networks: • ethereum: mainnet, sepolia • ethereum-classic: mainnet, mordor • binance-smart-chain: mainnet, testnet • polygon: mainnet, amoy • tron: mainnet, nile • avalanche (C-Chain): mainnet, fuji • arbitrum: mainnet, sepolia • base: mainnet, sepolia • optimism: mainnet, sepolia • bitcoin: mainnet, testnet • bitcoin-cash: mainnet, testnet • litecoin: mainnet, testnet • dogecoin: mainnet, testnet • dash: mainnet, testnet • zcash: mainnet, testnet Note: 'sync', 'activate', 'delete' actions require confirmation. They return a preview with a one-time token instead of executing immediately. Credits by action (source: OpenAPI): • activate: 30 • delete: 30 • list: 30 • sync: 30 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. |
| evm_address_historyA | Query EVM address full history (requires synced address). Cursor pagination: use 'nextStartingAfter' from response as 'startingAfter'. Actions & supported blockchains: • get-statistics: ethereum, ethereum-classic • list-transactions: ethereum, ethereum-classic, binance-smart-chain, polygon, tron • list-transactions-by-timestamp: ethereum, ethereum-classic (requires timestamp) • list-token-transfers: ethereum, polygon, tron, ethereum-classic, binance-smart-chain • list-internal-transactions: ethereum, polygon, tron, ethereum-classic, binance-smart-chain • list-tokens: ethereum, polygon, tron, ethereum-classic, binance-smart-chain Blockchain → Networks: • ethereum: mainnet, sepolia • ethereum-classic: mainnet, mordor • binance-smart-chain: mainnet, testnet • polygon: mainnet, amoy • tron: mainnet, nile • avalanche (C-Chain): mainnet, fuji • arbitrum: mainnet, sepolia • base: mainnet, sepolia • optimism: mainnet, sepolia Credits by action (source: OpenAPI): • get-statistics: binance-smart-chain 575, ethereum 230, ethereum-classic 299, polygon 460, tron 345 • list-internal-transactions: binance-smart-chain 825, ethereum 330, ethereum-classic 429, polygon 660, tron 495 • list-token-transfers: binance-smart-chain 575, ethereum 230, ethereum-classic 299, polygon 460, tron 345 • list-tokens: binance-smart-chain 575, ethereum 230, ethereum-classic 299, polygon 460, tron 345 • list-transactions: binance-smart-chain 325, ethereum 130, ethereum-classic 169, polygon 260, tron 195 • list-transactions-by-timestamp: binance-smart-chain 575, ethereum 230, ethereum-classic 299, polygon 460, tron 345 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. |
| utxo_address_historyA | Query UTXO address full history (requires synced address). Pagination: • list-transactions, list-transactions-by-timestamp: cursor pagination (use 'nextStartingAfter' → 'startingAfter') • list-unspent-outputs: offset pagination (use 'offset', response has 'total') Actions & supported blockchains: • get-statistics: bitcoin, bitcoin-cash • list-transactions: bitcoin, bitcoin-cash, litecoin, dogecoin, dash, zcash • list-transactions-by-timestamp: bitcoin, bitcoin-cash (requires timestamp) • list-unspent-outputs: bitcoin, bitcoin-cash, litecoin, dogecoin, dash, zcash (uses offset pagination) Blockchain → Networks: • bitcoin: mainnet, testnet • bitcoin-cash: mainnet, testnet • litecoin: mainnet, testnet • dogecoin: mainnet, testnet • dash: mainnet, testnet • zcash: mainnet, testnet Credits by action (source: OpenAPI): • get-statistics: bitcoin 530, bitcoin-cash 689, dash 583, dogecoin 583, litecoin 583, zcash 689 • list-transactions: bitcoin 130, bitcoin-cash 169, dash 143, dogecoin 143, litecoin 143, zcash 169 • list-transactions-by-timestamp: bitcoin 530, bitcoin-cash 689, dash 583, dogecoin 583, litecoin 583, zcash 689 • list-unspent-outputs: bitcoin 530, bitcoin-cash 689, dash 583, dogecoin 583, litecoin 583, zcash 689 Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers. |
| system_infoA | CryptoAPIs reference documentation — no API call, no credits consumed. Actions: • blockchains — Supported blockchains, networks, products per chain, denominations, fiat currencies • errors — Complete error code table (HTTP status, error code, message) • credits — Credit charging structure, cost multipliers per blockchain, monitoring & operations taxes (xPub, synced addresses, blockchain events), pay-as-you-go • callbacks — Webhook mechanics: URL requirements, retry strategy (5 retries, exponential backoff), HMAC security, idempotency • limits — Throughput soft/hard limits per plan, 2.1x penalty multiplier, rate limiting behavior |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| sync-and-query-history | Sync an address for history tracking and query its transaction history |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| supported-chains | Supported blockchains, networks, and actions for address history queries and management |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: manage_address handles syncing, evm_address_history and utxo_address_history query different blockchain types, and system_info provides reference. No overlap or ambiguity between tools.
Tool names are readable and predictable, but there is a minor inconsistency: manage_address follows a verb_noun pattern while the other three are noun phrases. The two address history tools share a consistent naming convention, keeping the set mostly coherent.
Four tools is well-scoped for an address history server, covering management, querying for EVM and UTXO chains, and reference. Each tool is essential and earns its place without overwhelming the agent.
The tool set covers the core lifecycle: syncing addresses (manage_address) and querying full history for EVM and UTXO chains. Missing a direct balance/address details tool is a minor gap, but the included actions cover the main use cases for address history.