Mcp Transactions Data
Look up transactions across EVM, UTXO, Solana, XRP, and Kaspa through Crypto APIs when debugging payouts or proving on-chain activity.
Overview
mcp-transactions-data is an Operate-phase MCP server that looks up transactions on EVM, UTXO, Solana, XRP, and Kaspa via Crypto APIs.
What is this MCP server?
- Transaction lookup across EVM, UTXO, Solana, XRP, and Kaspa via Crypto APIs
- npm @cryptoapis-io/mcp-transactions-data v0.3.0 with stdio MCP
- Requires CRYPTOAPIS_API_KEY for data endpoints
- Supports operate monitoring and post-ship verification from the same agent session
- Five chain families named in the published server description
- Server version 0.3.0
- Networks listed: EVM, UTXO, Solana, XRP, Kaspa (5 families)
- npm package @cryptoapis-io/mcp-transactions-data
What problem does it solve?
Jumping between explorers and APIs to resolve a single tx hash slows support and makes agent-assisted ops unreliable.
Who is it for?
Live products that need fast hash and transfer lookups across heterogeneous chains from Claude Code or Cursor.
Skip if: Greenfield projects with no on-chain activity yet, or workflows only authoring txs without reading chain state.
What do I get? / Deliverables
Your agent returns unified transaction lookups across five chain families for monitoring, analytics, and verification.
- Retrieved transaction metadata across supported networks
- Agent-ready answers for support and monitoring tickets
- Cross-chain visibility without custom explorer scrapers
Recommended MCP Servers
Journey fit
Primary shelf is operate because live transaction lookup supports incident response and production reconciliation after launch. Monitoring fits ongoing hash and address lookups agents need when users report stuck or missing transfers.
How it compares
Read-only chain data MCP server, not a transaction builder or local signer.
Common Questions / FAQ
Who is mcp-transactions-data for?
It is for builders running multi-chain apps who want agents to fetch transaction records from Crypto APIs during ops and analytics.
When should I use mcp-transactions-data?
Use it after launch when verifying broadcasts, investigating user reports, or pulling tx facts into dashboards and audits.
How do I add mcp-transactions-data to my agent?
Install @cryptoapis-io/mcp-transactions-data, configure CRYPTOAPIS_API_KEY, register the stdio MCP server, and query by hash or related identifiers via tools.