mcpdirectory.dev
9,129 servers · updated 23 Sept

Ratchet MCP server

community Active last commit 17 d
{
  "mcpServers": {
    "ratchetgate": {
      "command": "npx",
      "args": [
        "-y",
        "ratchet-mcp@latest"
      ],
      "env": {
        "AUTH_SECRET": "<auth_secret>",
        "PUBLIC_URL": "https://...",
        "DATABASE_URL": "postgresql://user:password@host:5432/db",
        "RATCHET_API_KEY": "<ratchet_api_key>",
        "STRIPE_SECRET_KEY": "sk_live_...",
        "STRIPE_WEBHOOK_SECRET": "sk_live_..."
      }
    }
  }
}
file .mcp.json (in your project root)install npx -y ratchet-mcpversion 0.3.0

What it does

Ratchet is an effect gate that prevents AI agents from executing duplicate side effects across retries and crashes. It holds durable decision records for irreversible actions—like charging cards, sending emails, or deploying code—and ensures each action is attempted at most once, with explicit handling of ambiguous failures.

  • Prevent duplicate charges or transfers when a payment request is retried after a network failure.
  • Track and enforce spending limits for AI agents attempting financial or resource-consuming operations.
  • Record durable outcomes of one-way actions so later callers can retrieve what was already done instead of repeating it.

Tools this server exposes

ToolDoes
beginRequest a decision before executing an effect, receiving execute, duplicate, blocked, or other decision states with a lease token.
reportReport the outcome of an executed effect with a lease token, recording whether it succeeded, failed, or remains indeterminate.

Before you enable it

An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.