Skip to content

Riptide — public risk and event research

by beepboop2025 · remote · no sign-in to list tools · v1.3.0 · published by GitHub user beepboop2025

Read-only paper risk evidence and policy-gated committed event research. No real orders.

Changes · 7

7 tools: 7 change things.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http riptide https://api.seiche.info/riptide/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

7 tools

Changes things 7Claude Code: ask
  • riptide_allocationLatest allocation committed by the independent daily paper job.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
    Latest allocation committed by the independent daily paper job.

    Annotations the server declares

    • title: Latest allocation committed by the independent daily paper job
    • readOnlyHint: true
    • idempotentHint: true
    • destructiveHint: false
    • openWorldHint: false
  • riptide_crypto_recordSeparate toy crypto strategy paper record and honesty boundary.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
    Separate toy crypto strategy paper record and honesty boundary.

    Annotations the server declares

    • title: Separate toy crypto strategy paper record and honesty boundary
    • readOnlyHint: true
    • idempotentHint: true
    • destructiveHint: false
    • openWorldHint: false
  • riptide_event_marketsPolicy-gated committed Event Intelligence availability, eligible quotes, and gaps.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
    Policy-gated committed Event Intelligence availability, eligible quotes, and gaps.

    Annotations the server declares

    • title: Policy-gated committed Event Intelligence availability, eligible quotes, and gaps
    • readOnlyHint: true
    • idempotentHint: true
    • destructiveHint: false
    • openWorldHint: false
  • riptide_methodologyPublic methodology, safety boundaries, and canonical links.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
    Public methodology, safety boundaries, and canonical links.

    Annotations the server declares

    • title: Public methodology, safety boundaries, and canonical links
    • readOnlyHint: true
    • idempotentHint: true
    • destructiveHint: false
    • openWorldHint: false
  • riptide_overviewRiptide health, latest allocation, both paper records, and links.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
    Riptide health, latest allocation, both paper records, and links.

    Annotations the server declares

    • title: Riptide health, latest allocation, both paper records, and links
    • readOnlyHint: true
    • idempotentHint: true
    • destructiveHint: false
    • openWorldHint: false
  • riptide_paper_recordVerified core paper equity, return, drawdown, and recent curve.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
    Verified core paper equity, return, drawdown, and recent curve.

    Annotations the server declares

    • title: Verified core paper equity, return, drawdown, and recent curve
    • readOnlyHint: true
    • idempotentHint: true
    • destructiveHint: false
    • openWorldHint: false
  • riptide_risk_evidenceLatest defensive coverage aggregate, without raw breach text.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
    Latest defensive coverage aggregate, without raw breach text.

    Annotations the server declares

    • title: Latest defensive coverage aggregate, without raw breach text
    • readOnlyHint: true
    • idempotentHint: true
    • destructiveHint: false
    • 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 private-data or untrusted-input or outbound.

Reads private data0
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 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 Oct 22, 2026, 15:20 UTC, unchanged since Oct 22, 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
7
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
none
RFC 9728 protected resource metadata
none
Authorization servers
none
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 7 tools that change things (7 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.seiche.info/riptide/mcp: tools/list returned 7 tools to an anonymous client, including riptide_allocation (write), riptide_crypto_record (write), riptide_event_markets (write), riptide_methodology (write), riptide_overview (write) and 2 more

    What this check looks for

Install

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

claude mcp add --transport http riptide https://api.seiche.info/riptide/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": [],
    "ask": [
      "mcp__riptide__riptide_allocation",
      "mcp__riptide__riptide_crypto_record",
      "mcp__riptide__riptide_event_markets",
      "mcp__riptide__riptide_methodology",
      "mcp__riptide__riptide_overview",
      "mcp__riptide__riptide_paper_record",
      "mcp__riptide__riptide_risk_evidence"
    ],
    "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 riptide. Review it before you use it.