Riptide — public risk and event research is a remote MCP server that gives an AI agent 7 tools, among them riptide_allocation, riptide_crypto_record, riptide_event_markets. It answers at https://api.seiche.info/riptide/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 21 October 2026, succeeded.
Read-only paper risk evidence and policy-gated committed event research. No real orders.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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. |
Every block below points at https://api.seiche.info/riptide/mcp. Pick your client and copy.
claude mcp add --transport http riptide-public-risk-and-event-re https://api.seiche.info/riptide/mcp
{
"mcpServers": {
"riptide-public-risk-and-event-re": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://api.seiche.info/riptide/mcp"]
}
}
}{
"mcpServers": {
"riptide-public-risk-and-event-re": {
"url": "https://api.seiche.info/riptide/mcp"
}
}
}{
"servers": {
"riptide-public-risk-and-event-re": {
"type": "http",
"url": "https://api.seiche.info/riptide/mcp"
}
}
}{
"context_servers": {
"riptide-public-risk-and-event-re": {
"url": "https://api.seiche.info/riptide/mcp"
}
}
}{
"mcpServers": {
"riptide-public-risk-and-event-re": {
"serverUrl": "https://api.seiche.info/riptide/mcp"
}
}
}{
"mcpServers": {
"riptide-public-risk-and-event-re": {
"url": "https://api.seiche.info/riptide/mcp"
}
}
}name: Riptide — public risk and event research
version: 0.0.1
schema: v1
mcpServers:
- name: Riptide — public risk and event research
type: streamable-http
url: https://api.seiche.info/riptide/mcp{
"mcpServers": {
"riptide-public-risk-and-event-re": {
"httpUrl": "https://api.seiche.info/riptide/mcp"
}
}
}{
"mcpServers": {
"riptide-public-risk-and-event-re": {
"type": "http",
"url": "https://api.seiche.info/riptide/mcp"
}
}
}{
"mcpServers": {
"riptide-public-risk-and-event-re": {
"url": "https://api.seiche.info/riptide/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fapi.seiche.info%2Friptide%2Fmcp&type=streamable_http&id=riptide-public-risk-and-event-re&name=Riptide%20%E2%80%94%20public%20risk%20and%20event%20research
It answered our last check on 21 October 2026 in 21 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
7, as returned by the server's own tools/list on 13 September 2026: riptide_allocation, riptide_crypto_record, riptide_event_markets, riptide_methodology, riptide_overview, riptide_paper_record, riptide_risk_evidence.
It answered our last check on 21 October 2026 in 21 ms. Over 6 checks since 11 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://api.seiche.info/riptide/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.beepboop2025. Endpoint host: api.seiche.info. ARD identifier: urn:air:io.github.beepboop2025:mcp:riptide.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.