← Registry

General Tools

ratchetgate.com

Provides general-purpose tools through the Model Context Protocol.

1 endpoint15 known toolsFirst detected August 31, 2026Last detected September 13, 2026

ENDPOINT 1

https://ratchetgate.com/mcp

No auth detected

MCP server metadata

Name
ratchet
Version
0.3.0
Capabilities
tools
Server instructions

Ratchet gates side effects so the same real-world action is attempted at most once. Before ANY action that touches the outside world — sending a message, charging a card, creating or modifying a resource in someone else's system — call ratchet_begin_effect and obey the decision it returns. Only "execute" authorises you to act. "duplicate", "in_flight", "blocked", "approval_required", and "denied" all mean: do not perform the action. After acting, call ratchet_report_effect. If you are genuinely unsure whether the action reached the outside world, report nothing — an unreported lease is recorded as "indeterminate", which is safer than a wrong answer. Derive idempotency keys deterministically from the work itself, never from a random value or the current time, or the gate cannot recognise a retry.

Known tools 15

ratchet_get_circuit

Call this when a begin returned "approval_required" or "denied" and the reason mentions a circuit breaker.

Inferred read-only
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).

Potential side effects
ratchet_report_effect

Call this IMMEDIATELY AFTER performing an action that ratchet_begin_effect authorised.

Inferred read-only
ratchet_extend_lease

Call this periodically during a long action you were authorised to perform, before the lease expires.

Inferred read-only
ratchet_get_effect

Look up the recorded state of an action WITHOUT reserving a lease and without consuming your plan allowance.

Inferred read-only
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".

Inferred read-only
ratchet_get_run

Recall the work already gated under a run id, before doing anything that might repeat it.

Inferred read-only
ratchet_list_effects

Review recent effects for this workspace, optionally filtered by state or run.

Inferred read-only
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.

Inferred read-only
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.

Inferred read-only
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.

Inferred read-only
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.

Inferred read-only
ratchet_list_receipts

Returns a signed receipt for every decision made about one effect, refusals included.

Inferred read-only
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.

Inferred read-only
ratchet_get_prevented_loss

Counts duplicate actions refused in the last 30 days and what they would have cost.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.ratchet]
url = "https://ratchetgate.com/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "ratchet": {
      "type": "http",
      "url": "https://ratchetgate.com/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: ratchet
Remote MCP URL: https://ratchetgate.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "ratchet": {
      "url": "https://ratchetgate.com/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "ratchet": {
      "type": "http",
      "url": "https://ratchetgate.com/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "ratchet",
  "transport": "streamable-http",
  "url": "https://ratchetgate.com/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.