Riptide

Riptide MCP

Public client configuration and tool documentation for Riptide, a read-only service for paper risk records and policy-gated event research.

Open Riptide · OpenAPI · Official MCP Registry

Connect

Use a client that supports Streamable HTTP MCP:

• Server URL: https://api.seiche.info/riptide/mcp
• Authentication: none for the public read-only tools.
• Payment: none for these MCP tools.

For Claude Code project configuration, use .mcp.json:

{
  "mcpServers": {
    "riptide": {
      "type": "http",
      "url": "https://api.seiche.info/riptide/mcp"
    }
  }
}

This repository also includes VS Code configuration and Cursor configuration, following their VS Code and Cursor configuration formats. Merge the Riptide entry into an existing configuration so other connections are preserved. Review the public tools when your client asks to connect.

Try a research question

Use Riptide to show the latest committed paper record. Include the record date, methodology, and any unavailable data.

Check Riptide Event Intelligence availability. Distinguish eligible published quotes from unavailable or quarantined provider data.

Explain the defensive coverage recorded by Riptide and what it cannot establish about future performance.

Public tools

Tool	Purpose
riptide_allocation	Latest allocation committed by the independent daily paper job.
riptide_crypto_record	Separate toy crypto strategy paper record and honesty boundary.
riptide_event_markets	Policy-gated committed Event Intelligence availability, eligible quotes, and gaps.
riptide_methodology	Public methodology, safety boundaries, and canonical links.
riptide_overview	Riptide health, latest allocation, both paper records, and links.
riptide_paper_record	Verified core paper equity, return, drawdown, and recent curve.
riptide_risk_evidence	Latest defensive coverage aggregate, without raw breach text.

The machine-readable tool snapshot was observed on 6 September 2026. Discover tools from the live endpoint before depending on a cached schema. server.json matches the active official Registry record for version 1.3.0 observed that day; it is a discovery record, not an independent deployment attestation.

Evidence boundaries

Riptide returns records committed by independent jobs. A public request does not compute a new signal, write a trading ledger, or place an order. Paper performance is not real-money performance or a promise of returns.

Event-market prices are published crowd quotes, not Riptide forecasts or bets. Source rights, jurisdiction and quote freshness can require an intentional quarantine with zero provider events. Preserve unavailable states, source dates, and the service's stated limitations when presenting a result.

The MCP tools provide research, not investment advice or trading authorization. Public access does not grant redistribution rights to underlying provider material; follow the rights information returned with each record.

Repository scope and maintenance

This repository contains public client files and documentation. The hosted implementation has its own release process. Open an issue here for connection or documentation problems, including your client version and a sanitized error; exclude credentials, private research inputs and account information.

The MIT license covers this repository's client configuration and original documentation. It does not relicense data returned by the service.