Riptide — public risk and event research
REMOTE · API.SEICHE.INFO
Read-only paper risk evidence and policy-gated committed event research. No real orders.
Available components
Last scanned (20 hours ago)
Scores higher than 94% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 284 tokens (~40/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 30 Aug 26 0
- Tool “riptide_allocation” now declares an output schema ▲ functional
- Tool “riptide_crypto_record” now declares an output schema ▲ functional
- Tool “riptide_event_markets” now declares an output schema ▲ functional
- Tool “riptide_methodology” now declares an output schema ▲ functional
- Tool “riptide_overview” now declares an output schema ▲ functional
- Tool “riptide_paper_record” now declares an output schema ▲ functional
- Tool “riptide_risk_evidence” now declares an output schema ▲ functional
- The server no longer declares the “resources” capability functional
- First check of Tool coverage: 100 functional
- Server version: 1.2.0 → 1.3.0 functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “riptide_event_markets” rewrote its description, which is the text the model reads security
- Server version: 1.1.0 → 1.2.0 functional
- 23 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 209 → 261 ▼ functional
- Server version: 1.0.0 → 1.1.0 functional
- New tool “riptide_event_markets” functional
- 17 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://api.seiche.info/riptide/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.seiche.info | CN=YE1,O=Let's Encrypt,C=US | 7 Sept 2026 | 6 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 51c1896503dd693d96ce81ef09be5a03892 |
| SANs: api.seiche.info | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of api.seiche.info. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| info. | present | 9986 | 8 | Verified |
| seiche.info. | present | 2371 | 13 | Verified |
| api.seiche.info. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'none'; frame-ancestors 'none'; base-uri 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.seiche.info/riptide/mcp | Verified | 200 | |
| http (plaintext) | http://api.seiche.info/riptide/mcp | HTTPS enforced | 308 | https://api.seiche.info/riptide/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
riptide_allocation Allocation ~21
Latest allocation committed by the independent daily paper job.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | – | – |
| disclaimer | string | yes | – |
| error | string | – | – |
| execution_mode | – | yes | – |
| generated_at | string | yes | – |
| kind | string | yes | – |
| product | – | yes | – |
| real_orders | – | yes | – |
| schema | – | yes | – |
No examples provided.
riptide_crypto_record Crypto Record ~21
Separate toy crypto strategy paper record and honesty boundary.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | – | – |
| disclaimer | string | yes | – |
| error | string | – | – |
| execution_mode | – | yes | – |
| generated_at | string | yes | – |
| kind | string | yes | – |
| product | – | yes | – |
| real_orders | – | yes | – |
| schema | – | yes | – |
No examples provided.
riptide_event_markets Event Markets ~26
Policy-gated committed Event Intelligence availability, eligible quotes, and gaps.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | – | – |
| disclaimer | string | yes | – |
| error | string | – | – |
| execution_mode | – | yes | – |
| generated_at | string | yes | – |
| kind | string | yes | – |
| product | – | yes | – |
| real_orders | – | yes | – |
| schema | – | yes | – |
No examples provided.
riptide_methodology Methodology ~21
Public methodology, safety boundaries, and canonical links.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | – | – |
| disclaimer | string | yes | – |
| error | string | – | – |
| execution_mode | – | yes | – |
| generated_at | string | yes | – |
| kind | string | yes | – |
| product | – | yes | – |
| real_orders | – | yes | – |
| schema | – | yes | – |
No examples provided.
riptide_overview Overview ~26
Riptide health, latest allocation, both paper records, and links.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | – | – |
| disclaimer | string | yes | – |
| error | string | – | – |
| execution_mode | – | yes | – |
| generated_at | string | yes | – |
| kind | string | yes | – |
| product | – | yes | – |
| real_orders | – | yes | – |
| schema | – | yes | – |
No examples provided.
riptide_paper_record Paper Record ~26
Verified core paper equity, return, drawdown, and recent curve.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | – | – |
| disclaimer | string | yes | – |
| error | string | – | – |
| execution_mode | – | yes | – |
| generated_at | string | yes | – |
| kind | string | yes | – |
| product | – | yes | – |
| real_orders | – | yes | – |
| schema | – | yes | – |
No examples provided.
riptide_risk_evidence Risk Evidence ~23
Latest defensive coverage aggregate, without raw breach text.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | – | – |
| disclaimer | string | yes | – |
| error | string | – | – |
| execution_mode | – | yes | – |
| generated_at | string | yes | – |
| kind | string | yes | – |
| product | – | yes | – |
| real_orders | – | yes | – |
| schema | – | yes | – |
No examples provided.
How do I install the Riptide — public risk and event research MCP server?
Riptide — public risk and event research is a hosted endpoint at https://api.seiche.info/riptide/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.seiche.info
claude mcp add --transport http beepboop2025-riptide 'https://api.seiche.info/riptide/mcp'
What is the Riptide — public risk and event research MCP server?
Riptide — public risk and event research is an MCP server listed in the public MCP registry as io.github.beepboop2025/riptide. Read-only paper risk evidence and policy-gated committed event research. No real orders. This page covers its hosted endpoint (https://api.seiche.info/riptide/mcp).
Is the Riptide — public risk and event research MCP server safe to use?
Riptide — public risk and event research scores 87 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Riptide — public risk and event research MCP server expose?
Riptide — public risk and event research exposes 7 tools: riptide_allocation, riptide_crypto_record, riptide_event_markets, riptide_methodology, riptide_overview, and 2 more. Their descriptions and schemas cost roughly 164 tokens of context every time the server is loaded.
Does the Riptide — public risk and event research MCP server require authentication?
No. We connected to Riptide — public risk and event research without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Riptide — public risk and event research MCP server still maintained?
Riptide — public risk and event research is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.