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.
87 npm
4
MIT
IndigoProtocol/indigo-mcp
OfficialRelated Servers
Alternatives to IndigoProtocol/indigo-mcp
No user-submitted related servers found.
Related Servers
- 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
- 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-
- AlicenseCqualityDmaintenanceMCP server enabling LLMs to interact with a Cardano node by wrapping cardano-cli/torsten-cli, supporting queries, transactions, staking, and governance operations.64MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that gives AI agents direct, on-chain access to DeFi data on EVM chains — wallet balances, Aave v3 lending positions, and live token prices, with no centralized API in the middle.1MIT
- AlicenseNot gradedqualityDmaintenanceAgent-native, self-hosted MCP server for crypto trading and DeFi management. Enables agents to query balances, execute trades, and manage positions with a policy engine and secure key storage.7Apache 2.0
TDQS
B3.1/5.0
Scored across 69 tools
Disambiguation2/5
Multiple query tools have unclear boundaries, e.g., get_redemption_queue and get_order_book both return open ROB order-book entries, and get_cdps_by_owner/get_cdps_by_address or get_staking_positions_by_owner/get_staking_position_by_address are near-duplicates. get_assets/get_asset/get_asset_price and get_oracle_price/get_pyth_price also overlap, so agents must read descriptions carefully to avoid misselection.
Naming Consistency4/5
The vast majority follow a consistent snake_case verb_noun pattern (get_*, open_*, close_*, adjust_*). Minor inconsistencies exist: singular get_staking_position_by_address vs plural get_staking_positions_by_owner, and sp/stable_pool abbreviation mixing (get_sp_account_by_owner vs get_stability_pool_accounts).
Tool Count1/5
69 tools far exceeds the well-scoped range and crosses the 50+ extreme threshold. Even though the protocol has many subdomains, the count overwhelms agent tool selection and includes many redundant query variants.
Completeness4/5
Core lifecycle coverage is strong: CDPs, stability pool accounts, staking positions, ROB orders, stableswap orders, and oracles all have open/read/adjust/close equivalents. Minor gaps exist around governance (only temperature checks and polls are readable, no vote/proposal creation) and external DEX actions are query-only, but these are workable.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive