@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 Block Data product. Get block details by height or hash for EVM, UTXO, and XRP blockchains.4328 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 Utils, enabling address validation, raw transaction decoding, and XRP X-Address encoding/decoding for UTXO, EVM, and XRP blockchains.5310 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 AML, enabling verification of blockchain addresses and screening of transactions for fraud, sanctions, and other AML risk categories.2293 npmMIT
- AlicenseAqualityBmaintenanceMCP server for Crypto APIs Blockchain Fees product, providing fee recommendations and gas estimates for UTXO, EVM, and XRP blockchains.6327 npmMIT
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.