Skip to main content
Glama
cryptoapis-mcp-block-data

cryptoapis-mcp-block-data

Official

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MCP_AUTH_TOKENNoBearer token for HTTP transport when bound to non-loopback. Prefer this over the --auth-token CLI argument.
CRYPTOAPIS_API_KEYYesYour Crypto APIs API key. Required for stdio transport and for HTTP transport in startup-key mode. Can also be supplied via the --api-key CLI argument.

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_block_dataA

Get EVM block details (Block Data product).

Actions: • get-block-by-height: Get block details by block height (number) • get-block-by-hash: Get block details by block hash • list-transactions-by-block-hash: List transactions in a block by block hash • list-transactions-by-block-height: List transactions in a block by block height • get-last-mined-block: Get the latest mined block details • list-latest-mined-blocks: List the latest mined blocks

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-block-by-hash: arbitrum 48, avalanche 54, base 36, binance-smart-chain 75, ethereum 30, ethereum-classic 39, optimism 42, polygon 60, tron 45 • get-block-by-height: arbitrum 48, avalanche 54, base 36, binance-smart-chain 75, ethereum 30, ethereum-classic 39, optimism 42, polygon 60, tron 45 • get-last-mined-block: arbitrum 48, avalanche 54, base 36, binance-smart-chain 75, ethereum 30, ethereum-classic 39, optimism 42, polygon 60, tron 45 • list-latest-mined-blocks: arbitrum 48, avalanche 54, base 36, binance-smart-chain 75, ethereum 30, ethereum-classic 39, optimism 42, polygon 60, tron 45 • list-transactions-by-block-hash: arbitrum 48, avalanche 54, base 36, binance-smart-chain 75, ethereum 30, ethereum-classic 39, optimism 42, polygon 60, tron 45 • list-transactions-by-block-height: arbitrum 48, avalanche 54, base 36, binance-smart-chain 75, ethereum 30, ethereum-classic 39, optimism 42, polygon 60, tron 45

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_block_dataB

Get UTXO block details (Block Data product).

Actions: • get-block-by-height: Get block details by block height (number) • get-block-by-hash: Get block details by block hash • list-transactions-by-block-height: List transactions in a block by block height • list-transactions-by-block-hash: List transactions in a block by block hash • get-last-mined-block: Get the latest mined block details • list-latest-mined-blocks: List the latest mined blocks

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-block-by-hash: bitcoin 20, bitcoin-cash 24, dash 22, dogecoin 22, litecoin 22, zcash 26 • get-block-by-height: bitcoin 20, bitcoin-cash 24, dash 22, dogecoin 22, litecoin 22, zcash 26 • get-last-mined-block: bitcoin 20, bitcoin-cash 24, dash 22, dogecoin 22, litecoin 22, zcash 26 • list-latest-mined-blocks: bitcoin 20, bitcoin-cash 24, dash 22, dogecoin 22, litecoin 22, zcash 26 • list-transactions-by-block-hash: bitcoin 20, bitcoin-cash 24, dash 22, dogecoin 22, litecoin 22, zcash 26 • list-transactions-by-block-height: bitcoin 20, bitcoin-cash 24, dash 22, dogecoin 22, litecoin 22, zcash 26

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_block_dataA

Get XRP block details (Block Data product). Path uses network only (no blockchain). Networks: mainnet, testnet.

Actions: • get-block-by-height: Get block details by block height (number) • get-block-by-hash: Get block details by block hash • list-transactions-by-block-height: List transactions in a block by block height • list-transactions-by-block-hash: List transactions in a block by block hash • get-last-mined-block: Get the latest mined block details • list-latest-mined-blocks: List the latest mined blocks

Credits by action (source: OpenAPI): • get-block-by-hash: 20 • get-block-by-height: 20 • get-last-mined-block: 20 • list-latest-mined-blocks: 20 • list-transactions-by-block-hash: 20 • list-transactions-by-block-height: 20

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
inspect-blockLook up a block by height or hash and summarize its contents

Resources

Contextual data attached and managed by the client

NameDescription
supported-chainsLists every blockchain, network, and action supported by the block-data tools

TDQS

A3.9/5.0

Scored across 4 tools

Disambiguation4/5

The three block-data tools are separated by blockchain family (EVM, UTXO, XRP), which gives clear selection rules when the chain is known. However, they expose identical action names, so an agent must first classify the target chain and could confuse EVM vs. UTXO if the chain is unspecified. system_info is clearly distinct as a reference tool.

Naming Consistency4/5

The three main tools follow a predictable snake_case pattern of [chain_family]_block_data. system_info deviates from that pattern but is a clearly separate reference utility, making the inconsistency minor and understandable.

Tool Count5/5

Four tools is well-scoped for a block-data server: three chain-family wrappers plus one reference tool. Each tool earns its place by consolidating multiple related actions, avoiding an overly fragmented surface.

Completeness5/5

The surface covers the full block-data lifecycle for all supported chain families: block by height/hash, transaction listing by block height/hash, and latest-mined-block retrieval. system_info fills the supporting reference/documentation role, leaving no obvious gaps for the stated purpose.

Maintenance

ActivityMaintained
ResponsivenessOutdated data