lat.rta/rta
rta — zero-knowledge proof of a threshold
Is the rta MCP server down? Yes. It has given no valid answer since 2026-10-21: not MCP (HTTP 200).
Prove a hidden value reached a threshold without revealing the value.
not MCP down since 2026-10-21 · probed 2026-11-15 · unchanged since 2026-11-12 · HTTP 200
Streamable HTTP error: Error POSTing to endpoint: {"type":"https://developers.cloudflare.com/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/err- Endpoint
- https://rta.lat/mcp (streamable-http)
- Host
- rta.lat
- Repository
- https://github.com/mrpkk/rta
- Website
- https://rta.lat/
- Registry
- active, updated 2026-11-12 · registry entry
Compare this server with others.
More servers
Other registry entries on rta.lat.
- nidhipati — proof of spend for AI agents io.github.mrpkk/nidhipati · alive
- Soma — open protocol for agent work io.github.mrpkk/soma-protocol · alive
- mitracore — trust layer for agent work lat.rta/mitracore · alive
- skilllint — vet an agent skill before you install it lat.rta/skilllint · alive
- Soma — open protocol for agent work lat.rta/soma · alive
Servers that mention knowledge or threshold.
- inference.sh ac.inference.sh/mcp · needs auth
- Knowledge Base ai.b77/knowledge-base · needs auth
- brainattic ai.brainattic/knowledge-base · needs auth
- Buron ai.buron/buron · paid (402)
- ColdState — Deterministic Knowledge Infrastructure ai.coldstate/knowledge · alive
- DeepDNA ai.deepdna/knowledge · alive
- ai.emberverse/emberverse · alive
- xmp4 — Semantic code knowledge for your stack ai.example4/xmp4 · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- No valid answer since 2026-10-21, in every probe since then.
- The endpoint answers HTTP 200, but not with a valid MCP initialize result. Common causes: the URL is a web page or a REST API and not the MCP endpoint, the server answers a JSON-RPC error on initialize, or the response is HTML.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.