indigo-mcp

indigo-mcp is the MCP (Model Context Protocol) server for Indigo Protocol, whose purpose is to let large language model (LLM) agents access data and operations related to Indigo Protocol on the Cardano blockchain through the MCP protocol.

I. Purpose and Positioning This server exposes Indigo's iAsset data, prices, and CDP/lending analysis capabilities to LLM agents. Official materials describe it as part of a further Cardano DeFi technology stack, and it can be combined with Cardano MCP to obtain full capabilities.

II. Main Capabilities According to official materials, this MCP server provides (a total of 75 tools, plus 13 optional AI Skills) the following capabilities:

• Real-time iAsset prices (iUSD, iBTC, iETH, iSOL, iEUR, iJPY)
• ADA and INDY token price sources
• CDP/lending browsing, with pagination and filtering support
• Query owners by payment key hash or bech32 address
• CDP health analysis, including collateral ratio and liquidation risk status
• Stability pool status and account queries
• INDY staking positions and manager status
• Protocol analytics: TVL, APR rewards, DEX yields, aggregate statistics
• Governance: protocol parameters, voting, temperature checks
• Redemption order book and queue aggregation
• DEX proxy: Steelswap swaps, Iris liquidity pools, Blockfrost balances
• CDP liquidation, redemption, freezing, and merging operations
• Open leveraged CDPs through ROB positions
• ROB (Redemption Order Book) position management
• Oracle interest rate feeds and initialization
• Stability pool request processing and cancellation
• Staking reward distribution
• Collector UTXO, IPFS storage and retrieval The tool categories in the materials include: CDP/loan tools, CDP write tools, CDP mint/burn tools, CDP liquidation and redemption tools, leveraged CDP tools, stability pool tools, stability pool request tools, staking write tools, staking reward tools, analytics and APR tools, governance tools, redemption and order book tools, ROB write tools, DEX proxy tools, Collector and IPFS tools, interest rate tools (v3), oracle/Pyth tools (v3), Stableswap Tool (v3).

III. Usage

1. Automatic installation (recommended): Run the interactive installation script, which automatically configures MCP clients (Claude Desktop, Claude Code, Cursor, Windsurf), asks for the Blockfrost API key, and automatically updates the configuration file, with no manual editing required.
2. Manual installation: Can be installed globally, or run directly with npx (no installation required).
3. HTTP transport (remote/hosted deployment): The server supports HTTP transport, providing POST /mcp (Streamable HTTP with SSE) and GET /health health check; each client has an independent session, initialize returns Mcp-Session-Id, which must be included in subsequent requests, and a client restart can re-initialize without affecting existing sessions. The bind address and port come from HOST and PORT.
4. Hosted deployment: Official materials mention a hosted deployment on Fronteir AI.
5. Environment variables: BLOCKFROST_API_KEY is required for write operations (transaction construction); read-only tools do not require this key; a free key can be obtained at blockfrost.io.
6. Example read-operation queries (natural language): such as "What are the current prices of all Indigo iAssets?" "What is the current price of iUSD?" "How much is ADA worth in USD?" "Show all iETH CDPs" "Which CDPs does this address own?" "Analyze my CDP health" "Is my position at risk of liquidation?" "Show the current stability pool status" "How much is my deposit in the stability pool?" "How much INDY have I staked?" "What is Indigo's current TVL?" "What APR can be earned in the iUSD stability pool?" "What are the current governance protocol parameters?" "Show the iUSD redemption queue" "Estimate the Steelswap quote for swapping 100 ADA to iUSD" "What is the current DEX yield for the iAsset trading pair?" etc.

IV. Time limit for price-dependent writes Materials indicate that iAssets priced by Pyth have a submission deadline: each iAsset is currently priced via Pyth, and the on-chain price feed validator only accepts transactions that embed the price update within 280 seconds after the price update. Price-dependent write tools (open_cdp, withdraw_cdp, mint_cdp, redeem_cdp, freeze_cdp, leverage_cdp, redeem_rob) will return a summary.pyth block containing the price, timestamp, and submitBefore deadline. If signing takes longer than that deadline (for example, a hardware wallet or manual confirmation in a browser), the transaction should be rebuilt rather than submitting an expired transaction; expired price updates will be rejected at build time with a retry prompt.

V. x402 Payment Gating (Optional) This MCP optionally uses the x402 protocol to apply per-call micropayment gating to tool calls; it is disabled by default and requires at least one wallet address to be set before it can be enabled. The pricing is: read tools (such as get_tvl, get_asset_price) cost 0.001 USDC each; analysis tools (such as analyze_cdp_health) cost 0.005 USDC each; write tools (such as open_cdp, mint_cdp) cost 0.01 USDC each. A split execution model is used: tool calls do not require the caller to provide a payment header; the gate intercepts and contacts the settlement worker (default mcp.openmm.io), the worker returns 402 and the EIP-3009 requirements (amount, payee, chain), the gate signs locally using X402_PRIVATE_KEY (the key never leaves this process), retries with the signed payment, and after the worker verifies on-chain and issues a JWT, the gate verifies the JWT locally, executes the original tool handler, and injects the settlement transaction hash into the tool response. This design means indigo-mcp never holds the receiving wallet, only the payment key. Relevant environment variables include PAYMENT_SERVER and X402_PRIVATE_KEY; when X402_PRIVATE_KEY is not set, gating is disabled and all tools can be executed without payment. For Base mainnet, X402_TESTNET must be set to false or omitted.

VI. Runtime Environment and Technical Notes Node.js >= 20 is required (the built-in undici requires the File global object introduced in Node 20). The server communicates via stdio using JSON-RPC, and tools can be tested directly through stdin. Distribution channels include npm, MCP Registry, container images (the Dockerfile builds from source, for container hosts such as Fly), and Smithery. Release process: merge the version number change (SERVER_VERSION is read from package.json), tag and push, CI first publishes to npm and then to MCP Registry (the registry verifies ownership through the package's mcpName field, so npm must be published first), deploy the hosted HTTP endpoint using fly deploy, and publish to Smithery using pnpm smithery:publish.

VII. Limitations and Notes Price-dependent writes are subject to a 280-second submission deadline, and expired transactions will be rejected. Write operations require BLOCKFROST_API_KEY. x402 payments are disabled by default, and once enabled are billed according to the standards above. The materials do not provide a specific charging model, details beyond the scope of platform support, or guarantees of results.host usage) and Smithery. Release process: merge the version number change (SERVER_VERSION is read from package.json), tag and push, CI first publishes to npm and then to MCP Registry (the registry verifies ownership through the package's mcpName field, so npm must be published first), deploy the hosted HTTP endpoint using fly deploy, and publish to Smithery using pnpm smithery:publish.

VII. Limitations and Notes Price-dependent writes are subject to a 280-second submission deadline, and expired transactions will be rejected. Write operations require BLOCKFROST_API_KEY. x402 payments are disabled by default, and once enabled are billed according to the standards above. The materials do not provide a specific charging model, details beyond the scope of platform support, or guarantees of results.