API

MCP server

Give an AI agent Iris's tools: it analyzes wallets, drills into their connections, traces transfers and finds a token's insiders, on its own, with your API key.

What it is

The Model Context Protocol lets AI agents (Claude, Cursor, Copilot, ChatGPT) call outside tools. Iris's MCP server gives them its engine: ask “where did the funds of this hack go?” and the agent analyzes the wallet, opens its flagged connections, traces the deposit through the mixer and writes up what it found, each claim with its transactions.


Endpoint	`https://iriscan.app/mcp`
Transport	Streamable HTTP, stateless JSON. Protocol 2025-06-18 (2025-03-26 and 2024-11-05 also accepted).
Auth	Your API key, as for the REST API. Listing the tools needs none; every tool call does.

Tools

Tool	Does	Cost
`analyze_address`	A wallet or a token, summed up for an agent: identity, risk, behaviors, flagged counterparties, top flows. `address`, `depth`? 1 to 10,000 (1,000 by default). A token seen for the first time can take about a minute.	1 analysis, 3 above 1,000 transactions
`get_connections`	The counterparties of an address analyzed through MCP in the last hour: `filter`? all, flagged, exchange or mixer, `limit`? 1 to 50 (12). Swap venues included; says which transactions were read.	Free
`trace_transfer`	Where one transfer through a mixer or an exchange came out: `wallet`, `signature`. Leads, not proof.	1 trace (2 credits from packs)
`find_token_insiders`	The wallets a token's creator is linked to by money: `mint`, `limit`? 1 to 100 (50). Up to about two minutes.	2 analyses, or 2 credits
`get_credits`	Your plan and what is left.	Free

Results are plain text, written to be read by a model, with times in ISO 8601 UTC. Failed calls are refunded, including a call cut short when the client disconnects. An account runs at most three calls at once, and one paid call per request.

Connecting a client

Create a key in Account → API, then add Iris to your client, with your key in place of iris_live_YOUR_KEY.

Claude Code

terminal

1claude mcp add --transport http iris https://iriscan.app/mcp \2  --header "Authorization: Bearer iris_live_YOUR_KEY"

Add --scope user to have it in every project. /mcp shows it connected, with its tools.

Cursor

~/.cursor/mcp.json

1{2  "mcpServers": {3    "iris": {4      "url": "https://iriscan.app/mcp",5      "headers": { "Authorization": "Bearer iris_live_YOUR_KEY" }6    }7  }8}

VS Code

.vscode/mcp.json

1{2  "servers": {3    "iris": {4      "type": "http",5      "url": "https://iriscan.app/mcp",6      "headers": { "Authorization": "Bearer iris_live_YOUR_KEY" }7    }8  }9}

Claude Desktop

claude_desktop_config.json

1{2  "mcpServers": {3    "iris": {4      "command": "npx",5      "args": ["-y", "mcp-remote", "https://iriscan.app/mcp", "--header", "Authorization: Bearer iris_live_YOUR_KEY"]6    }7  }8}

Settings → Developer → Edit Config opens the file; mcp-remote needs Node.js. Restart Claude Desktop after saving.

claude.ai, ChatGPT and other URL-only clients

connector URL

1https://iriscan.app/mcp/iris_live_YOUR_KEY

Add it as a custom connector: in claude.ai under Settings → Connectors, in ChatGPT in developer mode.

A key in a URL is a password

Anyone who sees the URL can spend your credits. Create a separate key just for this connector, so you can revoke it alone, and use the header instead wherever the client allows one.

What to ask

“Analyze 6mmiAP…. Who are its biggest victims, and where did it send the money?”
“This wallet deposited into Privacy Cash yesterday: trace where it came out.”
“Before I buy this token: who are its insiders, and do they still hold?”