TideTrade MCP server
app.tidetrade/tidetradetidetrade.appstreamable-httpv1.0.0Scanned
One published crypto trend rule on 140 assets: states, flips, the record, the rule. Read-only, free.
6 tools: 3 change things and 3 only read.
- Reads private data · 1
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. 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 TideTrade MCP server can do
The TideTrade MCP server is published by tidetrade.app, a domain the MCP Registry verified. It has 6 tools. It can create or change data (3 tools: asset, report and rule), but cannot delete data. 3 tools only read.
1 tool reads private data (fetch).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 21, 2026, version 1.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.
6 tools
Changes things 3Claude Code: ask
assetOne asset by id, symbol or name (btc, BTC, Bitcoin): its state on the last completed daily and weekly candle, the room to its line, the record of every daily trip since its replay …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 asset by id, symbol or name (btc, BTC, Bitcoin): its state on the last completed daily and weekly candle, the room to its line, the record of every daily trip since its replay (trips, losing share, average win and loss, best, worst, the rule against holding) and its most recent flips, with the page URL.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
reportOne Sunday Tide Report from the public archive (every ISO week since 2025-W01): how many of the 140 crypto assets were tide in, slack or out on the candles completed by that Sunday…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 Sunday Tide Report from the public archive (every ISO week since 2025-W01): how many of the 140 crypto assets were tide in, slack or out on the candles completed by that Sunday, the Core 30, the week's flips, the leaders, the assets in slack water and the ledger hash of the day. The latest report without a week.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
ruleThe rule manifest behind every state and flip: Supertrend parameters, ATR method, candle definitions, data sources per asset class, the schedule, record types, the changelog and th…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 rule manifest behind every state and flip: Supertrend parameters, ATR method, candle definitions, data sources per asset class, the schedule, record types, the changelog and the manifest hash.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 3Show 3 read-only tools
fetchFetch one document by id from search: snapshot (today's market, daily), snapshot:W (weekly), asset:<id>, report:<week> or report:latest, rule, page:<path>.Reads private dataNo findings
Why it is in this group
- The name "fetch" says "fetch": a word for reading.
What it can reach
- private-dataThe description's first sentence says "fetch" and "document": it reads documents.
Description, as the server wrote it Fetch one document by id from search: snapshot (today's market, daily), snapshot:W (weekly), asset:<id>, report:<week> or report:latest, rule, page:<path>.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
searchSearch assets, reports and pages.No findings
Why it is in this group
- The name "search" says "search": a word for reading.
Description, as the server wrote it Search assets, reports and pages. Returns ids for fetch: snapshot, snapshot:W, asset:<id>, report:<week>, rule, page:<path>.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
snapshotToday's tide on every asset under the rule: crypto breadth and the Core 30 by state (tide in, slack water, tide out), the flips on the newest completed candle, the current Sunday T…No findings
Why it is in this group
- The name "snapshot" says "snapshot": a word for reading.
Description, as the server wrote it Today's tide on every asset under the rule: crypto breadth and the Core 30 by state (tide in, slack water, tide out), the flips on the newest completed candle, the current Sunday Tide Report, and one row per asset with band, direction, close, the Tideline, distance from it in ATR and percent, candle date and last flip. Filter by band, tier or class; daily by default, weekly with timeframe W. Cached a minute; the rows change a few times a day after each candle completes.
Annotations the server declares
- 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 or outbound.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- 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 21, 2026, 19:18 UTC, unchanged since Nov 21, 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
- 3
- 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
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://tidetrade.app/mcp: tools/list returned 6 tools to an anonymous client, including asset (write), report (write), rule (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
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.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http tidetrade https://tidetrade.app/mcpclaude mcp add --transport http tidetrade https://tidetrade.app/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__tidetrade__snapshot",
"mcp__tidetrade__search",
"mcp__tidetrade__fetch"
],
"ask": [
"mcp__tidetrade__asset",
"mcp__tidetrade__report",
"mcp__tidetrade__rule"
],
"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 tidetrade. Review it before you use it.
Capability tags behind 1 rule
- mcp__tidetrade__fetch 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/app.tidetrade/tidetrade/verify?hash=0ee6ada8ac925353ee1f92bcbc51c96a76f1afa0900adae60046b3a5a890c62c" | jq -e '.changed == false'Pinned hash 0ee6ada8ac92, from Nov 21, 2026, 16:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/app.tidetrade/tidetrade/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/app.tidetrade/tidetrade)Source: MCP Registry. Synced Nov 21, 2026, 16:17 UTC.
TideTrade MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the TideTrade MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 3 of which can change, send or delete something, and 0 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 TideTrade MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the TideTrade MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the TideTrade MCP server have?
- 6 tools: 3 write, 3 read. asset, report, rule, snapshot, search and fetch.
Does the TideTrade MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the TideTrade MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the TideTrade MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.