@cryptoapis-io/mcp-transactions-data
OfficialProvides tools to get Bitcoin transaction details and raw transaction data by hash.
Provides tools to get Bitcoin Cash transaction details and raw transaction data by hash.
Provides tools to get Dash transaction details and raw transaction data by hash.
Provides tools to get Dogecoin transaction details and raw transaction data by hash.
Provides tools to get Ethereum transaction details, internal transactions, token transfers, and logs by hash.
Provides tools to get Litecoin transaction details and raw transaction data by hash.
Provides tools to get Optimism transaction details, internal transactions, token transfers, and logs by hash.
Provides tools to get Polygon transaction details, internal transactions, token transfers, and logs by hash.
Provides tools to get Solana transaction details by signature.
Provides tools to get XRP transaction details by hash.
Provides tools to get Zcash transaction details and raw transaction data by hash.
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-io/mcp-transactions-data get transaction details for 0x4e5f6a on Ethereum mainnet"
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-transactions-data
MCP server for Crypto APIs Transactions Data product. Look up transaction details by hash across EVM, UTXO, Solana, XRP, and Kaspa blockchains.
API Version: Compatible with Crypto APIs version 2024-12-12
Features
UTXO: Get transaction details and raw transaction data (Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash)
EVM: Get transaction details, internal transactions, token transfers, and logs (Ethereum, Ethereum Classic, BSC, Polygon, Avalanche (C-Chain), Arbitrum, Base, Optimism, Tron)
Solana: Get transaction details by signature
XRP: Get transaction details
Kaspa: Get transaction details by transaction ID
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-transactions-dataOr install all Crypto APIs MCP servers: npm install @cryptoapis-io/mcp
Usage
# Run with API key
npx @cryptoapis-io/mcp-transactions-data --api-key YOUR_API_KEY
# Or use environment variable
export CRYPTOAPIS_API_KEY=YOUR_API_KEY
npx @cryptoapis-io/mcp-transactions-data
# HTTP transport (listens on 127.0.0.1; see "Exposing the server beyond localhost")
npx @cryptoapis-io/mcp-transactions-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-transactions-data": {
"command": "npx",
"args": ["-y", "@cryptoapis-io/mcp-transactions-data"],
"env": {
"CRYPTOAPIS_API_KEY": "your_api_key_here"
}
}
}
}Cursor
Add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):
{
"mcpServers": {
"cryptoapis-transactions-data": {
"command": "npx",
"args": ["-y", "@cryptoapis-io/mcp-transactions-data"],
"env": {
"CRYPTOAPIS_API_KEY": "your_api_key_here"
}
}
}
}MCP Inspector
npx @modelcontextprotocol/inspector npx @cryptoapis-io/mcp-transactions-data --api-key YOUR_API_KEYn8n
Start the server in HTTP mode:
npx @cryptoapis-io/mcp-transactions-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
transactions_data_utxo
UTXO transaction details (Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash).
Action | Description |
| Get transaction details by hash |
| Get raw transaction data by hash |
transactions_data_evm
EVM transaction details (Ethereum, Ethereum Classic, BSC, Polygon, Avalanche (C-Chain), Arbitrum, Base, Optimism, Tron).
Action | Description |
| Get transaction details by hash |
| List internal transactions by hash |
| List token transfers by hash |
| List event logs by hash |
transactions_data_solana
Solana transaction details (mainnet, devnet).
Parameter | Description |
| Network (mainnet, devnet) |
| Transaction signature |
transactions_data_xrp
XRP transaction details (mainnet, testnet).
Parameter | Description |
| Network (mainnet, testnet) |
| Transaction hash |
transactions_data_kaspa
Kaspa transaction details (mainnet).
Parameter | Description |
| Network (mainnet) |
| Transaction ID |
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-transactions-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-transactions-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-transactions-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
6 toolssystem_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.
transactions_data_evmEVM transaction detailsARead-onlyIdempotent
Transactions Data EVM: get transaction details, internal transactions, token transfers, or logs by transaction hash.
Actions: get-transaction-details, list-internal-transactions, list-token-transfers, list-logs.
Credits by action (source: OpenAPI): • get-transaction-details: arbitrum 192, avalanche 216, base 144, binance-smart-chain 300, ethereum 120, ethereum-classic 156, optimism 168, polygon 240, tron 180 • 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-logs: arbitrum 192, avalanche 216, base 144, binance-smart-chain 300, ethereum 120, ethereum-classic 156, optimism 168, polygon 240, tron 180 • list-token-transfers: arbitrum 352, avalanche 396, base 264, binance-smart-chain 550, ethereum 220, ethereum-classic 286, optimism 308, polygon 440, tron 330
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), transactionHash (required), +1 more.
transactions_data_kaspaKaspa transaction detailsARead-onlyIdempotent
Transactions Data Kaspa: get transaction details by transaction ID. Network: mainnet.
Credits per call: 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: network (required), transactionId (required), context.
transactions_data_solanaSolana transaction detailsBRead-onlyIdempotent
Transactions Data Solana: get transaction details by transaction hash (signature). Networks: mainnet, devnet.
Credits per call: 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: network (required), transactionHash (required), context.
transactions_data_utxoUTXO transaction detailsBRead-onlyIdempotent
Transactions Data UTXO: get transaction details or raw transaction data by hash.
Actions: get-transaction-details, get-raw-transaction-data. Blockchains: bitcoin, bitcoin-cash, litecoin, dogecoin, dash, zcash. Networks: mainnet, testnet.
Credits by action (source: OpenAPI): • get-raw-transaction-data: bitcoin 110, bitcoin-cash 132, dash 121, dogecoin 121, litecoin 121, zcash 143 • get-transaction-details: 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), network (required), blockchain (required), transactionHash (required), +1 more.
transactions_data_xrpXRP transaction detailsBRead-onlyIdempotent
Transactions Data XRP: get transaction details by transaction hash. Networks: mainnet, testnet.
Credits per call: 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: network (required), transactionHash (required), context.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Each chain-family tool has a clearly distinct target (Solana, UTXO, EVM, XRP, Kaspa), so an agent can select by blockchain type with no overlap. The multi-action EVM and UTXO tools still have boundaries defined by their chain family, and system_info is unmistakably separate reference material.
The five data tools follow a clean transactions_data_<chain> pattern, making the set predictable. Only system_info deviates, but it is a different category of tool, so the deviation is minor and readable.
Six tools is well-scoped for a transaction-data server: one per supported chain family plus a reference tool. No tool feels redundant or missing at the structural level.
The surface covers transaction details across several chain families, with UTXO raw-data and EVM internal transactions, token transfers, and logs adding useful depth. Minor gaps remain, such as no address-based transaction listing and selective chain coverage, but core retrieval workflows are covered.
Maintenance
Related MCP Connectors
MCP server for Fuse Network: balances, tokens, staking, DeFi data, swaps and on-chain transactions.
Tenzro Network MCP server: wallet, identity, payments, inference, staking, bridges, verification.
MCP server for Modern Treasury — payment orders, transactions, counterparties and ledgers.
Related MCP Servers
- AlicenseAqualityBmaintenanceMCP server for Crypto APIs Blockchain Fees product, providing fee recommendations and gas estimates for UTXO, EVM, and XRP blockchains.6327 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.8119 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
- AlicenseAqualityBmaintenanceMCP server for Crypto APIs Block Data product. Get block details by height or hash for EVM, UTXO, and XRP blockchains.4328 npmMIT