Which integrations are available for this server?

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

How do I use cryptoapis-mcp-block-data?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. 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-mcp-block-data

Official

by CryptoAPIs-io

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

@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-data

Or 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_KEY

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-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_KEY

n8n

Start the server in HTTP mode:

npx @cryptoapis-io/mcp-block-data --transport http --port 3000 --api-key YOUR_API_KEY

In 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: 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_block_data`

Get EVM block details.

Action	Description
`get-block-by-height`	Get block details by block 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

`utxo_block_data`

Get UTXO block details (Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash).

Action	Description
`get-block-by-height`	Get block details by block 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

`xrp_block_data`

Get XRP block (ledger) details.

Action	Description
`get-block-by-height`	Get ledger details by ledger index
`get-block-by-hash`	Get ledger details by ledger 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

CLI Arguments

Argument	Description	Default
`--api-key`	Crypto APIs API key	`CRYPTOAPIS_API_KEY` env var
`--transport`	Transport type: `stdio` or `http`	`stdio`
`--host`	HTTP host (use `0.0.0.0` to accept remote connections — requires an auth token with `--api-key`)	`127.0.0.1`
`--auth-token`	Bearer token callers must send (`Authorization: Bearer <token>`); prefer the `MCP_AUTH_TOKEN` env var	`MCP_AUTH_TOKEN` env var
`--allowed-hosts`	Comma-separated `Host` header allowlist for non-loopback binds	—
`--port`	HTTP port	`3000`
`--path`	HTTP path	`/mcp`
`--stateless`	Enable stateless HTTP mode	`false`

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-block-data --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-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 tools

evm_block_dataB

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.

Name	Required	Description
`count`	No	Number of blocks to return (for list-latest-mined-blocks)
`limit`	No	Number of items to return (max 50)
`action`	Yes	Action to perform
`offset`	No	Pagination offset
`context`	No	Optional context for the request - echoed back in response
`network`	Yes	Network name
`blockHash`	No	Block hash (required for get-block-by-hash, list-transactions-by-block-hash)
`blockchain`	Yes	Blockchain protocol
`blockHeight`	No	Block height (required for get-block-by-height, list-transactions-by-block-height)

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

Name	Required	Description	Default
`action`	Yes	Reference topic to retrieve
`context`	No	Optional context for the request - echoed back in response

utxo_block_dataC

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.

Name	Required	Description
`count`	No	Number of blocks to return (for list-latest-mined-blocks)
`limit`	No	Number of items to return (max 50)
`action`	Yes	Action to perform
`offset`	No	Pagination offset
`context`	No	Optional context for the request - echoed back in response
`network`	Yes	Network name
`blockHash`	No	Block hash (required for get-block-by-hash, list-transactions-by-block-hash)
`blockchain`	Yes	Blockchain protocol
`blockHeight`	No	Block height (required for get-block-by-height, list-transactions-by-block-height)

xrp_block_dataA

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

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.

Name	Required	Description
`count`	No	Number of blocks to return (for list-latest-mined-blocks)
`limit`	No	Number of items to return (max 50)
`action`	Yes	Action to perform
`offset`	No	Pagination offset
`context`	No	Optional context for the request - echoed back in response
`network`	Yes	Network name: mainnet or testnet
`blockHash`	No	Block hash (required for get-block-by-hash, list-transactions-by-block-hash)
`blockHeight`	No	Block height (required for get-block-by-height, list-transactions-by-block-height)

Tool Schema Changelog

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

4 tool updatesv0.4.0Sep 25, 2026
- First observedevm_block_data
- First observedsystem_info
- First observedutxo_block_data
- First observedxrp_block_data

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.7/5.0

Scored 2026-09-25 04:35 across 4 tools

Disambiguation5/5

Each tool is clearly scoped to a distinct blockchain family (EVM, UTXO, XRP) or system reference, with no overlap in purpose. The actions within each block data tool are identical but apply to different networks, making selection dependent on the target blockchain—a clear and unambiguous decision.

Naming Consistency5/5

All block data tools follow the same naming pattern: {family}_block_data (e.g., evm_block_data, utxo_block_data, xrp_block_data), and the actions inside each are uniformly named (get-block-by-height, list-transactions-by-hash, etc.). system_info breaks the pattern but is logically distinct and still uses a simple noun convention.

Tool Count4/5

With only 4 tools, the count is on the lower end, but each block data tool encapsulates 6 actions across many blockchains, providing substantial functionality. This is a focused server for block data retrieval, so the tool count is reasonable, though the surface could be expanded with more specific tools if needed.

Completeness4/5

The tools cover the core block lifecycle: fetching blocks by height/hash and listing transactions in blocks, plus latest block retrieval. A notable missing operation is a direct transaction lookup by hash/txid, which would be a natural addition. Overall, the surface is solid for block data but has a minor gap in transaction-level access.

Maintenance

ActivitySlowing

ResponsivenessNo recent community issues

Resources

Related MCP Connectors

mcp-serverA
com.blockscout
MCP server for Blockscout
Blockchain Web3 & Decentralized Tech Search
16246
https://mcp.blockscout.com/mcp
Fuse NetworkB
io.fuse
MCP server for Fuse Network: balances, tokens, staking, DeFi data, swaps and on-chain transactions.
Blockchain Cryptocurrency
502
https://mcp.fuse.io/mcp
mcpA
com.everstake
MCP server connecting AI agents to non-custodial staking data across 130+ networks.
Blockchain Cryptocurrency
1111
https://mcp.everstake.com
Crypto Prices Mcp
io.github.varvararatta
Unlock the power of real-time cryptocurrency data with our Crypto Price Insights MCP server.
Cryptocurrency Finance
2
https://crypto-prices-mcp.mcpize.run/mcp

Related MCP Servers

@cryptoapis-io/mcp-blockchainofficial
Blockchain Cryptocurrency Finance
CryptoAPIs-io
A
license
A
quality
C
maintenance
MCP server for Crypto APIs Blockchain Fees product, providing fee recommendations and gas estimates for UTXO, EVM, and XRP blockchains.
Updated a month ago (2026-09-28 11:47 UTC)
6
131 npm
MIT
@cryptoapis-io/mcp-prepareofficial
Cryptocurrency Blockchain Web3 & Decentralized Tech
CryptoAPIs-io
A
license
A
quality
C
maintenance
MCP server for Crypto APIs Prepare Transactions product that builds unsigned EVM transactions for native coin, fungible token (ERC-20), and NFT (ERC-721) transfers.
Updated a month ago (2026-09-28 11:48 UTC)
8
117 npm
MIT
@cryptoapis-io/mcp-addressofficial
Blockchain Cryptocurrency
CryptoAPIs-io
A
license
A
quality
B
maintenance
MCP server for Crypto APIs Address History product, enabling querying full blockchain address transaction history for synced addresses across EVM and UTXO blockchains.
Updated a month ago (2026-09-28 11:47 UTC)
4
115 npm
MIT
@cryptoapis-io/mcpofficial
Blockchain Cryptocurrency Web3 & Decentralized Tech
CryptoAPIs-io
A
license
A
quality
C
maintenance
MCP server for Crypto APIs Transactions Data. Enables lookup of transaction details by hash across EVM, UTXO, Solana, XRP, and Kaspa blockchains.
Updated a month ago (2026-09-28 11:48 UTC)
6
109 npm
MIT

@cryptoapis-io/mcp-block-data

Features

Prerequisites

Installation

Usage

Claude Desktop

Cursor

MCP Inspector

n8n

Available Tools

evm_block_data

utxo_block_data

xrp_block_data

CLI Arguments

HTTP API Key Modes

Exposing the server beyond localhost

Important: API Key Required

Remote MCP Server

License

Available Tools

Tool Schema Changelog

TDQS

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

@cryptoapis-io/mcp-blockchainofficial

@cryptoapis-io/mcp-prepareofficial

@cryptoapis-io/mcp-addressofficial

@cryptoapis-io/mcpofficial

`evm_block_data`

`utxo_block_data`

`xrp_block_data`