A
licenseNot graded
qualityC
maintenanceMCP server for Cardano blockchain data — exposes on-chain queries, address lookups, transaction history, token metadata, stake pool info, and network parameters to LLM agents.
28 npm
4
MIT
cardano-node-mcp
Related Servers
Alternatives to cardano-node-mcp
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceAn MCP server that provides LLMs with access to 95 tools covering the Koios Cardano blockchain REST API, enabling queries for on-chain data like transactions, addresses, assets, and governance.923-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to manage Cardano wallets, check balances, send ADA and native assets, and settle atomic swaps via a built-in MCP server.2Apache 2.0
- FlicenseNot gradedqualityBmaintenanceOperate a Hydra head by talking to it — an MCP server that exposes lifecycle, ledger, L1 wallets, node logs, and on-chain error codes as tools for LLM clients to drive and debug a head in plain language.-
- AlicenseNot gradedqualityDmaintenanceMCP server that exposes Fund402 protocol tools to Casper testnet, allowing LLMs to execute real on-chain actions like wallet creation, token management, and borrowing via natural language.Apache 2.0
- AlicenseAqualityDmaintenanceMCP server exposing tools for WORM chain sealing, sovereign agent creation, Ada governance contract generation, and SSM state injection from Lean theorems.64Apache 2.0
TDQS
C2.9/5.0
Scored across 64 tools
Disambiguation2/5
Several tool pairs appear to perform identical or near-identical operations, such as cardano_address_key_gen vs cardano_key_generate_payment, cardano_stake_address_key_gen vs cardano_key_generate_stake, and the stake-pool/node key duplication (e.g., cardano_stake_pool_key_gen vs cardano_node_key_gen). While many query and governance tools are distinct, these overlapping boundaries make misselection likely.
Naming Consistency3/5
All names use snake_case with a cardano_ prefix, but ordering conventions are inconsistent: some use domain_action (cardano_transaction_build), others use action_domain (cardano_key_generate_payment), and some duplicate concepts use different patterns. The names are still mostly readable, but the mixed verb/noun ordering reduces predictability.
Tool Count2/5
64 tools is far beyond the typical 3-15 range and includes many redundant or alias-like commands that could be consolidated. The Cardano node domain is broad, so some scale is justified, but the set feels heavy and over-provisioned for a single MCP server.
Completeness4/5
The surface covers a wide range of Cardano node operations: queries, address/key generation, transaction lifecycle, stake address/pool management, governance actions, and DRep operations. Only minor gaps or redundancies are present, so agents can accomplish most intended workflows.
Maintenance
ActivityInactive
ResponsivenessNo issues