Mcp-address-history MCP Server

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

Local serverstdioMIT

What is the Mcp-address-history MCP Server?

Cryptoapis Address History is an MCP project maintained in the cryptoapis-io/cryptoapis-mcp-address-history repository. The maintainer describes its purpose as “MCP server for Crypto APIs Address History product. Query full blockchain address transaction history for synced addresses”. Read the project documentation for the complete scope.

Installation

The documented npm package is @cryptoapis-io/mcp-address-history. The configuration below comes from the maintainer’s example; adapt its paths and account values to your environment.

Configuration values

The example declares CRYPTOAPIS_API_KEY. Secret-looking values have been replaced with placeholders. Required and optional labels are shown only when the documentation states them.

Source

Project documentation · Repository · Discovery listing. This profile records the public documentation checked on 2026-10-08.

Recorded tools

Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.

ToolWhat it does
ActionDescription
syncSync a new address for historical data
activateActivate a previously synced address
deleteDelete a synced address
listList all synced addresses
get-statisticsGet address statistics
list-transactionsList all transactions
list-transactions-by-timestampList transactions from timestamp
list-token-transfersList token transfers
list-internal-transactionsList internal transactions
list-tokensList tokens held by address
list-unspent-outputsList unspent outputs (UTXOs)
manage_address
evm_address_history
utxo_address_history

How to install the Mcp-address-history MCP Server

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

From the project documentation. Replace placeholders and example paths before connecting.

Configuration

VariableDescriptionRequired
CRYPTOAPIS_API_KEYDeclared in the maintainer’s client configuration.Check documentation