Home / MCP registry index / com.ratchetgate/ratchet
com.ratchetgate/ratchet
com.ratchetgate/ratchet in the official MCP registry.
Endpoint https://ratchetgate.com/mcp. Source: github.com/thearchitect0x-glitch/ratchet.
The registry describes it as: Your agent asks before it acts, so the same real-world action is attempted at most once.
We read its 15 tools on 2026-10-28. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
ratchet_get_circuit ratchet_begin_effect ratchet_report_effect ratchet_extend_lease ratchet_get_effect ratchet_resolve_effect ratchet_get_run ratchet_list_effects ratchet_get_policy ratchet_unwind_group ratchet_get_group ratchet_get_usage ratchet_list_receipts ratchet_reconcile_effects ratchet_get_prevented_loss
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-ratchetgate-ratchet)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.