Skip to content

Capabilities

  • Per-call network: Chain tools accept network: "mainnet" | "testnet" | "devnet"; SUI_NETWORK selects the default. Endpoint overrides apply only to that default network. Local-only list_findings, export_case and delete_finding have no network argument.
  • MCP metadata: Tools declare titles and read/write annotations, and tools that can delete local records also declare destructiveHint. trace_funds, build_wallet_edges, screen_address, trace_flow_graph, find_flow_path, get_upgrade_history and classify_deposit_address expose JSON as structuredContent. Selected large results declare anthropic/maxResultSizeChars. See each tool entry for its metadata.
  • Output: JSON tool responses, graph JSON exports and SuiNS resolution annotations use compact encoding. Capped lists report omitted counts and retrieval calls; a local store also exposes omitted rows through result resources.
  • Transaction decoding: get_transaction labels swaps from pool events when the event identifies the coins and can be placed on a call. If that evidence cannot settle the call, it uses the call-based reading. History, timeline and fund traces decode without those events, so check get_transaction before citing their swap direction.
  • Fund flows: trace_funds follows one path; trace_flow_graph and find_flow_path allocate priced coin flows and valued object handovers, including position redemptions. Object edges carry the ID, type, checkpoint USD value and valuation tier. Unvalued object movements are listed separately without a share; a kiosk or wrapper transition can stop the branch as unread. See Fund flows.
  • Coin identity: The curated list vouches for exact types. search_token searches mainnet DEX indexes and confirms pool-backed candidates against on-chain metadata; a bounded metadata scan covers missing results and other networks. Symbols can name several assets. Provider outages, caps and unread confirmations leave coverage partial, so use a full coin type for unverified results. impostor_of marks a symbol lookalike, without claiming intent. See Coin identity and scale.
  • Pool discovery: find_pools searches both token orders across Cetus, DeepBook v2/v3, Turbos, BlueMove v1, Bluefin, Momentum, FlowX CLMM/v2, Magma, Aftermath AMM and Kriya v2. It reports a status per venue, total across discovered pools and omitted.next_call when the pool list is paged. An incomplete venue cannot establish absence. analyze_token inspects liquidity custody for up to three selected SUI/native-USDC pools; those holder scans have their own completeness fields.
  • Event queries: query_events accepts a package, module or full struct under event_type, and ISO 8601 bounds directly under after_checkpoint and before_checkpoint. The distinct module filter names the emitting call. When type origins are readable, type filters rewrite the struct and type arguments to their defining package; check event_type_resolution for other defining versions or unread origins and module_scope for emitting-version boundaries. A short or empty read may still have next_cursor.
  • Multisig: Derives a committee from a sent transaction’s signature and verifies the address; reports members and observed signers over the examined transaction window. Also reports zkLogin and passkey authentication. See Multisig.
  • Move packages: Disassembly, heuristic risk scans, capability audits, publisher attribution, UpgradeCap holder status and upgrade diffs work without a decompiler binary. See Packages and upgrade authority.
  • Chain reads: gRPC serves key lookups, GraphQL serves filtered lists and archive fallback covers older point reads.
  • Prices: Aftermath and DefiLlama supply current prices; DefiLlama and recent-date CoinGecko/GeckoTerminal quotes supply historical prices. Pyth requires PYTH_API_KEY and applies only to verified coin types. See Price sources.
  • Kiosk-held NFTs: Individual kiosks expose the current cap holder; collection-wide scans use sale-derived ownership and mark guesses from the mutable kiosk owner field. See Kiosk-held NFTs.
  • Move Registry: MVR resolves package names such as @deepbook/core and reverse names. See Move Registry tools.

For example, {"token_a":"SUI","token_b":"USDC"} with find_pools returns venues, total and pools; {"event_type":"0x2::coin","after_checkpoint":"2026-08-07T00:00:00Z","before_checkpoint":"2026-08-08T00:00:00Z"} with query_events returns events, has_next_page and next_cursor. Pass the cursor with the same filters and order to continue.