tide

ad.tide/mcptide.adstreamable-httpv2.0.0Scanned 1 hour ago

Sui blockchain data in plain English: transactions, wallets, coins, balances, fund flows and SQL.

22 tools: 2 do something that can't be undone, 12 change things and 8 only read.

Reads private data · 2
Reads text others write · 0
Can send data out · 2
5 findings

Anlyon alternative

14 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

22 tools

Can't be undone 2Sends, pays, publishes or merges: once done, it cannot be taken back.Claude Code: ask

candlesOHLCV price candles for a coin, in USD.Can send data out1 finding
Why it is in this group
- The input addresses people (input.to): what it sends cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Findings
- Warn
  The server marks "candles" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
  Matched text
  annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.
  What this check looks for
Description, as the server wrote it
OHLCV price candles for a coin, in USD. Pick interval and an optional from and to. Example: { coin: "SUI", interval: "1h" }.
Annotations the server declares
- title: Price candles
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
wallet_historyA wallet's transactions since genesis, newest first, each as one decoded sentence with the coins in and out.Can send data out1 finding
Why it is in this group
- The input addresses people (input.to): what it sends cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Findings
- Warn
  The server marks "wallet_history" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
  Matched text
  annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.
  What this check looks for
Description, as the server wrote it
A wallet's transactions since genesis, newest first, each as one decoded sentence with the coins in and out. Filter by coin, direction (in or out) and days. Page with cursor. Spam airdrops are left out. Example: { address: "0x...", limit: 10 }.
Annotations the server declares
- title: A wallet's transactions
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false

Changes things 12Creates or changes something that can be changed back.Claude Code: ask

address_kindTell what an address is: a plain key (ed25519, secp256k1, secp256r1), a passkey, a zkLogin address (with its provider), a multisig (members and threshold), an object, a package, or…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it
Tell what an address is: a plain key (ed25519, secp256k1, secp256r1), a passkey, a zkLogin address (with its provider), a multisig (members and threshold), an object, a package, or an address that never signed. Example: { address: "0x..." }.
Annotations the server declares
- title: What kind of address
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
balance_atThe exact balance a wallet held at a past time or checkpoint, read from full history.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it
The exact balance a wallet held at a past time or checkpoint, read from full history. With coin, that coin's balance and the transaction that last changed it. Without coin, every coin it held then, valued at that time's prices. Example: { address: "example.sui", coin: "SUI", time: "2025-06-01T00:00:00Z" }.
Annotations the server declares
- title: Balance at a past time
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
checkpointOne checkpoint by sequence number, or the newest with seq "latest": time, epoch, gas totals and its transactions as one-line sentences.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it
One checkpoint by sequence number, or the newest with seq "latest": time, epoch, gas totals and its transactions as one-line sentences. Use it to see what is happening on chain right now. Example: { seq: "latest" }.
Annotations the server declares
- title: Read a checkpoint
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
nftsThe NFTs and kiosk items an address owns: name, collection, image and listing state.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it
The NFTs and kiosk items an address owns: name, collection, image and listing state. Page with cursor. Example: { address: "example.sui" }.
Annotations the server declares
- title: NFTs a wallet owns
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
order_bookDeepBook order books.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it
DeepBook order books. With nothing: every pool with best bid, ask and 24h volume. With pool: its depth and latest trades. With address: the wallet's open orders and recent fills. Example: { pool: "0x..." }.
Annotations the server declares
- title: DeepBook order books
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
package_infoA Move package.1 finding
Why it is in this group
- The description's first verb is "move": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
  The server marks "package_info" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
  Matched text
  annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "move": a word for a change.
  What this check looks for
Description, as the server wrote it
A Move package. With only id: its modules, functions and upgrade history. With module and function: how to call it, each parameter explained, with a TypeScript snippet. With window (24h, 7d or 30d): calls per day and per function, failures and top callers. Example: { id: "0x2", module: "coin", function: "split" }.
Annotations the server declares
- title: Read a Move package
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
priceUSD prices for up to 50 coins, now or at a past time.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it
USD prices for up to 50 coins, now or at a past time. Pass coin types or symbols. Example: { coins: ["SUI", "DEEP"] }.
Annotations the server declares
- title: Coin prices
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
sqlRun one SQL SELECT over every Sui transaction, event, object version and balance change since genesis.1 finding
Why it is in this group
- The description's first verb is "run": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
  The server marks "sql" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
  Matched text
  annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "run": a word for a change.
  What this check looks for
Description, as the server wrote it
Run one SQL SELECT over every Sui transaction, event, object version and balance change since genesis. Needs an API key. Returns up to 100 rows; page with execution_id and offset. If it is still running, call again with execution_id. Tables and columns: https://api.tide.ad/v1/sql/schema. Example: { query: "SELECT sequence_number, total_transaction_blocks FROM sui.checkpoints ORDER BY sequence_number DESC LIMIT 5" }. Needs an API key.
Annotations the server declares
- title: Run SQL over all of Sui
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
stakingWith address: the wallet's staked SUI, per stake its validator, principal, rewards and status.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it
With address: the wallet's staked SUI, per stake its validator, principal, rewards and status. With validator: that validator's stake, commission and APY per epoch. Example: { address: "example.sui" }.
Annotations the server declares
- title: Stakes and validators
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
token_infoA coin's price, market cap, liquidity, volume and holder count, its safety checks (mint authority, deny list, concentration), its top 10 holders with linked-wallet clusters, and a …No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it
A coin's price, market cap, liquidity, volume and holder count, its safety checks (mint authority, deny list, concentration), its top 10 holders with linked-wallet clusters, and a report on its creator's past launches. Use it to judge a coin. Example: { coin: "DEEP" }.
Annotations the server declares
- title: Check a coin
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
trace_fundsFollow money between addresses.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it
Follow money between addresses. direction in: who sent funds to this address, hop by hop back, plus who first funded it. out: where its funds went, hop by hop forward. both: its largest counterparties either way. Exchanges and protocols end a path. Returns the 15 largest flows. Example: { address: "0x...", direction: "in", depth: 2 }.
Annotations the server declares
- title: Trace where money came from or went
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
wallet_profileEverything about a wallet in one call: total value with price status, top coins, DeFi and launchpad positions, SuiNS names and labels, who first funded it, its trading record and i…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it
Everything about a wallet in one call: total value with price status, top coins, DeFi and launchpad positions, SuiNS names and labels, who first funded it, its trading record and its latest transactions. Use it first for any question about an address or a .sui name. Example: { address: "example.sui" }.
Annotations the server declares
- title: Profile a wallet
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false

Only reads 8Looks things up and changes nothing.Show 8 read-only tools

docsSearch the tide API docs for the method that answers a question, with its parameters, credits and a curl example.Reads private dataNo findings
Why it is in this group
- The description's first verb is "search": a word for reading.
What it can reach
- private-dataThe name "docs" says "doc": it reads documents.
- private-dataThe description's first sentence says "search" and "doc": it reads documents.
Description, as the server wrote it
Search the tide API docs for the method that answers a question, with its parameters, credits and a curl example. Use it when no other tool fits; then call the method over REST at https://api.tide.ad. Example: { question: "transfers of a coin between two times" }.
Annotations the server declares
- title: Find the right tide API method
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
eventsList on-chain events by Move event type or by package, newest first, with an optional time or checkpoint range.No findings
Why it is in this group
- The description's first verb is "list": a word for reading.
Description, as the server wrote it
List on-chain events by Move event type or by package, newest first, with an optional time or checkpoint range. Page with cursor. Example: { type: "0x...::pool::SwapEvent", limit: 10 }.
Annotations the server declares
- title: List events
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
explain_transactionExplain one Sui transaction in plain English: what happened, the steps, who gained or lost which coins (with USD), the fee and the status.1 finding
Why it is in this group
- The name "explain_transaction" says "explain": a word for reading.
Findings
- Warn
  The description contains a 44-character base64 string.
  Matched text
  description: "...Example: { digest: "5ajkuHAnivMiKRne6EYS2bzvHpCHWYx849cmoSHN89Vm" }."
  What this check looks for
Description, as the server wrote it
Explain one Sui transaction in plain English: what happened, the steps, who gained or lost which coins (with USD), the fee and the status. Use it whenever you have a transaction digest. Example: { digest: "5ajkuHAnivMiKRne6EYS2bzvHpCHWYx849cmoSHN89Vm" }.
Annotations the server declares
- title: Explain a transaction
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
explain_unsignedCheck a Sui transaction before signing it: tide simulates it, explains what it would do in plain words, and checks every recipient, coin and package against full history.No findings
Why it is in this group
- The name "explain_unsigned" says "explain": a word for reading.
Description, as the server wrote it
Check a Sui transaction before signing it: tide simulates it, explains what it would do in plain words, and checks every recipient, coin and package against full history. Returns safe, caution or danger with findings and evidence links. Block on danger. Pass tx_bytes (base64 TransactionData, or TransactionKind bytes with sender). Example: { tx_bytes: "AAAC..." }.
Annotations the server declares
- title: Check a transaction before signing
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_objectRead any Sui object by id: type, owner, version and fields, with its recent change history (which transactions changed it).No findings
Why it is in this group
- The name "get_object" says "get": a word for reading.
Description, as the server wrote it
Read any Sui object by id: type, owner, version and fields, with its recent change history (which transactions changed it). Example: { id: "0x..." }.
Annotations the server declares
- title: Read an object
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_object_atRead a Sui object as it was at a version, checkpoint or time: its fields and owner then, or whether it was deleted or wrapped.No findings
Why it is in this group
- The name "get_object_at" says "get": a word for reading.
Description, as the server wrote it
Read a Sui object as it was at a version, checkpoint or time: its fields and owner then, or whether it was deleted or wrapped. Use it for what a pool, vault or position looked like before a change. Example: { id: "0x...", time: "2026-10-30T00:00:00Z" }.
Annotations the server declares
- title: Read an object at a past time
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
object_childrenList the dynamic fields of an object with decoded names and values (tables, bags, kiosks, pools, registries), or with depth 1 to 3, its tree of children.Reads private dataNo findings
Why it is in this group
- The description's first verb is "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "table": it reads databases.
Description, as the server wrote it
List the dynamic fields of an object with decoded names and values (tables, bags, kiosks, pools, registries), or with depth 1 to 3, its tree of children. Page with cursor. Example: { id: "0x..." }.
Annotations the server declares
- title: List an object's dynamic fields
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
searchFind anything on Sui by text: coins by symbol or name, SuiNS names, perps markets, pools, packages, addresses, objects and digests.No findings
Why it is in this group
- The name "search" says "search": a word for reading.
Description, as the server wrote it
Find anything on Sui by text: coins by symbol or name, SuiNS names, perps markets, pools, packages, addresses, objects and digests. Returns ids to pass to the other tools. Example: { query: "deep" }.
Annotations the server declares
- title: Search Sui
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input.

Reads private data2: Reads files, mail, messages, databases, secrets, calendars or repositories.; docs
object_children
Reads text others write0: Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2: Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.; candles
wallet_history

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Findings

Matches of fixed checks, with the text they matched.

5 warn

Warnexplain_transaction
The description contains a 44-character base64 string.
Matched text
description: "...Example: { digest: "5ajkuHAnivMiKRne6EYS2bzvHpCHWYx849cmoSHN89Vm" }."
What this check looks for
Warnwallet_history
The server marks "wallet_history" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
Matched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.
What this check looks for
Warnsql
The server marks "sql" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
Matched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "run": a word for a change.
What this check looks for
Warnpackage_info
The server marks "package_info" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
Matched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "move": a word for a change.
What this check looks for
Warncandles
The server marks "candles" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
Matched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.
What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

All changes to this server

Install

Pinned to version 2.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http tide https://api.tide.ad/mcp

claude mcp add --transport http tide https://api.tide.ad/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json

{
  "permissions": {
    "allow": [
      "mcp__tide__explain_transaction",
      "mcp__tide__search",
      "mcp__tide__explain_unsigned",
      "mcp__tide__get_object",
      "mcp__tide__get_object_at",
      "mcp__tide__object_children",
      "mcp__tide__events",
      "mcp__tide__docs"
    ],
    "ask": [
      "mcp__tide__wallet_profile",
      "mcp__tide__wallet_history",
      "mcp__tide__balance_at",
      "mcp__tide__token_info",
      "mcp__tide__trace_funds",
      "mcp__tide__price",
      "mcp__tide__sql",
      "mcp__tide__package_info",
      "mcp__tide__checkpoint",
      "mcp__tide__candles",
      "mcp__tide__nfts",
      "mcp__tide__staking",
      "mcp__tide__order_book",
      "mcp__tide__address_kind"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as tide. Review it before you use it.

Capability tags behind 4 rules

mcp__tide__wallet_history outbound
mcp__tide__object_children private-data
mcp__tide__candles outbound
mcp__tide__docs private-data

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://anlyon.dev/api/v1/servers/ad.tide/mcp/verify?hash=2e7d0796cc788f6fc7ddac176b1139d668d01d794b1f143fb2f66716e179d604" | jq -e '.changed == false'

Pinned hash 2e7d0796cc78, from Nov 4, 2026, 07:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/ad.tide/mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

[![anlyon.dev](https://anlyon.dev/badge/ad.tide/mcp.svg)](https://anlyon.dev/servers/ad.tide/mcp)

Source: MCP Registry. Synced Nov 4, 2026, 07:17 UTC.