@cryptoapis-io/mcpofficial
A
licenseA
qualityB
maintenanceMCP server for Crypto APIs Transactions Data. Enables lookup of transaction details by hash across EVM, UTXO, Solana, XRP, and Kaspa blockchains.
6
74 npm
MIT
cryptoapis-mcp-block-data
OfficialRelated Servers
Alternatives to cryptoapis-mcp-block-data
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP server for Crypto APIs Blockchain Fees product, providing fee recommendations and gas estimates for UTXO, EVM, and XRP blockchains.6224 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
- 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
TDQS
A3.7/5.0
Scored 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
ActivityMaintained
ResponsivenessNo issues