Iris
REMOTE · IRISCAN.APP
On-chain investigations: who is behind a wallet, who funded it and where its money went.
Available components
Last scanned (1 day ago)
Scores higher than 46% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Crypto and Web3
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. How we score → Why this is hard to score →
Endpoint Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability56
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 23 Oct 26 59
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Oct 2026 · Probed https://iriscan.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=iriscan.app | CN=YE2,O=Let's Encrypt,C=US | 29 Sept 2026 | 28 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 51cd183375e73bfff61e823b47f71826d99 |
| SANs: iriscan.app | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of iriscan.app. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| iriscan.app. | present | 6808 | 13 | Verified |
| iriscan.app. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://iriscan.app/mcp | Verified | 200 | |
| http (plaintext) | http://iriscan.app/mcp | HTTPS enforced | 308 | https://iriscan.app/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze_address Analyze an address on Solana, an EVM chain, Bitcoin, Tron, dYdX or Noble ~454
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | 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. |
No output schema declared.
No examples provided.
find_token_insiders Find a token's insiders ~234
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The token's address: a Solana mint (base58), or a 0x token with chain. |
No output schema declared.
No examples provided.
get_connections Get an address's connections ~276
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | 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. |
No output schema declared.
No examples provided.
get_credits Get credits left ~54
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
scan_launch_tool Scan a wallet for a launch tool (Proxima, BlockX) ~294
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.
| Name | Type | Req | Description |
|---|---|---|---|
| mint | string | – | Optional: narrow the report to this token (base58 mint). |
| wallet | string | yes | The Solana wallet (a dev or trader), or a token's mint to scan its creator (base58). |
No output schema declared.
No examples provided.
trace_transfer Trace a transfer through a mixer, exchange or swap service ~515
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The transaction: a Solana signature (base58), an EVM or Tron transaction hash, or a Bitcoin txid. |
| wallet | string | yes | The wallet whose deposit or withdrawal is traced (not the exchange or the mixer). |
No output schema declared.
No examples provided.
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.
remote · iriscan.app
claude mcp add --transport http 0xvector0-iris 'https://iriscan.app/mcp'
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.