Is sy88tvipKfaCTuVVeU2PczPa88hqgPfKnYQyCHboHP8 a bot? What does it do?
analyze_address{ "address": "sy88tv…oHP8" }1 analysisYes. Iris identifies it as an MEV arbitrage bot, with 95% confidence. It swaps on Jupiter and BisonFi and tips Jito to get its transactions in first.
Its risk score is low, 10 out of 100. The full report, with the transactions behind each finding: iriscan.app/sy88tv…oHP8
What you can ask
Ask in plain words.
Get the evidence back.
Your assistant picks the tool, reads the result and answers with a link to the full view on iriscan.app. A few questions to start with:
“Who funded 4G9JAzftaydKjB2558MLnkYw175KMN6NGGgyxkeRuwwA, and is it a bot?”
Usesanalyze_address
“Was token FT6wo71X9c3SRnvuccZhrDywryodxJEWo2zadndUdYKb bundled at launch? Who are the insiders?”
Usesfind_token_insiders
“This wallet deposited into Privacy Cash in tx <sig>. Where did the money come out?”
Usestrace_transfer
“Which exchanges did it cash out to, and when?”
Usesget_connections
Tools
Eight tools.
The same engine as the API.
Paid tools count like API requests, from your plan's allowance and then your credits. A call that fails is refunded.
analyze_address1 analysis
2 over 1,000 transactions
The full Iris report on a wallet or a token: who it is, how risky, what it did and the transactions that show it.
addressstringA wallet on Solana, an EVM chain (0x), Bitcoin, Tron, dYdX or Noble, or a Solana token mint or program.chainstringoptionalFor a 0x address: ethereum, base, arbitrum, robinhood, bsc or polygon. Defaults to ethereum; other chains are read from the address.depthintegeroptionalRecent transactions to read, 1 to 10,000. Defaults to 1,000.
1 analysis
2 over 1,000 transactions
get_connectionsFree
after analyze_address
Every counterparty of an address you just analyzed, with its label, the amounts each way and the first and last transaction. Filter to the flagged ones, the exchanges or the mixers.
addressstringAn address analyzed with analyze_address in the last hour.chainstringoptionalFor a 0x address analyzed on several EVM chains. Defaults to the latest analysis.filterstringoptionalall, flagged, exchange or mixer. Defaults to all.limitintegeroptionalHow many, largest by value first, 1 to 50. Defaults to 12.
Free
after analyze_address
trace_transfer1 trace
or 3 pack credits
Follows one deposit or withdrawal through a mixer or an exchange, and ranks the wallets on the other side that most likely belong to the same person.
walletstringThe wallet whose transfer is traced.signaturestringA transaction where the wallet sent to, or received from, a mixer or an exchange.chainstringoptionalFor a 0x wallet: the EVM chain of the transfer. Defaults to ethereum; Solana, Bitcoin and Tron are read from the address.hopsintegeroptional2 to trace it as a private swap through two exchanges, Houdini-style (Houdini Swap's partner exchanges), even to an address Iris doesn't know (taken as a partner's one-time deposit address). Named a Houdini Swap route only with partner wallets on both legs. A lead, not proof.
1 trace
or 3 pack credits
find_token_insiders2 analyses
Walks back the funding of a token's creator, earliest buyers and largest holders, and returns the wallets linked to the creator by money.
mintstringThe token's mint address.limitintegeroptionalWallets to check besides the creator, 1 to 100. Defaults to 50.chainstringoptionalrobinhood for a Robinhood Chain token, bsc for a BNB Chain one (a 0x address). Defaults to solana.
2 analyses
scan_launch_toolFree
20 a day on the free tier
Whether a Solana wallet launched or traded with a launch kit (Proxima or BlockX), with the evidence: Proxima's 5% sell fees and cut of creator-fee claims, BlockX's fee inside each trade and its nonce cash-outs, the fee wallets, and the tree of wallets that funded it up to the root funder.
walletstringThe dev or trader wallet. A token's mint scans its creator.mintstringoptionalNarrow the report to one token.
Free
20 a day on the free tier
follow_funds2 analyses
Follows the main stream of money out of one wallet, hop by hop, until it reaches an exchange, a bridge, a mixer or a swap, splits, or comes to rest. Each hop says how the money went; at a bridge it says where the money landed, to follow on there.
addressstringThe wallet to follow from: Solana, an EVM chain (0x), Bitcoin or Tron.chainstringoptionalFor a 0x address: the EVM chain. Defaults to ethereum; the others are read from the address.assetstringoptionalnative, or a token's mint or contract. Defaults to whatever left the wallet, dollars first.sinceintegeroptionalOnly what left from this time on (Unix seconds), e.g. a drain's time.max_hopsintegeroptionalHops at most.
2 analyses
explain_transactionFree
with an account
One transaction in plain words: who moved what to whom, the swap or bridge transfer it made, a token lock with its schedule, its parties with their labels, and on Solana the acts that need a key.
hashstringA Solana signature, an EVM hash, or a Bitcoin, Tron, dYdX or Noble hash.chainstringoptionalThe chain. Read from the hash otherwise.
Free
with an account
get_creditsFree
Your plan, and the analyses, traces and pack credits you have left.
No input.
Free
Connect
Add Iris to your client.
One URL and your API key. Pick your client for its exact setup, with your key in place of iris_live_YOUR_KEY.
1claude mcp add --transport http iris https://iriscan.app/mcp \2 --header "Authorization: Bearer iris_live_YOUR_KEY"- 1
Run it in a terminal, with your key in place of
iris_live_YOUR_KEY. - 2
Add
--scope userto have Iris in every project, not only the current one. - 3
In Claude Code,
/mcpshows iris as connected, with its tools.
Another client? This is all it needs.
URL
https://iriscan.app/mcpTransport
Key
API key
Your Iris key,
your Iris credits.
The MCP server uses the same keys and the same credits as the API. Nothing new to sign up for.
Create a key
In Account → API. It starts with iris_live_ and is shown once, so copy it into your client right away.
Open Account → APIPay as you do for the API
Tool calls count like API requests: your plan's allowance first, then pack credits. Every account starts with 10 free analyses and 2 traces, then gets 3 analyses a day.
See pricingSee what you used
Ask your assistant for your credits: get_credits is free. Every call also shows on the Overview tab of your account.
Open OverviewQuestions
Before you connect.
What does Iris receive?+
Only the tool calls your assistant makes: the tool's name and its arguments, such as an address, a transaction signature or a list of addresses. Your conversation, your prompts and your files stay with your assistant.
Why treat the key, and the connector URL, like a password?+
Anyone who has either can run tools on your account and spend your credits. Keep them out of shared configs and repositories. For the URL-only connector, create a separate key just for it, so you can revoke it on its own without breaking your other integrations, and use the header wherever a client supports one. If one leaks, revoke it in Account → API.
What are the limits?+
Paid tools draw on your plan's allowance, then on your pack credits. When both are spent, the tool returns an error your assistant can read, with where to top up. Calls with a key also count toward the API's call limit: 10 a day on the free tier, or your plan's calls per 10 minutes (50 on Individual). Past it, the tool returns an error with the code quota_exceeded and nothing is charged. Tool calls share the API's limit of three running at once per account. A call that fails is refunded.
How do I check what my assistant concluded?+
Every result links back to its full view on iriscan.app, such as iriscan.app/<address>: the report, the source of every label and the transactions behind each finding.
Does it work without a key?+
A client can connect and list the tools without one, so directories and inspectors can see what Iris offers. An agent with a wallet can also call them without one, paying each call in USDC with x402 ($0.05 an analysis), which an x402 client does on its own. Otherwise calling a tool needs a key, the free ones too, since they answer for your account.
Which clients work?+
Any client that connects to remote MCP servers over Streamable HTTP. A client that only runs local servers can reach it through mcp-remote, as Claude Desktop does above.