Skip to main content
Glama
cryptoapis-address-latest

cryptoapis-address-latest

Official

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MCP_AUTH_TOKENNoBearer token callers must send when exposing the server beyond localhost (HTTP transport with --host 0.0.0.0). Optional.
CRYPTOAPIS_API_KEYYesYour Crypto APIs API key. Required to run the server.

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

CapabilityDetails
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": true
}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
evm_address_latestA

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.

utxo_address_latestA

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.

solana_address_latestA

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.

xrp_address_latestA

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.

kaspa_address_latestA

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.

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

NameDescription
check-balancesCheck address balances across one or more blockchains

Resources

Contextual data attached and managed by the client

NameDescription
supported-chainsSupported blockchains, networks, and actions for address-latest queries

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