_ registry / mcp streamable-http · checked 1h ago

iris

https://iriscan.app

Registry code: f6090b6cfd1addb5

api record

Iris is on-chain intelligence (https://iriscan.app) for Solana, the EVM chains (Ethereum, Base, Arbitrum, Robinhood Chain, BNB Chain), Bitcoin, Tron, dYdX and Noble. Use it to find out who is behind a wallet, where its money came from and went, and whether a Solana token was rigged at launch.

- analyze_address (1 credit, 2 over 1000 transactions, or $0.05 with x402, $0.10 deep): start here for any wallet, or a Solana token mint or program. The chain is read from the address (Solana and Tron base58, 0x, bc1/1/3, dydx1, noble1); for a 0x address on an EVM chain other than Ethereum, pass chain.…

endpoint
https://iriscan.app/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is iris live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is iris free to use?
Yes — the hub reached it with no key and no payment.
What tools does iris have?
6 tools: analyze_address, trace_transfer, find_token_insiders, scan_launch_tool, get_credits, get_connections.
Is iris safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
88ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 6 tools
6 never probed 0 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • analyze_address unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "address"
      ],
      "properties": {
        "chain": {
          "enum": [
            "solana",
            "ethereum",
            "base",
            "arbitrum",
            "robinhood",
            "bsc",
            "bitcoin",
            "tron",
            "dydx",
            "noble"
          ],
          "type": "string",
          "description": "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": {
          "type": "integer",
          "default": 1000,
          "maximum": 10000,
          "minimum": 1,
          "description": "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."
        },
        "address": {
          "type": "string",
          "maxLength": 90,
          "minLength": 26,
          "description": "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."
        }
      },
      "additionalProperties": false
    }
    arguments 38 lines
  • trace_transfer unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "wallet",
        "signature"
      ],
      "properties": {
        "chain": {
          "enum": [
            "solana",
            "ethereum",
            "base",
            "arbitrum",
            "robinhood",
            "bsc",
            "bitcoin",
            "tron"
          ],
          "type": "string",
          "description": "The transfer's chain, when the wallet's address doesn't say it: an EVM chain for a 0x wallet (ethereum by default)."
        },
        "wallet": {
          "type": "string",
          "maxLength": 90,
          "minLength": 26,
          "description": "The wallet whose deposit or withdrawal is traced (not the exchange or the mixer)."
        },
        "direction": {
          "enum": [
            "in",
            "out"
          ],
          "type": "string",
          "description": "Optional, with counterparty: out when the wallet paid it (a deposit), in when it paid the wallet (a withdrawal)."
        },
        "signature": {
          "type": "string",
          "maxLength": 90,
          "minLength": 64,
          "description": "The transaction: a Solana signature (base58), an EVM or Tron transaction hash, or a Bitcoin txid."
        },
        "counterparty": {
          "type": "string",
          "maxLength": 90,
          "description": "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."
        }
      },
      "additionalProperties": false
    }
    arguments 49 lines
  • find_token_insiders unknown 1h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "mint"
      ],
      "properties": {
        "mint": {
          "type": "string",
          "maxLength": 90,
          "minLength": 26,
          "description": "The token's address: a Solana mint (base58), or a 0x token with chain."
        },
        "chain": {
          "enum": [
            "solana",
            "robinhood",
            "bsc"
          ],
          "type": "string",
          "default": "solana",
          "description": "robinhood for a Robinhood Chain token (Pons launches), bsc for a BNB Chain one (Flap and four.meme launches)."
        },
        "limit": {
          "type": "integer",
          "default": 50,
          "maximum": 100,
          "minimum": 1,
          "description": "How many candidate wallets to check (early buyers and top holders). Fewer is faster."
        }
      },
      "additionalProperties": false
    }
    arguments 32 lines
  • scan_launch_tool unknown 1h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "wallet"
      ],
      "properties": {
        "mint": {
          "type": "string",
          "pattern": "^[1-9A-HJ-NP-Za-km-z]+$",
          "maxLength": 44,
          "minLength": 32,
          "description": "Optional: narrow the report to this token (base58 mint)."
        },
        "wallet": {
          "type": "string",
          "pattern": "^[1-9A-HJ-NP-Za-km-z]+$",
          "maxLength": 44,
          "minLength": 32,
          "description": "The Solana wallet (a dev or trader), or a token's mint to scan its creator (base58)."
        }
      },
      "additionalProperties": false
    }
    arguments 23 lines
  • get_credits unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • get_connections unknown 1h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "address"
      ],
      "properties": {
        "chain": {
          "enum": [
            "solana",
            "ethereum",
            "base",
            "arbitrum",
            "robinhood",
            "bsc",
            "bitcoin",
            "tron",
            "dydx",
            "noble"
          ],
          "type": "string",
          "description": "Optional: the chain it was analyzed on, for a 0x address analyzed on several EVM chains. The latest analysis otherwise."
        },
        "limit": {
          "type": "integer",
          "default": 12,
          "maximum": 50,
          "minimum": 1,
          "description": "How many to list, largest by value first."
        },
        "filter": {
          "enum": [
            "all",
            "flagged",
            "exchange",
            "mixer"
          ],
          "type": "string",
          "default": "all",
          "description": "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."
        },
        "address": {
          "type": "string",
          "maxLength": 90,
          "minLength": 26,
          "description": "The address analyze_address analyzed."
        },
        "receipt": {
          "type": "string",
          "maxLength": 64,
          "description": "Only without an API key: the receipt analyze_address gave when it was paid with x402."
        }
      },
      "additionalProperties": false
    }
    arguments 54 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id f6090b6cfd1addb5.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/f6090b6cfd1addb5/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/f6090b6cfd1addb5/badge.svg)](https://brick.blue/agent/f6090b6cfd1addb5?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.