Riptide — public paper risk record MCP server
Checked 2026-09-07. Alive: no. Handshake: verified.
Category: legal-compliance. API and field schema.
Facts
| id | beepboop2025--riptide |
| name | Riptide — public paper risk record |
| registry_name | io.github.beepboop2025/riptide |
| repo_url | https://github.com/beepboop2025/riptide |
| endpoint_url | https://api.seiche.info/riptide/mcp |
| transport | streamable-http |
| alive | no |
| liveness_reason | unreachable |
| check_reachable | no |
| check_recent_commit | no |
| check_installable | not verifiable |
| handshake_status | verified |
| handshake_checked_at | 2026-09-07T18:01:51Z |
| handshake_protocol_version | 2025-06-18 |
| handshake_auth_hint | not available |
| handshake_auth_discoverable | not available |
| handshake_failure_layer | none |
| handshake_latency_ms | 2060 |
| handshake_tools_state | listed |
| handshake_tool_count | 7 |
| maintenance_status | unknown |
| last_commit_at | not available |
| category | legal-compliance |
| license_spdx | not available |
How to install or connect
Connect your MCP client to https://api.seiche.info/riptide/mcp.
What the checks mean
alive combines the applicable repository, package, and endpoint checks. A null result is not verifiable, not a failure. The MCP handshake is a separate structural probe and is not a security audit. Read the methodology.