ratchet
Server Details
Your agent asks before it acts, so the same real-world action is attempted at most once.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- deimos-hq/ratchet
- GitHub Stars
- 0
- Server Listing
- ratchet-mcp
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 15 tools
Each tool targets a distinct phase or concern of the effect lifecycle: beginning, extending, reporting, resolving, reconciling, unwinding, and inspecting. Even the several read-oriented tools are clearly separated by scope: single effect, run, group, policy, usage, and receipt listing.
All tools share the ratchet_ prefix and follow a consistent verb_noun pattern: begin_effect, extend_lease, get_run, list_effects, report_effect, unwind_group. There are no mixed naming conventions or vague generic verbs.
Fifteen tools is at the upper edge of the ideal range, but each one covers a necessary part of the idempotency and effect-tracking domain: gating, lease maintenance, reporting, resolution, reconciliation, investigation, and workflow unwinding. No tools feel redundant or ornamental.
The surface covers the full lifecycle of an externally visible effect: begin, extend, report, resolve, reconcile, and compensating rollback via unwind. It also provides the necessary inspection and policy tools for crash recovery, retries, budget checks, and proof of authorization, leaving no obvious dead ends.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Your agent asks you before it acts. You answer with one tap on your phone. Human-in-the-loop.
Human approval for AI agents: ask before a risky action, act only once a person approves.
Human-reviewed real-world actions for AI agents.
Human approval for AI agents: one ask, one person, one boolean.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceMCP server for governing agent actions: an agent can propose a retry but cannot approve it itself. Deterministic policy allows, holds or refuses each typed action, a held action needs a single-use human approval none of the tools can create, and every run leaves a verifiable receipt.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables an AI agent to prepare an action, have a human approve the exact preview via a local token-protected page, and then execute it once with no replay. Provides read-only status, revocation, expiry, and verified readback so uncertain or changed actions cannot be run without explicit human approval.MIT
- AlicenseNot gradedqualityDmaintenanceA local human-in-the-loop gate for AI agents that blocks actions until human approval, with timeout defaulting to denial.MIT
- AlicenseNot gradedqualityCmaintenanceFreshness gate for AI agents: verify a belief is still true against the live world before you act.Apache 2.0
Glama MCP Gateway
Add one secure layer between your agents and this server.