Riptide — public paper risk record
REMOTE · API.SEICHE.INFO · SCANNED AUG 16
Read-only paper allocation, performance, crypto and defensive evidence. Never places real orders.
Available components
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 →
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 Usability68
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 209 tokens (~34/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · api.seiche.info
claude mcp add --transport http beepboop2025-riptide https://api.seiche.info/riptide/mcp
[mcp_servers.beepboop2025-riptide] url = "https://api.seiche.info/riptide/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"beepboop2025-riptide": {
"type": "remote",
"url": "https://api.seiche.info/riptide/mcp",
"enabled": true
}
}
} openclaw mcp add beepboop2025-riptide --url https://api.seiche.info/riptide/mcp --transport streamable-http
mcp_servers:
beepboop2025-riptide:
url: "https://api.seiche.info/riptide/mcp" {
"mcpServers": {
"beepboop2025-riptide": {
"type": "http",
"url": "https://api.seiche.info/riptide/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 16 Aug 26 72
First indexed and scored.
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 16 Aug 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 | 9 Jul 2026 | 7 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 5124ecbed078faee1a2903ca8d3b4470ad0 |
| 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 |
DNSSEC secure
Validation of api.seiche.info. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| info. | present | 5104 | 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=() |
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.
riptide_allocation Allocation ~21
Latest allocation committed by the independent daily paper job.
Input schema present but exposes no named parameters.
No output schema declared.
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.
No output schema declared.
No examples provided.
riptide_methodology Methodology ~21
Public methodology, safety boundaries, and canonical links.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
riptide_overview Overview ~26
Riptide health, latest allocation, both paper records, and links.
Input schema present but exposes no named parameters.
No output schema declared.
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.
No output schema declared.
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.
No output schema declared.
No examples provided.