cryptoapis-mcp-block-data
OfficialRelated Servers
Alternatives to cryptoapis-mcp-block-data
No user-submitted related servers found.
Related Servers
AlicenseAqualityBmaintenanceMCP server for Crypto APIs Transactions Data. Enables lookup of transaction details by hash across EVM, UTXO, Solana, XRP, and Kaspa blockchains.6307 npmMIT- AlicenseAqualityBmaintenanceMCP server for Crypto APIs Blockchain Fees product, providing fee recommendations and gas estimates for UTXO, EVM, and XRP blockchains.689 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 Prepare Transactions product that builds unsigned EVM transactions for native coin, fungible token (ERC-20), and NFT (ERC-721) transfers.8305 npmMIT
TDQS
Scored across 4 tools
The three block-data tools are separated by blockchain family (EVM, UTXO, XRP), which gives clear selection rules when the chain is known. However, they expose identical action names, so an agent must first classify the target chain and could confuse EVM vs. UTXO if the chain is unspecified. system_info is clearly distinct as a reference tool.
The three main tools follow a predictable snake_case pattern of [chain_family]_block_data. system_info deviates from that pattern but is a clearly separate reference utility, making the inconsistency minor and understandable.
Four tools is well-scoped for a block-data server: three chain-family wrappers plus one reference tool. Each tool earns its place by consolidating multiple related actions, avoiding an overly fragmented surface.
The surface covers the full block-data lifecycle for all supported chain families: block by height/hash, transaction listing by block height/hash, and latest-mined-block retrieval. system_info fills the supporting reference/documentation role, leaving no obvious gaps for the stated purpose.