@cryptoapis-io/mcp-utils
OfficialRelated Servers
Alternatives to @cryptoapis-io/mcp-utils
No user-submitted related servers found.
Related Servers
- 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 Block Data product. Get block details by height or hash for EVM, UTXO, and XRP blockchains.4328 npmMIT

@cryptoapis-io/mcpofficial
AlicenseAqualityBmaintenanceMCP server for Crypto APIs Transactions Data. Enables lookup of transaction details by hash across EVM, UTXO, Solana, XRP, and Kaspa blockchains.6307 npmMIT- AlicenseNot gradedqualityBmaintenanceMCP server for Crypto APIs HD Wallet (Wallet as a Service) product. Track and manage HD wallets by their extended public key (xPub/yPub/zPub) — no private keys ever leave your device.181 npm1MIT
- 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
- AlicenseAqualityBmaintenanceMCP server for Crypto APIs Blockchain Fees product, providing fee recommendations and gas estimates for UTXO, EVM, and XRP blockchains.689 npmMIT
TDQS
Scored across 5 tools
The three chain-family utils tools (utxo, evm, xrp) each repeat the same validate-address/decode actions, but their descriptions explicitly enumerate which blockchains belong to each family, so an agent can route correctly. derive_addresses and system_info are clearly distinct. The only residual ambiguity is remembering which chain falls in which family bucket.
Four of five tools follow a predictable snake_case <domain>_utils / system_info noun pattern, which is coherent. derive_addresses breaks the pattern by being an action name rather than a utils family, a minor but noticeable deviation.
Five tools for an address/transaction utilities surface is well-scoped and each earns its place by bundling multiple actions. It sits at the lean end, with derive_addresses getting its own tool while validate/decode are grouped.
The surface covers address validation, raw tx decoding, HD address derivation, X-Address encode/decode, and reference docs across all supported chains — a solid utility lifecycle. Minor gaps exist in that derivation is exposed only for xpubs and other format conversions (beyond BCH) are absent, but agents can work around these.