tide MCP server
ad.tide/mcptide.adstreamable-httpv2.0.0Scanned
Sui blockchain data in plain English: transactions, wallets, coins, balances, fund flows and SQL.
38 tools: 5 do something that can't be undone, 24 change things and 9 only read.
- Reads private data · 2
- Reads text others write · 0
- Can send data out · 4
- 8 findings
Tools listed without sign-in. Remote posture
With Anlyon
5 tools here do something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the tide MCP server can do
The tide MCP server is published by tide.ad, a domain the MCP Registry verified. It has 38 tools. It can do things that cannot be undone, such as sending, paying or publishing (wallet_history, build_transaction, withdraw_plan, billing_topup and 1 more) and create or change data (24 tools: wallet_profile, balance_at, token_info, trace_funds and 20 more), but cannot delete data. 9 tools only read.
2 tools read private data (object_children and docs); 4 tools can send data out of your system (wallet_history, build_transaction, withdraw_plan and 1 more).
The fixed checks matched 8 findings (base64-blob and annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 17, 2026, version 2.0.0.
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.
38 tools
Can't be undone 5Claude Code: ask
billing_topupBuild an unsigned transaction that pays USDC on Sui to tide's treasury for credits ($3 per million credits; 1 USDC buys 333,333).1 finding
Why it is in this group
- The name "billing_topup" says "topup": a word that usually means money moves, which cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "billing_topup" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "billing_topup" says "topup": a word that usually means money moves, which cannot be taken back.
Description, as the server wrote it Build an unsigned transaction that pays USDC on Sui to tide's treasury for credits ($3 per million credits; 1 USDC buys 333,333). Returns base64 tx_bytes that need no SUI for gas (unless gas: true). Sign them with the paying address and send them, or POST them with the signature to https://api.tide.ad/v1/billing/topup/submit. Credits land on the paying address's account about a second after the transaction is final. With an API key the key's account pays; without one pass address. Free. Example: { usd: "10" }.
Annotations the server declares
- title: Buy credits with USDC
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
build_transactionBuild an unsigned Sui transaction for an action and get it back already checked: tide adds the protocol's own calls, picks the sender's gas coins, sets the budget, dry-runs the exa…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 "build_transaction" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.
Description, as the server wrote it Build an unsigned Sui transaction for an action and get it back already checked: tide adds the protocol's own calls, picks the sender's gas coins, sets the budget, dry-runs the exact bytes on current mainnet state and runs the pre-sign check. Returns tx_bytes, a plain description, what leaves and enters the wallet, gas and the verdict. If it would fail or the check says danger you get the reason and no bytes. Amounts are whole coins. Actions: stake {amount, validator}; unstake {staked_sui_id, validator, amount}; lst_mint {lst, amount}; lst_redeem {lst, amount}; swap {from, to, amount, slippage_pct}; supply {protocol, asset, amount}; withdraw {protocol, asset, amount}. Lending protocols: suilend, navi, scallop. Swaps use the Aftermath router with slippage_pct (default 0.5) enforced on chain. steps runs several actions in one transaction; a step without amount takes the previous output. tide never signs: sign tx_bytes with your own wallet. Example: { sender: "0x...", action: "supply", protocol: "navi", asset: "USDC", amount: 100 }.
Annotations the server declares
- title: Build a transaction to sign
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
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".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.
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".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.
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
withdraw_planList a wallet's staking, liquid staking and lending positions (native stakes, afSUI, haSUI, vSUI, sSUI, stSUI, Suilend, NAVI, Scallop), each with an id and the step that exits it, …Can send data out1 finding
Why it is in this group
- The name "withdraw_plan" says "withdraw": a word that usually means money moves, which cannot be taken back.
- 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 "withdraw_plan" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "withdraw_plan" says "withdraw": a word that usually means money moves, which cannot be taken back.
Description, as the server wrote it List a wallet's staking, liquid staking and lending positions (native stakes, afSUI, haSUI, vSUI, sSUI, stSUI, Suilend, NAVI, Scallop), each with an id and the step that exits it, and with exit build the exit transactions: unsigned, gassed and checked on current mainnet state, or the reason one would fail. to swaps the proceeds into one coin in the same transaction. Example: { wallet: "0x...", exit: "all", to: "USDC" }.
Annotations the server declares
- title: Exit a wallet's positions
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Changes things 24Claude 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
agent_pass_precheckBefore building: check one action against an Agent Pass's rules as they stand now (active, signer is the agent, rule for the coin or pair, per-action and daily limits, listed pools…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 Before building: check one action against an Agent Pass's rules as they stand now (active, signer is the agent, rule for the coin or pair, per-action and daily limits, listed pools, price floor, named recipient, budget left). Returns accept or the rule that would refuse it. Example: { pass: "0x03c7...7bac", step: { action: "swap", coin_in: "USDC", coin_out: "SUI", amount: "0.2" } }.
Annotations the server declares
- title: Will the pass accept this?
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
agent_pass_reportA report for a human on Agent Pass (Sui's on-chain agent authorization): for an owner, an agent or one pass, each pass's status, its rules in plain words (pools, caps, price floor,…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 report for a human on Agent Pass (Sui's on-chain agent authorization): for an owner, an agent or one pass, each pass's status, its rules in plain words (pools, caps, price floor, recipients), budgets left, today's usage and every transaction signed under it, including what Sui refused and why. Example: { owner: "0x1eb7...e0b1" } or { pass: "0x03c7...7bac" }.
Annotations the server declares
- title: What agents did under Agent Passes
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
agent_walletIs this address an AI agent, who does it act for and under what limits (Agent Pass, sui::allowance, Sui Agent Payments grant, t2000, Talus), how much of each limit is used, who pay…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 Is this address an AI agent, who does it act for and under what limits (Agent Pass, sui::allowance, Sui Agent Payments grant, t2000, Talus), how much of each limit is used, who pays its gas, and what it did lately in plain English. Example: { address: "0xb569f5371380e339038c0cdce2729621d36bfc89e740c28e3976bf04357edab6" }.
Annotations the server declares
- title: One AI agent wallet
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
agents_overviewThe agent world on Sui: agent wallets active in 24 hours, their transactions and volume, Agent Passes, sui::allowance spend, Sui Agent Payments (testnet, mainnet when live), gasles…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 agent world on Sui: agent wallets active in 24 hours, their transactions and volume, Agent Passes, sui::allowance spend, Sui Agent Payments (testnet, mainnet when live), gasless and sponsored transactions, every agent product with its status (mainnet, testnet, announced), the latest agent actions in plain English and the most active agents this week. Example: {}.
Annotations the server declares
- title: What AI agents do on Sui now
- 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
confirm_executionAfter execution: give the executed digest and the receipt (its id, or the receipt object).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 After execution: give the executed digest and the receipt (its id, or the receipt object). tide reads the transaction from the chain and compares status, balance changes, objects and events with the receipt. Returns match, or each difference in one plain sentence to report to your human (also not_executed, or other_transaction when the signed bytes were not the receipt's). Example: { digest: "CRDt...", receipt: "8e56072be767fadb73a18169d8dcfc3c" }.
Annotations the server declares
- title: Did it do what the receipt said?
- 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
owner_agentsThe AI agents one address runs on Sui: Agent Passes, allowances it granted, Sui Agent Payments grants, t2000 wallets it funded and agent wallets it pays gas for; per agent the limi…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 AI agents one address runs on Sui: Agent Passes, allowances it granted, Sui Agent Payments grants, t2000 wallets it funded and agent wallets it pays gas for; per agent the limits in words, how much is used, payments refused on chain, and their latest actions. Example: { address: "adeniyi.sui" }.
Annotations the server declares
- title: Agents an address runs
- 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".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "move": a word for a change.
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
perp_marketOne perpetual futures market on Sui (Aftermath, Bluefin or Parchment): mark and index price, 24h change and volume, open interest, funding (last, estimated next, when), max leverag…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 perpetual futures market on Sui (Aftermath, Bluefin or Parchment): mark and index price, 24h change and volume, open interest, funding (last, estimated next, when), max leverage, fees, the latest trades and pools it backs. Pass a symbol; venue is optional (the busiest market wins). Example: { market: "BTC", venue: "aftermath" }.
Annotations the server declares
- title: A perps market
- 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
receipt_for_transactionBefore you sign: send the exact unsigned bytes and your intent; tide dry-runs them on mainnet and returns a receipt signed by tide (ed25519) with the digest Sui will give them, eve…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 Before you sign: send the exact unsigned bytes and your intent; tide dry-runs them on mainnet and returns a receipt signed by tide (ed25519) with the digest Sui will give them, every simulated balance change, object and event, what Sui itself enforces (Agent Pass caps, listed pools, price floor, budget), checks of your intent (max_spend, min_receive, nothing else leaves the wallet) and a verdict. Give your human the url. After sending, call confirm_execution. Example: { tx_bytes: "AAAC...", intent: { action: "swap", max_spend: { USDC: "5" }, min_receive: { SUI: "4.9" } } }.
Annotations the server declares
- title: Signed receipt before signing
- 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".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "run": a word for a change.
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
verify_receiptCheck a receipt's ed25519 signature against tide's published key (https://api.tide.ad/.well-known/tide-attest.json), that its id matches its content, and that its digest is the bla…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 Check a receipt's ed25519 signature against tide's published key (https://api.tide.ad/.well-known/tide-attest.json), that its id matches its content, and that its digest is the blake2b digest of the bytes inside it. Pass the receipt id or the receipt object with its signature. Example: { receipt: "8e56072be767fadb73a18169d8dcfc3c" }.
Annotations the server declares
- title: Verify a tide receipt
- 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
walrus_blobEverything about one Walrus blob: status (registered, certified, expired, deleted), owner and uploader, size, the register and certify transactions, start and end epoch with an est…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 one Walrus blob: status (registered, certified, expired, deleted), owner and uploader, size, the register and certify transactions, start and end epoch with an estimated end date, deletable or permanent, shared blob funds, extensions, WAL paid, attributes, and what the content is (image, video, audio, pdf, json, markdown, csv, code, text, html, quilt with its patches, Seal encrypted with its policy package, binary), with a preview URL. Takes a blob id, a quilt patch id, the u256 or a Blob object id. Example: { id: "FHQl1gK7Rb5X5X3Q-DiNe4qvyTojL262p0JUn-ijQkQ" }.
Annotations the server declares
- title: Read a Walrus blob
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
yield_optionsEvery place on Sui to earn yield (lending, pools, liquid staking, native staking) with the APY each actually paid over 7 and 30 days, deposits, exit liquidity and a risk tier from …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 Every place on Sui to earn yield (lending, pools, liquid staking, native staking) with the APY each actually paid over 7 and 30 days, deposits, exit liquidity and a risk tier from 1 (lowest) to 5 with reasons. Filter by asset, kind, protocol, max_tier, min_apy; sort by tvl, apy, tier or exit. Example: { asset: "USDC", max_tier: 2, sort: "apy" }.
Annotations the server declares
- title: Where to earn yield on Sui
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
yield_planA ranked menu of 3 to 6 yield options on Sui for an amount: the realized APY used (never the advertised one), expected USD over the horizon, cost to get in and out at that size, ri…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 ranked menu of 3 to 6 yield options on Sui for an amount: the realized APY used (never the advertised one), expected USD over the horizon, cost to get in and out at that size, risk tier with reasons, plain steps and links. Ranks options that reach target_apy first, then lowest risk. With build: true and sender it also returns the unsigned transaction for the top option, already dry-run and checked, ready for the wallet to sign. Example: { amount_usd: 5000, asset: "USDC", target_apy: 6, max_risk_tier: 2, build: true, sender: "0x..." }.
Annotations the server declares
- title: Plan where to put an amount
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 9Show 9 read-only tools
billing_statusYour credits: what the plan has left this month, prepaid credits bought with USDC, the rate ($3 per million credits, so 1 USDC buys 333,333 credits), auto top-up settings and the l…No findings
Why it is in this group
- The name "billing_status" says "status": a word for reading.
Description, as the server wrote it Your credits: what the plan has left this month, prepaid credits bought with USDC, the rate ($3 per million credits, so 1 USDC buys 333,333 credits), auto top-up settings and the latest payments. Needs an API key. Free. Example: {}. Needs an API key.
Annotations the server declares
- title: Credits left and USDC top-ups
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
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.
What this check looks forMatched text
description: "...Example: { digest: "5ajkuHAnivMiKRne6EYS2bzvHpCHWYx849cmoSHN89Vm" }."
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.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out4
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 19, 2026, 17:22 UTC, unchanged since Nov 5, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 29
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 29 tools that change things (5 irreversible, 24 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.tide.ad/mcp: tools/list returned 38 tools to an anonymous client, including wallet_history (irreversible), build_transaction (irreversible), withdraw_plan (irreversible), billing_topup (irreversible), candles (irreversible) and 24 more
Findings
Matches of fixed checks, with the text they matched.
The description contains a 44-character base64 string.
What this check looks forMatched text
description: "...Example: { digest: "5ajkuHAnivMiKRne6EYS2bzvHpCHWYx849cmoSHN89Vm" }."
- Warnwallet_history
The server marks "wallet_history" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.
- Warnsql
The server marks "sql" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "run": a word for a change.
The server marks "build_transaction" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.
- Warnwithdraw_plan
The server marks "withdraw_plan" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "withdraw_plan" says "withdraw": a word that usually means money moves, which cannot be taken back.
- Warnbilling_topup
The server marks "billing_topup" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "billing_topup" says "topup": a word that usually means money moves, which cannot be taken back.
Show 2 more findingsShow fewer
- Warnpackage_info
The server marks "package_info" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "move": a word for a change.
- Warncandles
The server marks "candles" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools16 added.+16 addedView diff
- Added:agent_pass_precheckChanges things
- Added:agent_pass_reportChanges things
- Added:agent_walletChanges things
- Added:agents_overviewChanges things
- Added:billing_statusOnly reads
- Added:billing_topupCan't be undone
- Added:build_transactionCan't be undone
- Added:confirm_executionChanges things
- Added:owner_agentsChanges things
- Added:perp_marketChanges things
- Added:receipt_for_transactionChanges things
- Added:verify_receiptChanges things
- Added:walrus_blobChanges things
- Added:withdraw_planCan't be undone
- Added:yield_optionsChanges things
- Added:yield_planChanges things
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/mcpclaude mcp add --transport http tide https://api.tide.ad/mcpRun 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.
{
"permissions": {
"allow": [
"mcp__tide__explain_transaction",
"mcp__tide__search",
"mcp__tide__explain_unsigned",
"mcp__tide__billing_status",
"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__perp_market",
"mcp__tide__price",
"mcp__tide__sql",
"mcp__tide__yield_options",
"mcp__tide__yield_plan",
"mcp__tide__build_transaction",
"mcp__tide__withdraw_plan",
"mcp__tide__receipt_for_transaction",
"mcp__tide__confirm_execution",
"mcp__tide__verify_receipt",
"mcp__tide__agent_pass_report",
"mcp__tide__agent_pass_precheck",
"mcp__tide__agents_overview",
"mcp__tide__agent_wallet",
"mcp__tide__owner_agents",
"mcp__tide__billing_topup",
"mcp__tide__package_info",
"mcp__tide__checkpoint",
"mcp__tide__candles",
"mcp__tide__nfts",
"mcp__tide__staking",
"mcp__tide__order_book",
"mcp__tide__walrus_blob",
"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 6 rules
- mcp__tide__wallet_history outbound
- mcp__tide__build_transaction outbound
- mcp__tide__withdraw_plan outbound
- mcp__tide__object_children private-data
- mcp__tide__candles outbound
- mcp__tide__docs private-data
Pin
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://radar.anlyon.com/api/v1/servers/ad.tide/mcp/verify?hash=875b828aa141a219916c76649e3e10324d37a4d2bde32ed12a81737916389970" | jq -e '.changed == false'Pinned hash 875b828aa141, from Nov 17, 2026, 22:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/ad.tide/mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/ad.tide/mcp)Source: MCP Registry. Synced Nov 4, 2026, 07:17 UTC.
tide MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the tide MCP server safe?
- No scan can promise that. What its definitions show: 38 tools, 29 of which can change, send or delete something, and 8 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the tide MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the tide MCP server do things that cannot be undone?
- Yes. 5 tools can send, pay, publish or merge: wallet_history, build_transaction, withdraw_plan, billing_topup and candles.
What tools does the tide MCP server have?
- 38 tools: 5 irreversible, 24 write, 9 read. wallet_history, build_transaction, withdraw_plan, billing_topup, candles, wallet_profile, balance_at, token_info and 30 more.
Does the tide MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the tide MCP server send data to outside services?
- 4 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): wallet_history, build_transaction, withdraw_plan and candles.
Has the tide MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 17, 2026. Every change is on this page and in its Atom feed.