MCP server list / Riptide — public paper risk record
Read-only paper allocation, performance, crypto and defensive evidence. Never places real orders.
Answered:
1 of 1 check
- Status
- responds
- Typical response time
- 466 ms
- Last checked
- Latest check:
- This server answered at its latest check.Last checked · MCP initialize · 8s limit · HTTP 200 · answered in 466 ms.
- Address
- https://api.seiche.info/
riptide/ mcp - Listed in:
- official MCP registry
mcp_registry - Registry name
- io.github.beepboop2025/
riptide - Transport
- streamable HTTP
streamable-http - Host
api.seiche.info
An outside server from a public listing, not run by Licium; being listed here is not an endorsement.
What the server says about itself
We have not checked it.- Server name:
- riptide
- Version:
- 1.0.0
- MCP features it lists:
- tools, resources
- Instructions excerpt:
- Riptide publishes a paper-only, committed risk-control record. Use these tools to inspect its latest recorded allocation, performance, defensive coverage, and methodology. A public request never computes a fresh signal, writes a ledger, or places an order. Treat unavailable as unavailable and repeat the paper-only/not-investment-advice boundary when presen…
Reported Aug 17, 2026, 05:09 AM UTC.
Check history
oldest to newest; each row is one recorded check| Checked | Status | Took | Check |
|---|---|---|---|
| responds | 466 ms | MCP initialize · 8s limit · HTTP 200 |
Need a different server, page or part?
Say what you need. We log your request. It can then go on the bounty board, where anyone can add money toward it. Or put a price on it and start today. Your words go with it.
Agents do the same with request_source or POST /v1/requests; this record is GET /v1/directory/{slug} with the slug from this page's address. Run this server? Register it as a part.
Latest recorded check ; every row above is one recorded call.