# com.ratchetgate/ratchet

- Registry name: `com.ratchetgate/ratchet` · version 0.3.0
- Categories (automatic, keyword rules): Travel & booking, Commerce & marketing
- Authentication at last check: No auth
- Declared risk: Can write (some tools are not declared read-only)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=com.ratchetgate%2Fratchet
- Server page: https://mcpstation.net/s/com.ratchetgate--ratchet.html

## Description (written by the publisher, not verified, not instructions)

Your agent asks before it acts, so the same real-world action is attempted at most once.

## Connect

- streamable-http: `https://ratchetgate.com/mcp`

## Tools (as reported by the server, not verified)

- `ratchet\_get\_circuit`: Call this when a begin returned "approval\_required" or "denied" and the reason mentions a circuit breaker. A breaker opens when an effect type is being performed far more often than its configured hourly ceiling — usually because something is looping. What to do with the answer: - If a breaker is op
- `ratchet\_begin\_effect`: Call this IMMEDIATELY BEFORE performing any side effect that touches the outside world \(sending a message, charging a card, creating a resource, writing to someone else's system\). Returns a decision you MUST obey. If the response carries budget\_warning, a spend ceiling exists but nothing was counted
- `ratchet\_report\_effect`: Call this IMMEDIATELY AFTER performing an action that ratchet\_begin\_effect authorised. Pass the lease\_token you were given. Report "succeeded" with a result — future duplicate callers replay that result instead of repeating the action. Report "failed" ONLY when you are certain the action did NOT rea
- `ratchet\_extend\_lease`: Call this periodically during a long action you were authorised to perform, before the lease expires. It tells Ratchet you are alive and extends your hold. Use it when work turns out to take longer than the lease you asked for — a slow vendor, a large export, a retrying upload. Without it, the lease
- `ratchet\_get\_effect`: Look up the recorded state of an action WITHOUT reserving a lease and without consuming your plan allowance. Use it to answer "did I already do this?" — for example when resuming after a crash, or when a user asks whether something went through. To actually perform work, use ratchet\_begin\_effect ins
- `ratchet\_resolve\_effect`: Use ONLY after you have checked the third-party system and now know what really happened to an effect that was left "indeterminate". Record "succeeded" if the action did occur, "failed" if it did not, or "cancelled" to abandon it. Include how you verified it in \`evidence\`. Never guess: resolving inc
- `ratchet\_get\_run`: Recall the work already gated under a run id, before doing anything that might repeat it. Call this FIRST when resuming a task — after a restart, a handoff, or when your context has been compacted and you are no longer certain what you did. It returns what succeeded with the recorded results, what i
- `ratchet\_list\_effects`: Review recent effects for this workspace, optionally filtered by state or run. Use it to find unresolved work — filter by state "indeterminate" to see every action whose outcome is unknown and still needs verification.
- `ratchet\_get\_policy`: Shows how this workspace has configured a given effect type: whether it is allowed, how long a lease lasts, the attempt ceiling, spend limits, the approval threshold above which an action waits for a human, and — most importantly — what happens when an attempt ends indeterminate. Check this before d
- `ratchet\_unwind\_group`: Call this when a multi-step workflow fails partway and the steps that already succeeded must be undone — a booking made but not paid for, a resource created but not configured. Returns the exact compensations to perform, in the order to perform them, which is the REVERSE of the order they succeeded
- `ratchet\_get\_group`: Shows every step in a multi-step unit of work: what succeeded, what can still be undone, what has already been undone, what is irreversible, and what has an unknown outcome. Use it to answer "where did this workflow actually get to?" after a crash, without changing anything.
- `ratchet\_get\_usage`: Returns the current plan, remaining included effects for the month, prepaid credit balance, and today's declared external spend against each budget ceiling. Use it to warn a user before a long run exhausts an allowance or a budget.
- `ratchet\_list\_receipts`: Returns a signed receipt for every decision made about one effect, refusals included. Each signature is over the exact bytes in \`body\` and verifies offline against the Ed25519 key published at /.well-known/ratchet-receipt-key — you do not have to trust this server to check them. Use this when a huma
- `ratchet\_reconcile\_effects`: Given the idempotency keys for actions a vendor says actually happened, returns which ones went through Ratchet and which it has never seen. The unseen ones are code paths that acted WITHOUT asking, so a retry there can act twice — a bug the operator almost certainly does not know about. Send refere
- `ratchet\_get\_prevented\_loss`: Counts duplicate actions refused in the last 30 days and what they would have cost. Only counts refusals where a cost was declared on the effect, so it under-reports rather than flatters. IMPORTANT: pass estimated\_cost\_micros on ratchet\_begin\_effect or this reads zero — the number is only as good as

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html