What can you do with this server?

MCP server for querying Crypto APIs address history across EVM and UTXO blockchains and managing synced addresses. * Manage synced addresses: sync, list, activate, and delete; sync/activate/delete require confirmation via a one-time token. * Query EVM address history: get-statistics, list-transactions, list-transactions-by-timestamp, list-token-transfers, list-internal-transactions, and list-tokens for Ethereum, Ethereum Classic, BSC, Polygon, and Tron. * Query UTXO address history: get-statistics, list-transactions, list-transactions-by-timestamp, and list-unspent-outputs for Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, and Zcash. * Use cursor-based pagination for most lists and offset pagination for UTXO unspent outputs. * Retrieve Crypto APIs reference docs via system_info: supported blockchains, errors, credits, callbacks, and limits without consuming credits.

Which integrations are available for this server?

Provides tools to query Binance Smart Chain address history, including transactions, token transfers, internal transactions, tokens held, and statistics, with address sync management. Provides tools to query Bitcoin address history, including transactions, statistics, and unspent outputs, with address sync management. Provides tools to query Bitcoin Cash address history, including transactions, statistics, and unspent outputs, with address sync management. Provides tools to query Dash address history, including transactions, statistics, and unspent outputs, with address sync management. Provides tools to query Dogecoin address history, including transactions, statistics, and unspent outputs, with address sync management. Provides tools to query Ethereum address history, including transactions, token transfers, internal transactions, tokens held, and statistics, with address sync management. Provides tools to query Litecoin address history, including transactions, statistics, and unspent outputs, with address sync management. Provides tools to query Polygon address history, including transactions, token transfers, internal transactions, tokens held, and statistics, with address sync management. Provides tools to query Zcash address history, including transactions, statistics, and unspent outputs, with address sync management.

How do I use @cryptoapis-io/mcp-address-history?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@@cryptoapis-io/mcp-address-history List transactions for Bitcoin address 1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

@cryptoapis-io/mcp-address-history

Official

by CryptoAPIs-io

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

@cryptoapis-io/mcp-address-history

MCP server for Crypto APIs Address History product. Query full blockchain address transaction history for synced addresses.

API Version: Compatible with Crypto APIs version 2024-12-12

Features

Query complete EVM address history (Ethereum, Ethereum Classic, BSC, Polygon, Tron)
Query complete UTXO address history (Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash)
Manage address sync (activate, sync, delete, list)
Query by timestamp range
Cursor-based pagination for large result sets

Related MCP server: @cryptoapis-io/mcp-prepare-transactions

Prerequisites

To use this MCP server, you need:

Register at Crypto APIs
Generate an API key from your dashboard

Installation

npm install @cryptoapis-io/mcp-address-history

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

Usage

# Run with API key
npx @cryptoapis-io/mcp-address-history --api-key YOUR_API_KEY

# Or use environment variable
export CRYPTOAPIS_API_KEY=YOUR_API_KEY
npx @cryptoapis-io/mcp-address-history

Claude Desktop

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

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

Cursor

Add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):

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

MCP Inspector

npx @modelcontextprotocol/inspector npx @cryptoapis-io/mcp-address-history --api-key YOUR_API_KEY

n8n

Start the server in HTTP mode:

npx @cryptoapis-io/mcp-address-history --transport http --port 3000 --api-key YOUR_API_KEY

In your n8n workflow, add an AI Agent node
Under Tools, add an MCP Client Tool and set the URL to http://localhost:3000/mcp

n8n in Docker: localhost inside the container is not your machine. Start the server with --host 0.0.0.0 and MCP_AUTH_TOKEN set (see Exposing the server beyond localhost), use http://host.docker.internal:3000/mcp as the URL, and add an Authorization: Bearer <token> header to the MCP Client Tool credential.

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

Available Tools

`manage_address`

Manage synced addresses for historical data access. Supports all EVM and UTXO blockchains.

Actions:

Action	Description
`sync`	Sync a new address for historical data
`activate`	Activate a previously synced address
`delete`	Delete a synced address
`list`	List all synced addresses

`evm_address_history`

Query EVM address full history (requires synced address).

Actions:

Action	Description
`get-statistics`	Get address statistics
`list-transactions`	List all transactions
`list-transactions-by-timestamp`	List transactions from a timestamp
`list-token-transfers`	List token transfers
`list-internal-transactions`	List internal transactions
`list-tokens`	List tokens held by address

Supported Blockchains: ethereum, ethereum-classic, binance-smart-chain, polygon, tron

Note: get-statistics and list-transactions-by-timestamp only support Ethereum and Ethereum Classic. Other actions support all five blockchains.

`utxo_address_history`

Query UTXO address full history (requires synced address).

Actions:

Action	Description	Pagination
`get-statistics`	Get address statistics	-
`list-transactions`	List all transactions	cursor
`list-transactions-by-timestamp`	List transactions from timestamp	cursor
`list-unspent-outputs`	List unspent outputs (UTXOs)	offset

Supported Blockchains: bitcoin, bitcoin-cash, litecoin, dogecoin, dash, zcash

Pagination

Most endpoints use cursor-based pagination:

// Response
{
  "items": [...],
  "limit": 10,
  "hasMore": true,
  "nextStartingAfter": "abc123"
}

Use nextStartingAfter value as startingAfter parameter in the next request.

Exception: list-unspent-outputs uses offset pagination:

// Response
{
  "items": [...],
  "limit": 10,
  "offset": 0,
  "total": 150
}

Configuration

For 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).

Command-line argument (recommended):

npx @cryptoapis-io/mcp-address-history --api-key {your_api_key}

Environment variable:

export CRYPTOAPIS_API_KEY={your_api_key}

CLI Arguments

Argument	Description
`--api-key`	Crypto APIs API key
`--transport`	Transport type: `stdio` (default) or `http`
`--host`	HTTP host (default: `127.0.0.1`; use `0.0.0.0` to accept remote connections — requires an auth token with `--api-key`)
`--auth-token`	Bearer token callers must send (`Authorization: Bearer <token>`); prefer the `MCP_AUTH_TOKEN` env var
`--allowed-hosts`	Comma-separated `Host` header allowlist for non-loopback binds
`--port`	HTTP port (default: `3000`)
`--path`	HTTP path (default: `/mcp`)
`--stateless`	Enable stateless mode for HTTP

HTTP API Key Modes

When using HTTP transport, the server supports two API key modes:

With --api-key: The key is used for all requests. x-api-key request headers are ignored.
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.

# Per-request key mode (multi-tenant)
npx @cryptoapis-io/mcp-address-history --transport http --port 3000
# Clients send x-api-key header with each request

Exposing the server beyond localhost

HTTP mode listens on 127.0.0.1 by default, so only processes on the same machine can reach it. To accept connections from other machines or containers, bind explicitly and protect the port:

# Startup-key mode: callers must present the token (the server refuses to start without one)
export MCP_AUTH_TOKEN=$(openssl rand -hex 32)
npx @cryptoapis-io/mcp-address-history --transport http --host 0.0.0.0 --port 3000 --api-key YOUR_API_KEY \
  --allowed-hosts mcp.internal.example
# Clients send: Authorization: Bearer $MCP_AUTH_TOKEN

# Per-request key mode: no startup key, every request must carry the caller's own x-api-key
npx @cryptoapis-io/mcp-address-history --transport http --host 0.0.0.0 --port 3000

--allowed-hosts restricts the Host header (DNS rebinding protection) when not bound to loopback. Prefer MCP_AUTH_TOKEN over --auth-token: command-line arguments are visible in the process list.

Stdio transport always requires an API key at startup.

Important: API Key Required

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.

Remote MCP Server

Crypto APIs provides an official remote MCP server with all tools available via HTTP Streamable transport at https://ai.cryptoapis.io/mcp. Pass your API key via the x-api-key header — no installation required.

License

MIT

Available Tools

4 tools

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

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.

Name	Required	Description
`limit`	No	Number of items to return (max 50)
`action`	Yes	Action to perform
`address`	Yes	Address to query
`context`	No	Optional context for the request - echoed back in response
`network`	Yes	Network name
`timestamp`	No	Unix timestamp (starting point) for list-transactions-by-timestamp action
`blockchain`	Yes	Blockchain protocol
`sortingOrder`	No	Sort order: ascending (oldest first) or descending (newest first)
`startingAfter`	No	Pagination cursor - use nextStartingAfter from previous response

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.

Name	Required	Description
`limit`	No	Number of items to return (max 50)
`action`	Yes	Action to perform: sync, list, activate, delete
`address`	No	Address (required for sync, activate, delete)
`context`	No	Optional context for the request - echoed back in response
`network`	Yes	Network name
`blockchain`	Yes	Blockchain protocol
`sortingOrder`	No	Sort order: ascending (oldest first) or descending (newest first)
`startingAfter`	No	Pagination cursor - use nextStartingAfter from previous response
`confirmationToken`	No	Confirmation token from a previous preview response. IMPORTANT: You MUST present the warning and impact to the user and receive their explicit approval before passing this token. NEVER auto-confirm — always ask the user first. The token expires after 60 seconds.

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

Name	Required	Description	Default
`action`	Yes	Reference topic to retrieve
`context`	No	Optional context for the request - echoed back in response

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.

Name	Required	Description
`limit`	No	Number of items to return (max 50)
`action`	Yes	Action to perform
`offset`	No	Pagination offset
`address`	Yes	Address to query
`context`	No	Optional context for the request - echoed back in response
`network`	Yes	Network name
`timestamp`	No	Unix timestamp (starting point) for list-transactions-by-timestamp action
`blockchain`	Yes	Blockchain protocol
`sortingOrder`	No	Sort order: ascending (oldest first) or descending (newest first)
`startingAfter`	No	Pagination cursor - use nextStartingAfter from previous response

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

4 tool updatesv0.3.0Aug 2, 2026
- First observedevm_address_history
- First observedmanage_address
- First observedsystem_info
- First observedutxo_address_history

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.5/5.0

Scored 2026-08-02 07:10 across 4 tools

Disambiguation5/5

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.

Naming Consistency4/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivitySlowing

ResponsivenessNo recent community issues

Resources

Related MCP Connectors

Fuse NetworkB
io.fuse
MCP server for Fuse Network: balances, tokens, staking, DeFi data, swaps and on-chain transactions.
Blockchain Cryptocurrency
502
https://mcp.fuse.io/mcp
BittensorMCP
io.github.btmcp
Hosted MCP server for live Bittensor chain reads and self-custodial on-chain writes.
Blockchain Cryptocurrency Web3 & Decentralized Tech
1
https://bittensormcp.com/api/mcp
mcpA
com.everstake
MCP server connecting AI agents to non-custodial staking data across 130+ networks.
Blockchain Cryptocurrency
1111
https://mcp.everstake.com
James's MCP ServerA
io.github.JGPAS
MCP server with quote and live cryptocurrency price tools, local and cloud-deployed transports.
Cryptocurrency Finance
21
https://mcp-first-server.onrender.com/mcp

Related MCP Servers

@cryptoapis-io/mcp-blockchainofficial
Blockchain Cryptocurrency Finance
CryptoAPIs-io
A
license
A
quality
C
maintenance
MCP server for Crypto APIs Blockchain Fees product, providing fee recommendations and gas estimates for UTXO, EVM, and XRP blockchains.
Updated a month ago (2026-09-28 11:47 UTC)
6
131 npm
MIT
@cryptoapis-io/mcp-prepareofficial
Cryptocurrency Blockchain Web3 & Decentralized Tech
CryptoAPIs-io
A
license
A
quality
C
maintenance
MCP server for Crypto APIs Prepare Transactions product that builds unsigned EVM transactions for native coin, fungible token (ERC-20), and NFT (ERC-721) transfers.
Updated a month ago (2026-09-28 11:48 UTC)
8
117 npm
MIT
cryptoapis-mcp-block-dataofficial
Blockchain Cryptocurrency Web3 & Decentralized Tech
CryptoAPIs-io
A
license
A
quality
C
maintenance
MCP server for Crypto APIs Block Data product. Get block details by height or hash for EVM, UTXO, and XRP blockchains.
Updated a month ago (2026-09-28 11:47 UTC)
4
115 npm
MIT
@cryptoapis-io/mcpofficial
Blockchain Cryptocurrency Web3 & Decentralized Tech
CryptoAPIs-io
A
license
A
quality
C
maintenance
MCP server for Crypto APIs Transactions Data. Enables lookup of transaction details by hash across EVM, UTXO, Solana, XRP, and Kaspa blockchains.
Updated a month ago (2026-09-28 11:48 UTC)
6
109 npm
MIT

@cryptoapis-io/mcp-address-history

Features

Prerequisites

Installation

Usage

Claude Desktop

Cursor

MCP Inspector

n8n

Available Tools

manage_address

evm_address_history

utxo_address_history

Pagination

Configuration

CLI Arguments

HTTP API Key Modes

Exposing the server beyond localhost

Important: API Key Required

Remote MCP Server

License

Available Tools

Tool Schema Changelog

TDQS

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

@cryptoapis-io/mcp-blockchainofficial

@cryptoapis-io/mcp-prepareofficial

cryptoapis-mcp-block-dataofficial

@cryptoapis-io/mcpofficial

`manage_address`

`evm_address_history`

`utxo_address_history`