Skip to main content
Glama
cryptoapis-address-latest

cryptoapis-address-latest

Official

@cryptoapis-io/mcp-address-latest

MCP server for Crypto APIs Address Latest product. Query recent blockchain address data (last 14 days) without requiring address sync.

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

Features

  • Query EVM addresses (Ethereum, Ethereum Classic, BSC, Polygon, Avalanche (C-Chain), Arbitrum, Base, Optimism, Tron)

  • Query UTXO addresses (Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash)

  • Query Solana addresses (SOL balance, transactions, SPL tokens)

  • Query XRP/Ripple addresses (balance, transactions, sequence)

  • Query Kaspa addresses (balance, transactions)

  • Cursor-based pagination for large result sets

  • No address sync required (unlike Address History)

Related MCP server: onchain-forensics

Prerequisites

To use this MCP server, you need:

  1. Register at Crypto APIs

  2. Generate an API key from your dashboard

Installation

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

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

Usage

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

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

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-latest": {
      "command": "npx",
      "args": ["-y", "@cryptoapis-io/mcp-address-latest"],
      "env": {
        "CRYPTOAPIS_API_KEY": "your_api_key_here"
      }
    }
  }
}

Cursor

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

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

MCP Inspector

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

n8n

  1. Start the server in HTTP mode:

    npx @cryptoapis-io/mcp-address-latest --transport http --port 3000 --api-key YOUR_API_KEY
  2. In your n8n workflow, add an AI Agent node

  3. 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

evm_address_latest

Query latest EVM address data.

Actions:

Action

Description

get-balance

Get address balance

get-next-nonce

Get next available nonce. Supported: Ethereum (mainnet, sepolia), Ethereum Classic (mainnet, mordor), BSC (mainnet, testnet)

list-transactions

List address transactions

list-token-transfers

List token transfers (ERC-20, ERC-721, ERC-1155)

list-internal-transactions

List internal transactions

Supported Blockchains: ethereum, ethereum-classic, binance-smart-chain, polygon, avalanche (C-Chain), arbitrum, base, optimism, tron

utxo_address_latest

Query latest UTXO address data.

Actions:

Action

Description

get-balance

Get address balance

list-transactions

List address transactions

list-unconfirmed-transactions

List unconfirmed transactions (mempool); uses offset pagination

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

solana_address_latest

Query latest Solana address data.

Actions:

Action

Description

get-balance

Get address SOL balance

list-transactions

List address transactions

list-tokens

List SPL tokens held by address

Supported Networks: mainnet, devnet

xrp_address_latest

Query latest XRP (Ripple) address data.

Actions:

Action

Description

get-balance

Get address XRP balance

list-transactions

List address transactions

get-next-sequence

Get next available sequence number

Supported Networks: mainnet, testnet

kaspa_address_latest

Query latest Kaspa address data.

Actions:

Action

Description

get-balance

Get address KAS balance

list-transactions

List address transactions

Supported Networks: mainnet

Pagination

Most list 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-unconfirmed-transactions (UTXO) uses offset pagination with limit, offset, and total fields.

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

  1. Command-line argument (recommended):

    npx @cryptoapis-io/mcp-address-latest --api-key {your_api_key}
  2. 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-latest --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-latest --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-latest --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

6 tools
evm_address_latestEVM address balance and latest activityA
Read-onlyIdempotent

Query latest EVM address data (last 14 days). Cursor pagination: use 'nextStartingAfter' from response as 'startingAfter'.

Actions & supported blockchains: • get-balance: ethereum, ethereum-classic, binance-smart-chain, tron, polygon, avalanche (C-Chain), arbitrum, base, optimism • get-next-nonce: ethereum, ethereum-classic, binance-smart-chain (mainnet, mordor, testnet, sepolia) • list-transactions: ethereum, ethereum-classic, binance-smart-chain, arbitrum, polygon, avalanche (C-Chain), base, optimism, tron • list-token-transfers: ethereum, ethereum-classic, binance-smart-chain, tron, polygon, avalanche (C-Chain), arbitrum, base, optimism • list-internal-transactions: ethereum, ethereum-classic, binance-smart-chain, polygon, avalanche (C-Chain), arbitrum, base, optimism, tron

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-balance: arbitrum 48, avalanche 54, base 36, binance-smart-chain 75, ethereum 30, ethereum-classic 39, optimism 42, polygon 60, tron 45 • get-next-nonce: arbitrum 32, avalanche 36, base 24, binance-smart-chain 50, ethereum 20, ethereum-classic 26, optimism 28, polygon 40, tron 30 • list-internal-transactions: arbitrum 512, avalanche 576, base 384, binance-smart-chain 800, ethereum 320, ethereum-classic 416, optimism 448, polygon 640, tron 480 • list-token-transfers: arbitrum 352, avalanche 396, base 264, binance-smart-chain 550, ethereum 220, ethereum-classic 286, optimism 308, polygon 440, tron 330 • list-transactions: arbitrum 192, avalanche 216, base 144, binance-smart-chain 300, ethereum 120, ethereum-classic 156, optimism 168, polygon 240, tron 180

Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers.

Inputs: action (required), address (required), network (required), blockchain (required), +4 more.

kaspa_address_latestKaspa address balance and latest activityA
Read-onlyIdempotent

Query latest Kaspa address data. Cursor pagination: use 'nextStartingAfter' from response as 'startingAfter'.

Actions: • get-balance: Get address KAS balance • list-transactions: Get address transactions

Networks: mainnet (only)

Credits by action (source: OpenAPI): • get-balance: kaspa 918 • list-transactions: kaspa 918

Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers.

Inputs: action (required), address (required), network (required), limit, +3 more.

solana_address_latestSolana address balance and latest activityA
Read-onlyIdempotent

Query latest Solana address data (last 14 days). Cursor pagination: use 'nextStartingAfter' from response as 'startingAfter'.

Actions: • get-balance: Get address SOL balance • list-transactions: Get address transactions • list-tokens: Get SPL tokens held by address

Networks: mainnet, devnet

Credits by action (source: OpenAPI): • get-balance: solana 75 • list-tokens: solana 120 • list-transactions: solana 90

Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers.

Inputs: action (required), address (required), network (required), limit, +3 more.

system_infoCryptoAPIs reference infoA
Read-onlyIdempotent

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

Inputs: action (required), context.

utxo_address_latestUTXO address balance and latest activityA
Read-onlyIdempotent

Query latest UTXO address data (last 14 days). • get-balance: no pagination • list-transactions: cursor pagination - use 'nextStartingAfter' from response as 'startingAfter' • list-unconfirmed-transactions: offset pagination - use 'limit' and 'offset' (lists unconfirmed/mempool transactions)

Actions & supported blockchains: • get-balance: bitcoin, bitcoin-cash, litecoin, dash, dogecoin, zcash • list-transactions: bitcoin, bitcoin-cash, dash, dogecoin, litecoin, zcash • list-unconfirmed-transactions: bitcoin, bitcoin-cash, litecoin, dogecoin, dash, zcash

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-balance: bitcoin 510, bitcoin-cash 612, dash 561, dogecoin 561, litecoin 561, zcash 663 • list-transactions: bitcoin 110, bitcoin-cash 132, dash 121, dogecoin 121, litecoin 121, zcash 143 • list-unconfirmed-transactions: bitcoin 110, bitcoin-cash 132, dash 121, dogecoin 121, litecoin 121, zcash 143

Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers.

Inputs: action (required), address (required), network (required), blockchain (required), +5 more.

xrp_address_latestXRP address balance and latest activityA
Read-onlyIdempotent

Query latest XRP (Ripple) address data. Cursor pagination: use 'nextStartingAfter' from response as 'startingAfter'.

Actions: • get-balance: Get address XRP balance • list-transactions: Get address transactions • get-next-sequence: Get next available sequence number for transactions

Networks: mainnet, testnet

Credits by action (source: OpenAPI): • get-balance: xrp 20 • get-next-sequence: xrp 20 • list-transactions: xrp 110

Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers.

Inputs: action (required), address (required), network (required), limit, +3 more.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool is scoped to a distinct blockchain family (EVM, UTXO, Solana, XRP, Kaspa) plus a documentation tool, so the top-level boundaries are clear. The only mild ambiguity is that get-balance/list-transactions appear as sub-actions in five tools, so the agent must know which family a chain belongs to (e.g. tron living under the EVM tool is non-obvious).

    Naming Consistency4/5

    Five tools follow a clean, predictable <chain>_address_latest pattern, making the family scope immediately readable. system_info is the single deviation, but it is a clearly different kind of tool so the break is understandable.

    Tool Count5/5

    Six tools is well-scoped for an address-data API, with each chain family bundling its own actions rather than exploding into dozens of per-action tools. No tool feels redundant or filler.

    Completeness4/5

    Core address workflows are covered: balance, transactions, token transfers, nonce/sequence, and unconfirmed mempool transactions. Minor gaps exist — no UTXO/unspent-output listing, no token holdings for Solana/XRP chains beyond list-tokens, and Kaspa supports only balance plus transactions.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides tools for querying onchain data across 12+ blockchain networks, including token balances, transaction analysis, and smart contract security auditing. It enables users to interact with multiple EVM-compatible chains and perform deep contract evaluations through natural language interfaces.
      1
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables blockchain forensics across multiple chains (Base, Ethereum, Arbitrum, Optimism, Polygon) with tools to trace transactions, cluster addresses, detect anomalies, and identify mixer usage.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying on-chain data (balances, transactions, token transfers, blocks) across 20+ EVM chains through natural language.
      61 npm
      MIT