cryptoapis-mcp-block-data
OfficialProvides block data capabilities for the Bitcoin blockchain, including retrieving block details by height or hash, listing transactions in a block, and getting the latest mined blocks.
Provides block data capabilities for the Bitcoin Cash blockchain, including retrieving block details by height or hash, listing transactions in a block, and getting the latest mined blocks.
Provides block data capabilities for the Dash blockchain, including retrieving block details by height or hash, listing transactions in a block, and getting the latest mined blocks.
Provides block data capabilities for the Dogecoin blockchain, including retrieving block details by height or hash, listing transactions in a block, and getting the latest mined blocks.
Provides block data capabilities for the Ethereum blockchain, including retrieving block details by height or hash, listing transactions in a block, and getting the latest mined blocks.
Provides block data capabilities for the Litecoin blockchain, including retrieving block details by height or hash, listing transactions in a block, and getting the latest mined blocks.
Provides block data capabilities for the Optimism blockchain, including retrieving block details by height or hash, listing transactions in a block, and getting the latest mined blocks.
Provides block data capabilities for the Polygon blockchain, including retrieving block details by height or hash, listing transactions in a block, and getting the latest mined blocks.
Provides block data capabilities for the XRP Ledger, including retrieving ledger details by index or hash, listing transactions in a ledger, and getting the latest closed ledger.
Provides block data capabilities for the Zcash blockchain, including retrieving block details by height or hash, listing transactions in a block, and getting the latest mined blocks.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@cryptoapis-mcp-block-data get the latest mined Ethereum block"
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-block-data
MCP server for Crypto APIs Block Data product. Get block details by height or hash for EVM, UTXO, and XRP blockchains.
API Version: Compatible with Crypto APIs version 2024-12-12
Features
Get block details by block height or block hash
List transactions by block height or block hash
Get last mined block and list latest mined blocks
Supported EVM chains: Ethereum, Ethereum Classic, BSC, Polygon, Avalanche (C-Chain), Arbitrum, Base, Optimism, Tron
Supported UTXO chains: Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash
Supported other: XRP (mainnet, testnet)
Related MCP server: @cryptoapis-io/mcp-prepare-transactions
Prerequisites
Node.js 18+
Crypto APIs account and API key (sign up | get API key)
Installation
npm install @cryptoapis-io/mcp-block-dataOr install all Crypto APIs MCP servers: npm install @cryptoapis-io/mcp
Usage
# Run with API key
npx @cryptoapis-io/mcp-block-data --api-key YOUR_API_KEY
# Or use environment variable
export CRYPTOAPIS_API_KEY=YOUR_API_KEY
npx @cryptoapis-io/mcp-block-data
# HTTP transport (listens on 127.0.0.1; see "Exposing the server beyond localhost")
npx @cryptoapis-io/mcp-block-data --transport http --port 3000 --api-key YOUR_API_KEYClaude 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-block-data": {
"command": "npx",
"args": ["-y", "@cryptoapis-io/mcp-block-data"],
"env": {
"CRYPTOAPIS_API_KEY": "your_api_key_here"
}
}
}
}Cursor
Add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):
{
"mcpServers": {
"cryptoapis-block-data": {
"command": "npx",
"args": ["-y", "@cryptoapis-io/mcp-block-data"],
"env": {
"CRYPTOAPIS_API_KEY": "your_api_key_here"
}
}
}
}MCP Inspector
npx @modelcontextprotocol/inspector npx @cryptoapis-io/mcp-block-data --api-key YOUR_API_KEYn8n
Start the server in HTTP mode:
npx @cryptoapis-io/mcp-block-data --transport http --port 3000 --api-key YOUR_API_KEYIn 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:
localhostinside the container is not your machine. Start the server with--host 0.0.0.0andMCP_AUTH_TOKENset (see Exposing the server beyond localhost), usehttp://host.docker.internal:3000/mcpas the URL, and add anAuthorization: Bearer <token>header to the MCP Client Tool credential.
All servers default to port 3000. Use
--portto assign different ports when running multiple servers.
Available Tools
evm_block_data
Get EVM block details.
Action | Description |
| Get block details by block number |
| Get block details by block hash |
| List transactions in a block by block height |
| List transactions in a block by block hash |
| Get the latest mined block details |
| List the latest mined blocks |
utxo_block_data
Get UTXO block details (Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash).
Action | Description |
| Get block details by block number |
| Get block details by block hash |
| List transactions in a block by block height |
| List transactions in a block by block hash |
| Get the latest mined block details |
| List the latest mined blocks |
xrp_block_data
Get XRP block (ledger) details.
Action | Description |
| Get ledger details by ledger index |
| Get ledger details by ledger hash |
| List transactions in a block by block height |
| List transactions in a block by block hash |
| Get the latest mined block details |
| List the latest mined blocks |
CLI Arguments
Argument | Description | Default |
| Crypto APIs API key |
|
| Transport type: |
|
| HTTP host (use |
|
| Bearer token callers must send ( |
|
| Comma-separated | — |
| HTTP port |
|
| HTTP path |
|
| Enable stateless HTTP mode |
|
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-keyrequest headers are ignored.Without
--api-key: Each request must include anx-api-keyheader 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-block-data --transport http --port 3000
# Clients send x-api-key header with each requestExposing 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-block-data --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-block-data --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 toolsevm_block_dataEVM block dataARead-onlyIdempotent
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.
Inputs: action (required), network (required), blockchain (required), count, +5 more.
system_infoCryptoAPIs reference infoARead-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_block_dataUTXO block dataBRead-onlyIdempotent
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.
Inputs: action (required), network (required), blockchain (required), count, +5 more.
xrp_block_dataXRP block dataARead-onlyIdempotent
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.
Inputs: action (required), network (required), count, limit, +4 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
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.
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.
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.
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
Related MCP Connectors
Bitcoin on-chain analytics API & MCP server, new data every block: MVRV, SOPR, exchange/whale flows
MCP server for Fuse Network: balances, tokens, staking, DeFi data, swaps and on-chain transactions.
MCP server connecting AI agents to non-custodial staking data across 130+ networks.
Related MCP Servers
- AlicenseAqualityBmaintenanceMCP server for Crypto APIs Blockchain Fees product, providing fee recommendations and gas estimates for UTXO, EVM, and XRP blockchains.689 npmMIT
- AlicenseAqualityBmaintenanceMCP server for Crypto APIs Prepare Transactions product that builds unsigned EVM transactions for native coin, fungible token (ERC-20), and NFT (ERC-721) transfers.8305 npmMIT
- AlicenseAqualityBmaintenanceMCP server for Crypto APIs Address History product, enabling querying full blockchain address transaction history for synced addresses across EVM and UTXO blockchains.4337 npmMIT

@cryptoapis-io/mcpofficial
AlicenseAqualityBmaintenanceMCP server for Crypto APIs Transactions Data. Enables lookup of transaction details by hash across EVM, UTXO, Solana, XRP, and Kaspa blockchains.6307 npmMIT