A
licenseNot graded
qualityC
maintenanceMCP server for Crypto APIs Transactions Data. Enables lookup of transaction details by hash across EVM, UTXO, Solana, XRP, and Kaspa blockchains.
27 npm
MIT
Crypto APIs MCP Broadcast
OfficialRelated Servers
Alternatives to Crypto APIs MCP Broadcast
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables to simulate EVM transactions (dry-run) to preview results, gas usage, and state changes before broadcasting on supported blockchains.32 npmMIT
- AlicenseAqualityCmaintenanceMCP server for Crypto APIs Prepare Transactions product that builds unsigned EVM transactions for native coin, fungible token (ERC-20), and NFT (ERC-721) transfers.250 npmMIT
Tatum MCP Serverofficial
AlicenseBqualityDmaintenanceProvides access to Tatum's blockchain API across 40+ networks, enabling developers to interact with blockchain data, manage notifications, estimate fees, access RPC nodes, and work with smart contracts through natural language.31113 npm15MIT- AlicenseNot gradedqualityDmaintenanceEnables blockchain payment operations across multiple networks including Base, Ethereum, BSC, Polygon, and Avalanche. Supports balance queries, token transfers, transaction tracking, wallet management, and gas fee estimation with built-in security limits.MIT
- AlicenseAqualityBmaintenanceMCP server for local transaction signing across EVM, UTXO, Tron, and XRP blockchains, with no network calls or API keys required.7538 npmMIT
TDQS
A4.1/5.0
Scored across 2 tools
Disambiguation5/5
The two tools serve completely distinct purposes: one performs an action (broadcast_signed_transaction) and the other returns static reference documentation (system_info). There is no realistic way to confuse them, so misselection is essentially impossible.
Naming Consistency4/5
Both names use snake_case, which is consistent. However, the conventions differ semantically: one is a verb_noun action name while the other is a noun_phrase reference name, a minor deviation.
Tool Count3/5
Two tools is thin for a server branded as 'Crypto APIs,' even though it is scoped to the Broadcast product. system_info is a generic helper rather than a broadcast operation, so the effective actionable surface is only a single tool.
Completeness3/5
The domain is transaction broadcasting, but there is no way to check broadcast status, query a transaction, or estimate fees—all common follow-ups after submitting a signed hex. Coverage of the core send operation is present but leaves agents at a dead end for verification.
Maintenance
ActivityMaintained
ResponsivenessNo issues