ratchet MCP server
com.ratchetgate/ratchetratchetgate.comstreamable-httpv0.3.0Scanned
Your agent asks before it acts, so the same real-world action is attempted at most once.
15 tools: 2 do something that can't be undone, 6 change things and 7 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 0
- 4 findings
Sign-in required, no OAuth metadata. Remote posture
With Anlyon
2 tools here do something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the ratchet MCP server can do
The ratchet MCP server is published by ratchetgate.com, a domain the MCP Registry verified. It has 15 tools. It can do things that cannot be undone, such as sending, paying or publishing (ratchet_unwind_group and ratchet_get_group) and create or change data (6 tools: ratchet_get_circuit, ratchet_begin_effect, ratchet_report_effect, ratchet_extend_lease and 2 more), but cannot delete data. 7 tools only read.
2 tools bring in text other people can write (ratchet_get_circuit and ratchet_list_effects).
The fixed checks matched 4 findings (annotation-conflict and credentials-mention). Each one comes with the text it matched.
Last scanned Nov 11, 2026, version 0.3.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
15 tools
Can't be undone 2Claude Code: ask
ratchet_get_groupShows 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.1 finding
Why it is in this group
- The name "ratchet_get_group" says "get": a word for reading.
- The description says "irreversible".
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "ratchet_get_group" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "ratchet_get_group" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Inspect a unit of work
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
ratchet_unwind_groupCall 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.No findings
Why it is in this group
- The description's first verb is "call": a word for a change.
- The description says "irreversible".
Description, as the server wrote it 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 in. Undoing forwards can strand a step that depended on an earlier one. Ratchet does NOT perform the compensations. For each step: call ratchet_begin_effect with the step's suggested_idempotency_key and compensates_effect_id, do the real undo, then call ratchet_report_effect. Gating the undo is what stops a retry from refunding twice. Read `unresolved` first. If any effect in the group has an unknown outcome, STOP and resolve it before undoing anything around it. Read `irreversible` too: those steps succeeded and declared no way to undo themselves, so a human has to decide what to do about them. Say so plainly rather than implying the rollback was complete.
Annotations the server declares
- title: Roll back a multi-step unit of work
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Changes things 6Claude Code: ask
ratchet_begin_effectCall 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).No findings
Why it is in this group
- The description's first verb is "call": a word for a change.
Description, as the server wrote it 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 toward it — surface that to the operator rather than ignoring it. If it carries integration_warning, you have been beginning effects without reporting them: call ratchet_report_effect after every action, and tell the operator, because the effects already begun will start being blocked. Decisions: - "execute": you hold the lease. Perform the action now, then call ratchet_report_effect. If the response carries vendor_idempotency_key, send that key to the vendor as ITS own idempotency key (the response says where it goes). Where enforced is true the vendor itself will then refuse a duplicate, which protects the action even if some other caller skips this gate entirely. - "duplicate": this action ALREADY HAPPENED. Do NOT perform it. Use the returned `result` as though you had just done the work. - "in_flight": another process is doing it right now. Do NOT perform it. Wait `retry_after_seconds` and ask again. - "blocked": an earlier attempt may or may not have taken effect. Do NOT perform it. Tell the user what is unresolved, or verify at the vendor and call ratchet_resolve_effect. - "approval_required": a human must approve. Do NOT perform it. - "denied": policy or budget refused it. Do NOT perform it. The idempotency_key must be derived deterministically from the work itself so that a retry of the same logical action produces the same key. Never use a random value or the current time.
Annotations the server declares
- title: Ask permission to perform a side effect
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
ratchet_extend_leaseCall this periodically during a long action you were authorised to perform, before the lease expires.No findings
Why it is in this group
- The description's first verb is "call": a word for a change.
Description, as the server wrote it 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 expires while you are still working, the effect is recorded as having an UNKNOWN outcome, and your report is then refused. If it fails with lease_expired or lease_lost, STOP. Your hold is gone and the outcome is already recorded as unknown. Do not keep going and do not retry the action — call ratchet_begin_effect to find out where things actually stand.
Annotations the server declares
- title: Say you are still working on an effect
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
ratchet_get_circuitCall this when a begin returned "approval_required" or "denied" and the reason mentions a circuit breaker.Reads text others write1 finding
Why it is in this group
- The name "ratchet_get_circuit" says "get": a word for reading.
- The description's first verb is "call": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe description's first sentence says "call" and "mention": it reads comments, which other people can write.
Findings
- Warn
The server marks "ratchet_get_circuit" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "ratchet_get_circuit" says "get": a word for reading.
Description, as the server wrote it 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 open, STOP creating effects of that type. Retrying will not help and each attempt is recorded. - resets_at tells you when it closes itself. If it is null, a human opened it deliberately and only a human will close it — do not wait, and do not poll. - Report the reason to your operator and stop. Do not attempt to work around it by renaming the effect type, splitting the work across keys, or using a different idempotency key: that defeats a safety control that exists to protect the people your actions reach. - effect_type "*" means every effect type in the workspace is stopped.
Annotations the server declares
- title: Check whether surge containment is holding your work
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
ratchet_reconcile_effectsGiven the idempotency keys for actions a vendor says actually happened, returns which ones went through Ratchet and which it has never seen.1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...about. Send references only; never send credentials."
Description, as the server wrote it 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 references only; never send credentials.
Annotations the server declares
- title: Find real-world actions that bypassed the gate
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
ratchet_report_effectCall this IMMEDIATELY AFTER performing an action that ratchet_begin_effect authorised.No findings
Why it is in this group
- The description's first verb is "call": a word for a change.
Description, as the server wrote it 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 reach the outside world (for example, a validation error before the request was sent). That permits a clean retry. If you are UNSURE whether it went through — a timeout, a dropped connection, an ambiguous error — do NOT report anything. Say so to the user. Letting the lease lapse records an honest "indeterminate", which is far safer than a false "failed" that licenses a duplicate.
Annotations the server declares
- title: Report the outcome of an effect you executed
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
ratchet_resolve_effectUse ONLY after you have checked the third-party system and now know what really happened to an effect that was left "indeterminate".1 finding
Why it is in this group
- The name "ratchet_resolve_effect" says "resolve": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
Findings
- Warn
The server marks "ratchet_resolve_effect" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "ratchet_resolve_effect" says "resolve": a word for reading.
Description, as the server wrote it 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 incorrectly is exactly the duplicate or lost action this service exists to prevent.
Annotations the server declares
- title: Settle an effect whose outcome was unknown
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Only reads 7Show 7 read-only tools
ratchet_get_effectLook up the recorded state of an action WITHOUT reserving a lease and without consuming your plan allowance.No findings
Why it is in this group
- The name "ratchet_get_effect" says "get": a word for reading.
Description, as the server wrote it 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 instead; this tool never grants permission.
Annotations the server declares
- title: Check whether an action has already been done
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
ratchet_get_policyShows 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…No findings
Why it is in this group
- The name "ratchet_get_policy" says "get": a word for reading.
Description, as the server wrote it 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 designing a retry strategy.
Annotations the server declares
- title: Read the policy for an effect type
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
ratchet_get_prevented_lossCounts duplicate actions refused in the last 30 days and what they would have cost.No findings
Why it is in this group
- The name "ratchet_get_prevented_loss" says "get": a word for reading.
Description, as the server wrote it 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 what callers declare. This is money not spent at your vendors, never money paid to Ratchet.
Annotations the server declares
- title: What the gate has actually saved
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
ratchet_get_runRecall the work already gated under a run id, before doing anything that might repeat it.No findings
Why it is in this group
- The name "ratchet_get_run" says "get": a word for reading.
Description, as the server wrote it 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 is still in flight, what failed, and — separately, because it is the only category that can hurt you — what has an unknown outcome. Anything under "done" has already happened: use its result rather than performing it again. Costs about a seventeenth of the context of listing the same effects.
Annotations the server declares
- title: What have I already done in this run?
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
ratchet_get_usageReturns the current plan, remaining included effects for the month, prepaid credit balance, and today's declared external spend against each budget ceiling.No findings
Why it is in this group
- The name "ratchet_get_usage" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Check plan, credit balance, and spend
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
ratchet_list_effectsReview recent effects for this workspace, optionally filtered by state or run.Reads text others writeNo findings
Why it is in this group
- The name "ratchet_list_effects" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "review": it reads comments, which other people can write.
Description, as the server wrote it 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.
Annotations the server declares
- title: List recent gated effects
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
ratchet_list_receiptsReturns a signed receipt for every decision made about one effect, refusals included.No findings
Why it is in this group
- The name "ratchet_list_receipts" says "list": a word for reading.
Description, as the server wrote it 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 human asks you to PROVE an action was or was not authorised, rather than asserting it.
Annotations the server declares
- title: Get signed proof of the decisions on an effect
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:45 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 503
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: initialize answered HTTP 503.
Posture changes
- Nov 13, 2026
- HTTP status of an anonymous initialize: 200 to 503
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 8 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://ratchetgate.com/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://ratchetgate.com to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Findings
Matches of fixed checks, with the text they matched.
The server marks "ratchet_get_circuit" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "ratchet_get_circuit" says "get": a word for reading.
The server marks "ratchet_resolve_effect" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "ratchet_resolve_effect" says "resolve": a word for reading.
The server marks "ratchet_get_group" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "ratchet_get_group" says "get": a word for reading.
The description mentions "credentials".
What this check looks forMatched text
description: "...about. Send references only; never send credentials."
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 503; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 8 -> 0 (and 5 more).View diff
- HTTP status of an anonymous initialize: 200 to 503
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 8 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://ratchetgate.com/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://ratchetgate.com to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Install
Pinned to version 0.3.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http ratchet https://ratchetgate.com/mcpclaude mcp add --transport http ratchet https://ratchetgate.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__ratchet__ratchet_get_effect",
"mcp__ratchet__ratchet_get_run",
"mcp__ratchet__ratchet_list_effects",
"mcp__ratchet__ratchet_get_policy",
"mcp__ratchet__ratchet_get_usage",
"mcp__ratchet__ratchet_list_receipts",
"mcp__ratchet__ratchet_get_prevented_loss"
],
"ask": [
"mcp__ratchet__ratchet_get_circuit",
"mcp__ratchet__ratchet_begin_effect",
"mcp__ratchet__ratchet_report_effect",
"mcp__ratchet__ratchet_extend_lease",
"mcp__ratchet__ratchet_resolve_effect",
"mcp__ratchet__ratchet_unwind_group",
"mcp__ratchet__ratchet_get_group",
"mcp__ratchet__ratchet_reconcile_effects"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as ratchet. Review it before you use it.
Capability tags behind 2 rules
- mcp__ratchet__ratchet_get_circuit untrusted-input
- mcp__ratchet__ratchet_list_effects untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.ratchetgate/ratchet/verify?hash=97d177427f4aea4b4b87b005aeba7521e1150db962682a1b782e3455bf5f6afb" | jq -e '.changed == false'Pinned hash 97d177427f4a, from Nov 11, 2026, 00:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.ratchetgate/ratchet/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.ratchetgate/ratchet)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:01 UTC.
ratchet MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the ratchet MCP server safe?
- No scan can promise that. What its definitions show: 15 tools, 8 of which can change, send or delete something, and 4 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the ratchet MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the ratchet MCP server do things that cannot be undone?
- Yes. 2 tools can send, pay, publish or merge: ratchet_unwind_group and ratchet_get_group.
What tools does the ratchet MCP server have?
- 15 tools: 2 irreversible, 6 write, 7 read. ratchet_unwind_group, ratchet_get_group, ratchet_get_circuit, ratchet_begin_effect, ratchet_report_effect, ratchet_extend_lease, ratchet_resolve_effect, ratchet_reconcile_effects and 7 more.
Does the ratchet MCP server need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the ratchet MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the ratchet MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 11, 2026.