# Indigo MCP MCP server for [Indigo Protocol](https://indigoprotocol.io/) — exposes Indigo iAsset data, prices, and CDP/loan analytics to LLM agents via the [Model Context Protocol](https://modelcontextprotocol.io/). ## Features - Real-time iAsset prices (iUSD, iBTC, iETH, iSOL) - ADA and INDY token price feeds - CDP/loan browsing with pagination and filtering - Owner lookup by payment key hash or bech32 address - CDP health analysis with collateral ratio and liquidation risk status - Stability pool state and account queries - INDY staking positions and manager state - Protocol analytics: TVL, APR rewards, DEX yields, aggregated stats - Governance: protocol parameters, polls, temperature checks - Redemption order book and queue aggregation - DEX proxy: Steelswap swaps, Iris liquidity pools, Blockfrost balances - CDP liquidation, redemption, freeze, and merge operations - Leveraged CDP opening via LRP positions - LRP (Limit Redemption Protocol) position management - Oracle interest rate feeding and initialization - Stability pool request processing and cancellation - Staking reward distribution - Collector UTXOs, IPFS storage and retrieval ## Quick Start Install globally: ```bash npm install -g @indigoprotocol/indigo-mcp ``` Or run directly with npx (no install needed): ```bash npx @indigoprotocol/indigo-mcp ``` ### Docker ```bash docker build -t indigo-mcp . docker run -i indigo-mcp ``` ### HTTP Transport (Remote) The server supports HTTP transport for remote/hosted deployments: ```bash MCP_TRANSPORT=http PORT=3000 npx @indigoprotocol/indigo-mcp ``` This starts an HTTP server with: - `POST /mcp` — MCP endpoint (Streamable HTTP with SSE) - `GET /health` — Health check ## Configuration > **Note:** `BLOCKFROST_API_KEY` is required for write operations (transaction building). Read-only tools work without it. Get a free key at [blockfrost.io](https://blockfrost.io/). ### Claude Desktop Add to `~/Library/Application Support/Claude/claude_desktop_config.json` (macOS) or `%APPDATA%\Claude\claude_desktop_config.json` (Windows): ```json { "mcpServers": { "indigo": { "command": "npx", "args": ["-y", "@indigoprotocol/indigo-mcp"], "env": { "INDEXER_URL": "https://analytics.indigoprotocol.io/api/v1", "BLOCKFROST_API_KEY": "your-blockfrost-project-id" } } } } ``` ### Claude Code (CLI) Add to `~/.claude/settings.json` or `.claude/settings.json` in your project: ```json { "mcpServers": { "indigo": { "command": "npx", "args": ["-y", "@indigoprotocol/indigo-mcp"], "env": { "INDEXER_URL": "https://analytics.indigoprotocol.io/api/v1", "BLOCKFROST_API_KEY": "your-blockfrost-project-id" } } } } ``` ### Cursor Add to `~/.cursor/mcp.json` (global) or `.cursor/mcp.json` (project-level): ```json { "mcpServers": { "indigo": { "command": "npx", "args": ["-y", "@indigoprotocol/indigo-mcp"], "env": { "INDEXER_URL": "https://analytics.indigoprotocol.io/api/v1", "BLOCKFROST_API_KEY": "your-blockfrost-project-id" } } } } ``` ### Windsurf Add to `~/.codeium/windsurf/mcp_config.json`: ```json { "mcpServers": { "indigo": { "command": "npx", "args": ["-y", "@indigoprotocol/indigo-mcp"], "env": { "INDEXER_URL": "https://analytics.indigoprotocol.io/api/v1", "BLOCKFROST_API_KEY": "your-blockfrost-project-id" } } } } ``` ### Any MCP-Compatible Client Run the server directly via stdio: ```bash INDEXER_URL=https://analytics.indigoprotocol.io/api/v1 \ BLOCKFROST_API_KEY=your-blockfrost-project-id \ npx @indigoprotocol/indigo-mcp ``` Or install globally and reference the binary: ```bash npm install -g @indigoprotocol/indigo-mcp indigo-mcp ``` For any client that supports MCP over stdio, point it to the `npx @indigoprotocol/indigo-mcp` command with the environment variables above. ## Environment Variables - `INDEXER_URL` — Indigo analytics API base URL (default: `https://analytics.indigoprotocol.io/api/v1`) - `BLOCKFROST_API_KEY` — Blockfrost project ID for transaction building (required for write ops) - `CARDANO_NETWORK` — Cardano network: `mainnet`, `preprod`, or `preview` (default: `mainnet`) - `MCP_TRANSPORT` — Transport mode: `stdio` or `http` (default: `stdio`) - `PORT` — HTTP server port when `MCP_TRANSPORT=http` (default: `3000`) ## Example Queries When connected to an LLM agent, you can ask natural language questions like: - "What are the current prices of all Indigo iAssets?" - "What is the price of iUSD right now?" - "How much is ADA worth in USD?" - "Show me all iETH CDPs" - "What CDPs does this address own?" (paste a Cardano address) - "Analyze the health of my CDPs" (with your address or payment key hash) - "Are any of my positions at risk of liquidation?" - "Show me the current stability pool state" - "What are my stability pool deposits?" (with your address) - "How much INDY am I staking?" (with your address) - "What's the current TVL of Indigo?" - "What APR can I earn on iUSD stability pool?" - "What are the current governance protocol parameters?" - "Show me the iUSD redemption queue" - "Get a Steelswap estimate for swapping 100 ADA to iUSD" - "What are the current DEX yields for iAsset pairs?"

MCP readiness

B · 85/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake	10/10	initialize and tools/list both answered.
Live MCP endpoint	23/25	Endpoint answers the MCP initialize handshake (5329 ms); very slow response -2.
Protocol revision	8/10	Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Signed descriptor	n/a	No MCP standard defines a signed server descriptor.
Uptime (30 days)	14.52/15	30/31 probes succeeded over 30 days (97%).
Tool declaration	10/10	Lists 60 tool(s) with descriptions.
Verified identity	5/10	Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags	4/5	seen in a source within 7 days.
Auth declaration	2/5	Declares credential scheme: smithery_api_key.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Very slow (5329 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-11.

Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness: Higher than 78% of peers; This listing 85 · peer median 81
Latency: Faster than 3% of peers; This listing 4,501 ms · peer median 326 ms

Where it loses the most points, and how to win them back

Verified identity −5 — Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Auth declaration −3 — State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
Live MCP endpoint −2 — Answer initialize and tools/list at the declared endpoint.
Now: Endpoint answers the MCP initialize handshake (5329 ms); very slow response -2.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

smithery since 2026-06-04 ↗

How to connect

MCP endpoint (streamable-http)

https://server.smithery.ai/indigoprotocol/indigo-mcp/mcp

JSON-RPC initialize probe

curl -X POST https://server.smithery.ai/indigoprotocol/indigo-mcp/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://indigoprotocol.io/

Listed at (smithery)

https://indigoprotocol.io/