# Iris (remote · iriscan.app)

On-chain investigations: who is behind a wallet, who funded it and where its money went.

- Trust score: 59/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `iriscan.app`: 59/100 (this document), [markdown](https://verifymcp.io/servers/0xvector0-iris/iriscan.md), [page](https://verifymcp.io/servers/0xvector0-iris/iriscan)

## Channel facts

- Endpoint: `https://iriscan.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-23.

- **Endpoint Security**: 60/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 56/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2627 tokens (~437/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "trace_transfer" implies "transfer" and declares readOnlyHint instead, contradicting what its own name says it does.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Iris MCP server?

Iris is a hosted endpoint at https://iriscan.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http 0xvector0-iris 'https://iriscan.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "0xvector0-iris": {
      "url": "https://iriscan.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "0xvector0-iris": {
      "type": "http",
      "url": "https://iriscan.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.0xvector0-iris]
url = "https://iriscan.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "0xvector0-iris": {
      "type": "remote",
      "url": "https://iriscan.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add 0xvector0-iris --url 'https://iriscan.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  0xvector0-iris:
    url: "https://iriscan.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "0xvector0-iris": {
      "Transport": "http",
      "Url": "https://iriscan.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add 0xvector0-iris -t streamable-http -u 'https://iriscan.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "0xvector0-iris": {
      "type": "http",
      "url": "https://iriscan.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-23 (score 59)

First indexed and scored.

## MCP tools (6)

### `analyze_address` (~454 tokens)

Analyze an address on Solana, an EVM chain, Bitcoin, Tron, dYdX or Noble

Analyze a wallet with Iris: on Solana (also a token mint or a program), Ethereum, Base, Arbitrum, Robinhood Chain, BNB Chain, Bitcoin, Tron, dYdX or Noble. The chain is read from the address (0x is Ethereum unless chain says another EVM chain). Costs 1 credit (2 when depth is over 1000), or without an API key $0.05 ($0.10 deep) paid per call with x402; refunded (never settled) if it fails. A token, or a wallet Iris hasn't read recently, can take about a minute. For a wallet: what it is (exchange, MEV bot, drainer, sniper, scam or poisoning wallet, personal wallet...), its risk score, the database's labels on it, its behaviours with example transactions, who sent it its first SOL (Solana), where its money came from and went (largest counterparties, labeled), look-alike (address poisoning) addresses, and the exchanges and mixers it moved money with, with the latest transaction for each (to use with trace_transfer). For a token mint: its creator and the creator's funder, the launch bundle and who funded it, red flags, the wallets in its groups and its top holders. For a program: who can upgrade it, who deployed it, its top callers. Only the latest transactions (depth) are read. Returns a summary and a link to the full view on iriscan.app.

Input parameters:

- `address` (string, required): The address: Solana or Tron base58, 0x (EVM), Bitcoin (bc1, 1 or 3), dydx1 or noble1. On Solana also a token mint or a program.
- `chain` (string): The chain, when the address's form doesn't say it: an EVM chain for a 0x address (ethereum by default). Read from the address otherwise.
- `depth` (integer): How many of the most recent transactions to read. Over 1000 is a deep analysis (2 credits, or $0.10 with x402). Smaller is faster: 200 is often enough for a first look.

### `trace_transfer` (~515 tokens)

Trace a transfer through a mixer, exchange or swap service

Follow one transfer through the mixer (Privacy Cash, Cloak, Umbra, encrypt.trade, MagicBlock Private Payments, ShadowWire...), exchange, or instant-swap service (SideShift, ChangeNOW, FixedFloat, SimpleSwap, StealthEX, Changelly...) on its other side, by timing and amount: for a deposit, the withdrawals that match it after; for a withdrawal, the deposits that match it before. Gives the likely wallets with a confidence, and how many transfers of the same amount could also fit (the anonymity set). A swap service pays out in another asset, often on another chain: a deposit into SideShift is matched exactly from SideShift's public record of completed shifts (the coin, network and amount it paid out, and the Solana recipient), any other by value at the prices of the time (1 of N candidates). One-time deposit addresses that sweep to the service count as the service. Give the wallet and the signature (transaction hash) of a transaction where it sent money to, or received money from, a mixer, an exchange or a swap service (analyze_address and get_connections list them). Off Solana: on Tron through an exchange or an instant exchange, on an EVM chain through an instant exchange or a privacy pool (Tornado Cash, Railgun, Privacy Pools), on Bitcoin through a CoinJoin or an instant exchange. The chain is read from the wallet's address (pass chain for an EVM chain other than Ethereum). Costs 1 trace (or 3 pack credits), or without an API key $0.25 paid per call with x402; refunded (never settled) if it fails. Results are leads, not proof.

Input parameters:

- `chain` (string): The transfer's chain, when the wallet's address doesn't say it: an EVM chain for a 0x wallet (ethereum by default).
- `counterparty` (string): Optional: the exchange, swap service or mixer wallet (or pool contract) on the other side, when the transaction moved money with several. Iris picks the one it knows otherwise.
- `direction` (string): Optional, with counterparty: out when the wallet paid it (a deposit), in when it paid the wallet (a withdrawal).
- `signature` (string, required): The transaction: a Solana signature (base58), an EVM or Tron transaction hash, or a Bitcoin txid.
- `wallet` (string, required): The wallet whose deposit or withdrawal is traced (not the exchange or the mixer).

### `find_token_insiders` (~234 tokens)

Find a token's insiders

Find the wallets a token's creator is linked to by money (a Solana token, or a Robinhood Chain or BNB Chain one with chain): wallets it funded, wallets that paid it, wallets with the same funder, among the token's earliest buyers, the wallets handed tokens at launch and its largest holders. Says how much of the supply they bought and hold, with the transactions that link them, and why none were found when none were. Costs 2 credits, or without an API key $0.10 paid per call with x402; refunded (never settled) if it fails. Can take up to two minutes. Results are leads, not proof.

Input parameters:

- `chain` (string): robinhood for a Robinhood Chain token (Pons launches), bsc for a BNB Chain one (Flap and four.meme launches).
- `limit` (integer): How many candidate wallets to check (early buyers and top holders). Fewer is faster.
- `mint` (string, required): The token's address: a Solana mint (base58), or a 0x token with chain.

### `scan_launch_tool` (~294 tokens)

Scan a wallet for a launch tool (Proxima, BlockX)

Whether a Solana wallet launched or traded memecoins with a launch kit, Proxima (proxima.tools) or BlockX, with the evidence. Proxima: its 5% sell fees (a separate bare transfer after each sell, built with it), its 5% cut of pump.fun creator-fee claims, its receipt round trips (895,880 lamports out, 890,880 back). BlockX: its fee inside each trade (0.4% to 0.8%), its nonce relay funding, cash-outs through nonce accounts created and emptied within seconds, its sweep of their rent. Lists the tokens the wallet launched and the relays tipped, the sells the tool took its fee on, each fee wallet (what it was paid, its balance now, whether it ever sent anything out), the creator-fee claims, and the tree of wallets that funded it, walked up to its root funder with what Iris knows of that root. A token's mint scans its creator. Free with an API key, or without one $0.02 paid per call with x402; never settled if it fails. Can take up to two minutes.

Input parameters:

- `mint` (string): Optional: narrow the report to this token (base58 mint).
- `wallet` (string, required): The Solana wallet (a dev or trader), or a token's mint to scan its creator (base58).

### `get_connections` (~276 tokens)

Get an address's connections

Every counterparty of an address that analyze_address analyzed in the last hour on this account (without an API key: for the x402 payer whose receipt is given): wallets it sent to or received from and the venues it swapped on, with labels, the native coin (SOL, ETH, BTC, TRX...) and stablecoins moved each way, the number of transactions, and the date and signature of its first and last transfer (for trace_transfer). Covers the transactions that analysis read only. For a token: the wallets in its groups (creator, bundlers, insiders, wallets handed supply) and its top holders. Free, from the earlier analysis; run analyze_address first.

Input parameters:

- `address` (string, required): The address analyze_address analyzed.
- `chain` (string): Optional: the chain it was analyzed on, for a 0x address analyzed on several EVM chains. The latest analysis otherwise.
- `filter` (string): flagged: threats, sanctioned and mixer counterparties, and look-alike (address poisoning) ones; for a token, its creator, bundlers and insiders. exchange or mixer: only those.
- `limit` (integer): How many to list, largest by value first.
- `receipt` (string): Only without an API key: the receipt analyze_address gave when it was paid with x402.

### `get_credits` (~54 tokens)

Get credits left

The account's plan and what is left: analyses, traces and pack credits, when the allowance renews, and what each tool costs. Without an API key: what each tool costs per call with x402. Free.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/0xvector0-iris/iriscan#diagnostics

## Score history

- 2026-10-23: 59

## Common questions

### What is the Iris MCP server?

Iris is an MCP server listed in the public MCP registry as io.github.0xVector0/iris. On-chain investigations: who is behind a wallet, who funded it and where its money went. This page covers its hosted endpoint (https://iriscan.app/mcp).

### Is the Iris MCP server safe to use?

Iris scores 59 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Iris MCP server expose?

Iris exposes 6 tools: analyze_address, trace_transfer, find_token_insiders, scan_launch_tool, get_connections, get_credits. Their descriptions and schemas cost roughly 1,827 tokens of context every time the server is loaded.

### Does the Iris MCP server require authentication?

No. We connected to Iris without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Iris MCP server still maintained?

Iris is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://iriscan.app/mcp
- Authorisation metadata: https://iriscan.app/.well-known/oauth-protected-resource/mcp
- Website: https://iriscan.app/mcp
- Changelog RSS feed: https://verifymcp.io/servers/0xvector0-iris/iriscan.xml
- Changelog JSON feed: https://verifymcp.io/servers/0xvector0-iris/iriscan.json
- HTML version of this page: https://verifymcp.io/servers/0xvector0-iris/iriscan