Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Sui Analytics

NPM · SUI-ANALYTICS-MCP

Read-only Sui analytics: fund tracing, protocol-aware tx decoding, no API keys or wallet.

Available components

−1 this week 91 Trust /100

Last scanned (23 hours ago)

Scores higher than 93% of npm servers

Category Crypto and Web3

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security99
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 44 of 173 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to 0xfreak0/sui-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 9 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability77
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 5898 tokens (~280/item across 21 items; 20 tools + 1 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 Management69
  • Stability check failed: the tool surface changed between 1.18.0 and 1.27.0: 0 tool removals, 4 breaking changes, 1 additions. See how to fix → Fail
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 Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

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.

  • 16 Oct 26 −3

    No change was recorded against any check on this day. Stability & Change Management went from 89 to 69.

  • 14 Oct 26 +44
    • Stability: unverified → fail ▼ security
    • Injection markers: unverified → pass ▲ security
    • Tool coverage: unverified → 100 ▲ functional
    • Schema quality: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Package version: 1.26.0 → 1.27.0 functional
  • 13 Oct 26 +1
    • Security disclosure: unverified → pass ▲ functional
    • Package version: 1.26.0 → 1.27.0 functional
  • 11 Oct 26 −43
    • Stability: fail → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Security disclosure: pass → unverified ▼ functional
    • Schema quality: 100 → unverified ▼ functional
    • Package version: 1.26.0 → 1.27.0 functional
  • 5 Oct 26 −2

    No change was recorded against any check on this day. Stability & Change Management went from 89 to 73.

  • 3 Oct 26 +1
    • Security disclosure: unverified → pass ▲ functional
  • 2 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 82 to 86.

  • 1 Oct 26 +13
    • Stability: fail → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Malware scan: unverified → pass ▲ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Security disclosure: pass → unverified ▼ functional
    • Schema quality: 100 → unverified ▼ functional
    • Package version: 1.25.0 → 1.26.0 functional
Diagnostics

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 16 Oct 2026 · Analysed npm/sui-analytics-mcp@1.27.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo 0xfreak0/sui-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/0xfreak0/sui-mcp/.github/workflows/publish.yml@refs/tags/v1.27.0
Rekor log index 3114729800
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:1ed8e29a436425300c9062f276b21cad4499ffb4914027ff2f6fedb477d1444964d2452b07ede4f67579354ad2b7c709cb62e91613418a58df748e733

Background: How many MCP packages publish verified provenance →

Dependencies 173 packages
Packages resolved 173
Stale 44
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 20 exposed · ~5,456 tokens

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 →

Tool Tokens
analyze_token ~245

(Recommended for token research) Get a comprehensive analysis of a Sui token in one call: metadata, current price, 24h change, total supply, and top 5 holders. Accepts either a coin type (e.g. '0x2::sui::SUI') or a symbol (e.g. 'DEEP', 'cetus'). A symbol several coins use returns status ambiguous_symbol with candidates (verified first, then by supply) from a symbol index of every mainnet coin up to its sync date. A symbol more than 100 coins use returns its count and no candidates, since the index keeps only the count; a coin published after the sync date is found only by a bounded live scan.

NameTypeReqDescription
include_holdersboolean–Include top 5 holders (default: true). Set false for faster response.
networkstring–Network: 'mainnet' (default) | 'testnet' | 'devnet'
querystringyesSymbol ('deep') or full coin type ('0x2::sui::SUI'). A symbol matches exactly, in any case; use search_token for partial names.

No output schema declared.

No examples provided.

enable_tools ~416

Turn on more Sui tool profiles for this session. When a tool you need is not in your list, call this first: it is disabled, not missing. Do not rebuild a tool by hand. Pass `profile` or `profiles`: one name, several, or 'all'. Enabled tools are callable at once. 'forensics' (incident investigation: tracing, attribution, clustering, packages, labels, case findings): resolve_protocol_packages, sample_control_addresses, trace_funds, trace_flow_graph, find_flow_path, resolve_bridge_transfer, find_funding_source, find_funding_sources, get_address_fanout, classify_deposit_address, screen_address, build_wallet_edges, analyze_multisig, find_shared_multisig, check_coin_restrictions, analyze_package, get_package, get_move_function, disassemble_module, build_timeline, trace_object_history, get_upgrade_history, manage_labels, query_events, check_activity, get_top_holders, compare_oracle_price, analyze_attack_tx, summarize_incident_losses, summarize_address_flows, aggregate_events, save_finding, list_findings, export_case, delete_finding, watch_addresses, poll_watch, get_nft_sales 'developer' (Move packages, bytecode, upgrades, PTBs, unsigned transactions, MVR): get_package_dependency_graph, decompile_module, diff_package_upgrade, decode_ptb, simulate_transaction, build_transfer, build_staking, get_checkpoint, list_dynamic_fields, mvr_resolve, mvr_reverse_resolve, mvr_get_package_info, mvr_search, mvr_resolve_struct 'market' (DeepBook, pools, token search, validators): deepbook_orderbook, deepbook_trades, get_pool_stats, search_token, get_coin_info, get_validators On: core.

NameTypeReqDescription
profile––Profile to enable, or 'all'. Accepts several: ['forensics','developer'].
profiles––Alias for `profile`. Same values; use whichever reads better.

No output schema declared.

No examples provided.

find_pools ~174

Find liquidity pools for a token pair across Cetus, DeepBook v2/v3, Turbos and BlueMove v1. Searches both token orders and every Turbos fee tier. Each result reports the pool's own token order. Use get_pool_stats for reserves, fees and prices.

NameTypeReqDescription
networkstring–Network: 'mainnet' (default) | 'testnet' | 'devnet'
protocolstring–Filter by protocol: 'cetus', 'deepbook', 'turbos', or 'bluemove'. Searches all if omitted.
token_astringyesFirst token: symbol (e.g. 'SUI') or full coin type
token_bstringyesSecond token: symbol (e.g. 'USDC') or full coin type

No output schema declared.

No examples provided.

get_balance ~330

Read one coin's liquid balance for a Sui address or object, now or at a past time/checkpoint; the default coin is SUI. The total includes Coin<T> objects and address-balance funds, so no coin objects does not mean no funds. Only its defining module can withdraw an object's address balance. This excludes staking and DeFi positions: check get_staking_summary and get_defi_positions before assessing holdings; use get_wallet_overview for every coin. Historical reads are direct within the consistent range (about the last hour), reconstructed for older points and exact only when complete:true. Reconstruction stops at max_transactions; an incomplete result has balance:null and reached_checkpoint marks progress. Reconstructed coin_balance and address_balance are null; anchor has the split at its checkpoint.

NameTypeReqDescription
addressstring–Alias for `owner`.
atstring–ISO 8601 time: use the last checkpoint at or before it. Give this or at_checkpoint, not both.
at_checkpointinteger–Balance as of the end of this checkpoint. Give this or `at`, not both.
coin_typestring–Coin type (default: 0x2::sui::SUI)
max_transactionsinteger–Reconstruction transaction limit (default 1000, max 10000); ignored for current or consistent-range reads.
networkstring–Network: 'mainnet' (default) | 'testnet' | 'devnet'
ownerstring–Owner address (0x...). Required; `address` is accepted in its place.

No output schema declared.

No examples provided.

get_chain_info ~88

Get current Sui network info: chain ID, epoch, checkpoint height, timestamp, and reference gas price. Optionally pass an epoch number to get details for a specific epoch.

NameTypeReqDescription
epochstring–Epoch number to query. Returns current epoch info if omitted.
networkstring–Network: 'mainnet' (default) | 'testnet' | 'devnet'

No output schema declared.

No examples provided.

get_defi_positions ~191

Find and value a wallet's staked SUI with rewards, issuer-rate liquid-staking coins, CLMM/AMM liquidity, lending and balances inside owned objects. Positions include asset legs, valuation method and evidence tier; USD is null if any leg lacks a price, with unpriced_reason. Totals sum only priced positions. coverage lists unrecognised owned-object types and counts; unread lists failed reads. Lending includes protocol health ratios. leads flags near-borrow-limit positions and operated shared vaults with their holdings.

NameTypeReqDescription
addressstringyesWallet address (0x...)
detailstring–'summary' (default): highest-value positions fitting about 30k characters, plus all unpriced ones; omitted counts the rest. 'full': every position.
networkstring–Network: 'mainnet' (default) | 'testnet' | 'devnet'

No output schema declared.

No examples provided.

get_object ~201

Get a Sui object by its ID. Returns type, owner, version, content (JSON), and digest. Automatically extracts display metadata (name, description, image_url) for NFTs. For the LATEST version it also lists `address_balances` (funds the object holds in its own address balance, which are not among its fields and which only its defining module can withdraw) and, for a kiosk, `kiosk_cap_holder`: who actually controls it today, since `content.owner` is self-declared and not kept in sync with the KioskOwnerCap transfer that does. Neither is read for a specific `version`: both are current state and would misname a past snapshot's controller.

NameTypeReqDescription
networkstring–Network: 'mainnet' (default) | 'testnet' | 'devnet'
object_idstringyesThe object ID (0x...)
versionstring–Specific version to fetch

No output schema declared.

No examples provided.

get_staking_summary ~182

Get directly held StakedSui positions and principal, now or at as_of. Historical budget stops return a continuation; totals stay null until replay finishes. Excludes wrapped stakes and liquid-staking tokens.

NameTypeReqDescription
addressstringyesWallet address (0x...)
as_ofstring–ISO 8601 date or checkpoint string; holdings at the end of the last checkpoint at or before it.
continuationstring–Opaque historical replay state from continue_with; keep address, as_of and network unchanged.
detailstring–summary caps displayed positions; full returns every read position.
max_transactionsinteger–Historical replay budget per direction (default 1000); also bounds object-change pages.
networkstring–Network: 'mainnet' (default) | 'testnet' | 'devnet'

No output schema declared.

No examples provided.

get_token_prices ~192

Get USD prices for Sui coins by full coin type, current by default or at a past moment when `at` is set. Needs no API key. Each price names its source, confidence and sample time, and each coin that could not be priced is listed under `unpriced` with the reason. The 24h change is null when DefiLlama lacks the current or day-earlier price. An unverified coin is priced only by its exact coin type, never by a symbol-matched feed.

NameTypeReqDescription
atnumber|string–Price at this moment, as Unix seconds or ISO 8601. Omit for current prices.
coin_typesarrayyesFull coin type strings, e.g. ['0x2::sui::SUI'].
networkstring–Network: 'mainnet' (default) | 'testnet' | 'devnet'

No output schema declared.

No examples provided.

get_transaction ~513

Read one Sui transaction's sender, status, gas, balance changes, decoded actions and event fields; no hand-written GraphQL is needed to read event values. It identifies protocols from calls and events (including wrappers), and unnamed packages by their curated publishing key; protocols_unchecked marks unread publishers. It shows address-balance deposits and withdrawals, requested withdrawals and gas source; non-sender object deliveries (coins separately when no other object moved); sender-owned capabilities mutated without transfer; and router coin round trips with cost from pool events, or null with a reason. High-bit u256 event numbers get signed readings; full detail also gives two's-complement readings of high-bit u64/u128/u256 pure values. Use detail:'full' for inputs with declared types and object versions, resolved command arguments and Result origins, and every changed object's ID, type and version by kind. Summary may fold or cap event rows past ~20k chars, retaining events emitted by called non-framework packages; omitted reports reductions. Full detail lists all events in pages: follow events_page.next_call. For command-only or pre-sign inspection use decode_ptb; for exploit profit, state deltas and anomaly leads use analyze_attack_tx.

NameTypeReqDescription
commandsarray–Command indices to list with detail:'full', e.g. [3, 7], instead of the first page. Where attributable, events narrow to emitting calls and objects to commands taking them or returning their type; ev…
detailstring–'summary' (default): object counts, no inputs/commands; ~20k chars of deliveries/transfers/balance changes, prioritizing all capabilities and, for SUI/verified coins, sender changes and largest credi…
digeststringyesTransaction digest (Base58)
event_offsetinteger–Where the full-detail event page starts (after any commands narrowing); pages are ~40k chars and events_page.next_call carries the next offset.
max_event_field_bytesinteger–Decoded event-field byte cap; unset decodes every event. Set only to bound fields knowingly; skips are reported. 0 skips decoding.
networkstring–Network: 'mainnet' (default) | 'testnet' | 'devnet'

No output schema declared.

No examples provided.

get_transaction_history ~379

(Recommended for wallet activity) Read a wallet's decoded protocols, actions and coin flows; prefer this to query_transactions for exploring activity. Rows use complete balance changes and commands. Newest first by default; oldest starts at the first transaction. Pass next_cursor as cursor with the same order. address_poisoning always checks the shown page only, so empty pairs clear nothing older. subject_flow is the queried wallet's signed change per coin; token_flow is the sender's, omitted when they are the same address. Counterparties include at most 25 value recipients; counterparty_count reports larger sets. Summary keeps ~35k characters, preserving failed and lookalike-involved rows; omitted reports the rest and detail:'full' lists the whole page. signed_as_alias separately lists transactions signed as another wallet's address_alias delegate, which the main page cannot show. The delegate scan is cached for up to five minutes; alias_scan_as_of dates it and signed_as_alias_unavailable marks incomplete scans, even beside returned matches.

NameTypeReqDescription
addressstringyesSui wallet address (0x...)
cursorstring–`next_cursor` from the previous page. Continues in the same direction; pass the same `order`.
detailstring–'summary' (default) keeps ~35k chars in page order, always retaining failed and lookalike-involved rows; omitted reports the rest. 'full' lists every row of the page.
limitnumber–Number of transactions to return (default 10, max 50)
networkstring–Network: 'mainnet' (default) | 'testnet' | 'devnet'
orderstring–'newest' (default) pages backward from recent activity; 'oldest' pages forward from the first transaction.

No output schema declared.

No examples provided.

get_transactions ~196

Read 1-50 transaction digests in batched calls. Returns sender, status, timing, balance changes, non-coin object transfers and objects created for other owners, Move calls, decoded events and protocols. GraphQL misses are retried through the archive. object_changes_truncated marks an incomplete bounded object read; use get_transaction for that digest. Summary caps displayed rows with counts and omitted retrieval; detail: 'full' removes display caps, not object or event read bounds.

NameTypeReqDescription
detailstring–'summary' (default): events, calls, balances and object custody share about 30k characters across the batch. 'full': every fetched row, subject to read bounds.
digestsarrayyesTransaction digests, Base58 (1-50). Duplicates are collapsed.
networkstring–Network: 'mainnet' (default) | 'testnet' | 'devnet'

No output schema declared.

No examples provided.

get_wallet_overview ~328

(Recommended first tool for wallets) Overview of a Sui wallet: every coin balance, SuiNS name, staked SUI and kiosk counts, 50 newest transactions with an older-history continuation, and a time-bounded scan of package versions it published or upgraded in the first 20 sent transactions (`package_activity.scan.next_call` continues; `package_activity_next_call` retries if unavailable). include_prices adds USD values, coins ranked by value, and DeFi positions (staked SUI with rewards, liquid staking, liquidity, lending, and balances inside owned objects), each totalled apart. `coverage` says which owned objects the total covers and lists unrecognised types with counts; `leads` names lending positions near their borrow limit and shared vaults the wallet operates, with what they hold. include_nfts adds NFT estimates, kept out of the total.

NameTypeReqDescription
addressstringyesWallet address (0x...)
detailstring–'summary' (default): holdings and unrecognised object types that fit about 12k characters each, the rest in `omitted`. 'full': every row.
include_nftsboolean–With include_prices, also estimate held NFTs (default: false). Takes many requests on a wallet with many objects; list_nft_collections does this alone.
include_pricesboolean–Add USD values, DeFi positions, coverage and leads (default: false).
networkstring–Network: 'mainnet' (default) | 'testnet' | 'devnet'

No output schema declared.

No examples provided.

get_wallet_packages ~188

List package versions created by publish or upgrade transactions sent from this wallet address. Scans 20 sent transactions per call, oldest first; `scan.complete` is true only when all pages and transactions were read. `scan.next_call` continues with an opaque cursor that carries prior unread counts. `scan.incomplete_transactions` names unread digests on this page and `scan.prior_incomplete_transactions` counts them on earlier pages. Each package carries its creating transaction, lineage root and version; an alias may have signed for the sender, and the sender is not necessarily the current UpgradeCap holder.

NameTypeReqDescription
addressstringyesWallet address (0x...)
cursorstring–Opaque cursor from scan.next_call, to scan the next 20 sent transactions.
networkstring–Network: 'mainnet' (default) | 'testnet' | 'devnet'

No output schema declared.

No examples provided.

identify_address ~229

(Recommended first step) Classify a Sui address as wallet, package, validator or object before choosing other tools. A wallet includes package_activity: publish/upgrade transactions it sent in the first 20 sent transactions, with next_call to continue the scan. It adds contextual balance/name, module or stake information. Packages can be identified from bridge labels on their defined objects; bridge_carrier identifies bytecode calls into curated bridge exits. A wallet's first_seen is the oldest transaction GraphQL returns where it sent or was affected, with received coins read across all balance-change pages. first_inflow means it gained coins without sending, including genesis with sender:null; genesis names no funding wallet. If no gain is found in incomplete changes, first_inflow is null. first_seen_unavailable means the first read failed. Use find_funding_sources when the first transaction was only a token airdrop.

NameTypeReqDescription
addressstringyesSui address or object ID (0x...)
networkstring–Network: 'mainnet' (default) | 'testnet' | 'devnet'

No output schema declared.

No examples provided.

list_nft_collections ~260

Summary of the NFT collections a wallet holds: every kiosk plus directly owned objects, one row per collection type with its count. Each collection carries an estimated value (tier heuristic): per item, the lower of the collection's lowest active listing and its last sale in the 30 days before now, or whichever of the two exists (a listing alone only if placed in that window), with zero-price sales, sales within one address or kiosk, and sales where one side first funded the other left out; unpriced otherwise. `estimated_value` totals every collection; the default view keeps every priced collection and caps the rest, and `detail: 'full'` returns all rows. `value: false` skips the valuation.

NameTypeReqDescription
addressstringyesOwner wallet address (0x...)
detailstring–'summary' (default): priced collections, then the most-held others that fit; `omitted` counts the rest. 'full': every collection.
networkstring–Network: 'mainnet' (default) | 'testnet' | 'devnet'
valueboolean–Estimate each collection's value from its market (default true). Costs a few requests per collection that has a market.

No output schema declared.

No examples provided.

list_nfts ~289

(Recommended for NFTs) List NFTs owned by a wallet, including kiosk-stored NFTs. Each row has an object id, `collection_ref` (zero-based index into this page's exact `collection_types`), kiosk and display metadata. `detail: 'full'` adds raw Move contents and valuation evidence. `est_usd` is a heuristic NFT estimate; other valued objects carry `value_usd` and a tier. `value: false` skips valuation. Pass `next_cursor` as `cursor` for the next page; its absence means the wallet is fully enumerated. Use list_nft_collections for a per-collection summary and wallet total.

NameTypeReqDescription
addressstringyesOwner wallet address (0x...)
cursorstring–Opaque pagination token from a prior response's `next_cursor`. Omit on first call.
detailstring–'summary' (default) leaves out raw contents and valuation evidence, counted in `omitted`. 'full' includes both.
limitinteger–Most NFTs to return (default 50, max 1000).
networkstring–Network: 'mainnet' (default) | 'testnet' | 'devnet'
valueboolean–Estimate each NFT's value from its collection's market (default true). Costs a few requests per collection on the page.

No output schema declared.

No examples provided.

list_owned_objects ~281

List raw objects owned by a Sui address with optional type filter and pagination. `count` covers every object of the page; the default view lists the objects that fit about 30k characters in page order and states the rest under `omitted`, and `detail: 'full'` lists the whole page. `next_cursor` continues after the whole page, rows under `omitted` included. For NFTs specifically, prefer list_nfts (resolves kiosk storage, extracts display metadata). For a wallet summary, prefer get_wallet_overview.

NameTypeReqDescription
addressstring–Alias for `owner`.
cursorstring–Pagination cursor from previous response
detailstring–'summary' (default): the page's objects that fit about 30k characters, the rest in `omitted`. 'full': the whole page.
limitinteger–Max results (default 50, max 1000)
networkstring–Network: 'mainnet' (default) | 'testnet' | 'devnet'
object_typestring–Filter by object type (e.g. 0x2::coin::Coin<0x2::sui::SUI>)
ownerstring–Owner address (0x...). Required; `address` is accepted in its place.

No output schema declared.

No examples provided.

query_transactions ~527

Query raw transactions by sender, affected address or object, Move function, or time/checkpoint range. Only one of affected_address, affected_object and function is allowed. Prefer get_transaction_history for readable wallet activity. Pages default to newest first and report order, timestamp bounds and resolved window; pass next_cursor as cursor with the same order and filters. Short service pages are filled to limit within a read budget; scan reports exhaustion and the continuation call. Continue while has_next_page, even with no transactions. A function filter covers only the named package version; function_scope names other versions and all_versions:true merges the whole lineage. Rows wait for each stream's next rows or exhaustion to establish global order. It matches any PTB containing the call, even one leg among several protocols. Whole-PTB balance changes therefore over-attribute protocol volume. Use include_functions to inspect every Move call, and query_events for a protocol's own flow.

NameTypeReqDescription
affected_addressstring–Filter by affected address (sender, sponsor, or recipient). Mutually exclusive with affected_object and function.
affected_objectstring–Filter by affected object ID. Mutually exclusive with affected_address and function.
after_checkpointstring|number–Transactions after this checkpoint number (exclusive), or at/after this ISO 8601 time (inclusive).
all_versionsboolean–With function, merge calls through all lineage versions (default false: named version only).
before_checkpointstring|number–Transactions before this checkpoint number (exclusive), or at/before this ISO 8601 time (inclusive).
cursorstring–`next_cursor` from the previous page. Pass the same `order` and filters.
functionstring–Filter by Move function (e.g. 0x2::coin::transfer or 0x2::pay). Mutually exclusive with affected_address and affected_object.
include_functionsboolean–List every Move call to expose multi-protocol PTBs. With function, adds total_calls and matched_calls at the filter's function/module/package granularity, for the named version or all_versions.
limitinteger–Max results (default 20, max 50)
networkstring–Network: 'mainnet' (default) | 'testnet' | 'devnet'
orderstring–'newest' (default) starts at the most recent match and pages back; 'oldest' starts at the earliest and pages forward.
senderstring–Filter by sender address

No output schema declared.

No examples provided.

resolve_name ~247

Resolve a SuiNS name (.sui domain) to an address, or reverse-lookup an address to its SuiNS name. At least one of 'name' or 'address' must be provided. A name that is not registered, has expired, or points at no address resolves to null with `name_note` saying which; a malformed name is an error. IDENTITY WARNING: a SuiNS name is a self-chosen handle that anyone can buy. It is not identity and it is not verified. Names matching an exchange, a project or a person can be, and are, registered by unrelated parties, including by someone who wants an investigator to draw a particular conclusion. Treat a name as a label the holder picked, never as evidence of who they are, and do not carry it to other platforms as a matching key without independent corroboration.

NameTypeReqDescription
addressstring–Address to reverse-lookup to a SuiNS name
namestring–SuiNS name to resolve (e.g. 'example.sui')
networkstring–Network: 'mainnet' (default) | 'testnet' | 'devnet'

No output schema declared.

No examples provided.

Install

How do I install the Sui Analytics MCP server?

Sui Analytics runs locally as an npm package, launched with npx -y sui-analytics-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · sui-analytics-mcp

# add to Claude Code
claude mcp add 0xfreak0-sui-mcp -- npx -y sui-analytics-mcp
Common questions

What is the Sui Analytics MCP server?

Sui Analytics is an MCP server listed in the public MCP registry as io.github.0xfreak0/sui-mcp. Read-only Sui analytics: fund tracing, protocol-aware tx decoding, no API keys or wallet. This page covers its npm package (sui-analytics-mcp).

Is the Sui Analytics MCP server safe to use?

Sui Analytics scores 91 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Sui Analytics MCP server expose?

Sui Analytics exposes 20 tools: get_chain_info, get_object, list_owned_objects, get_balance, get_transaction, and 15 more. Their descriptions and schemas cost roughly 5,456 tokens of context every time the server is loaded.

Is the Sui Analytics MCP server still maintained?

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

What licence is the Sui Analytics MCP server under?

Sui Analytics declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.