A
licenseA
qualityB
maintenanceMCP server for Crypto APIs Block Data product. Get block details by height or hash for EVM, UTXO, and XRP blockchains.
4
347 npm
MIT
@cryptoapis-io/mcp-transactions-data
OfficialRelated Servers
Alternatives to @cryptoapis-io/mcp-transactions-data
No user-submitted related servers found.
Related Servers
- 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.895 npmMIT
- AlicenseAqualityBmaintenanceMCP server for Crypto APIs Utils, enabling address validation, raw transaction decoding, and XRP X-Address encoding/decoding for UTXO, EVM, and XRP blockchains.5167 npmMIT
- AlicenseAqualityBmaintenanceMCP server for Crypto APIs Address History product, enabling querying full blockchain address transaction history for synced addresses across EVM and UTXO blockchains.483 npmMIT
- AlicenseAqualityBmaintenanceMCP server for Crypto APIs AML, enabling verification of blockchain addresses and screening of transactions for fraud, sanctions, and other AML risk categories.257 npmMIT
- AlicenseAqualityAmaintenanceMCP server for Crypto APIs Blockchain Fees product, providing fee recommendations and gas estimates for UTXO, EVM, and XRP blockchains.6224 npmMIT
TDQS
A3.5/5.0
Scored across 6 tools
Disambiguation4/5
Tools are partitioned cleanly by blockchain family (UTXO, EVM, Solana, XRP, Kaspa), and the EVM tool's multi-action nature is distinct from the simpler single-action chain tools. Minor residual overlap since Solana/XRP/Kaspa tools all do essentially 'get transaction details by hash', but the chain scoping keeps selections unambiguous.
Naming Consistency4/5
All five data tools share a strict `transactions_data_<chain>` pattern, which is highly predictable. The lone `system_info` tool deviates from the family prefix but is a clearly distinct meta/reference tool, so the break is minor.
Tool Count4/5
Six tools is well-scoped for a transaction-data retrieval product, with each chain family earning its own tool. No bloat or obvious redundancy, though splitting the low-action chains (Solana/XRP/Kaspa) into separate tools is slightly granular.
Completeness4/5
The surface covers the read/lifecycle needs of fetching transaction data across major chain families, with EVM richly covered (details, internal txs, token transfers, logs). Coverage is read-only by nature, but there is no address-based transaction listing, which is a plausible gap for transaction workloads.
Maintenance
ActivityMaintained
ResponsivenessNo issues