Skip to main content
Glama
thearchitect0x-glitch

ratchet-mcp

by thearchitect0x-glitch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to ratchet-mcp

  • Dvarapala

    demolished-lab
    A
    license
    Not graded
    quality
    C
    maintenance
    Provides permission gates and tamper-evident audit logging for AI agent tool executions, with declarative policies, consent ladders, and hash-chained verification.
    MIT

  • everrun

    UcelX
    A
    license
    Not graded
    quality
    B
    maintenance
    Provides durable mission state for AI agents, enabling crash-safe recovery, verified completion, and explicit reconciliation of uncertain side effects without duplicate or blind retries.
    3
    Apache 2.0

Related Servers

  • shield-kya

    The-Pixel-Boys
    A
    license
    Not graded
    quality
    B
    maintenance
    A local gate that lets agents submit risky tool actions for policy evaluation and receive ALLOW, DENY, or REQUIRE_APPROVE decisions before executing irreversible side effects. It can also open human approval holds and record an activity trail without executing the side effect itself.
    1,549 npm
    1
    MIT
  • ERDL Guard by OpenOBA

    ERDL Guardofficial

    OpenOBA
    A
    license
    Not graded
    quality
    A
    maintenance
    Enforces deterministic policy decisions on AI agent tool calls, supporting allow, deny, correct, escalate, and human review actions with verifiable audit receipts.
    200 npm
    MIT
  • mcp-vaara by vaaraio

    mcp-vaaraofficial

    vaaraio
    A
    license
    Not graded
    quality
    A
    maintenance
    Gates every AI agent tool call against your policy before it runs, then writes a hash-chained, tamper-evident record of what was decided and what happened. Anyone can verify that record offline, without your software, your systems or any key you hold.
    1,428 PyPI
    12
    AGPL 3.0

  • interlock-mcp

    Mustaqeem-Rafi
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI agents to use payment APIs safely by gating every tool call through deterministic mandates, value checks, and an exactly-once ledger, so they cannot pay twice or exceed authorisation.
    5 npm
    MIT
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.5/5.0

Scored across 15 tools

Disambiguation5/5

Each tool targets a distinct concern: authorization, reporting, lease extension, state lookup, group/run inspection, receipts, policy, usage, reconciliation, and safety statistics. The only superficially similar retrieval tools (get_effect, list_effects, get_run, get_group) are clearly separated by what they return and when to use them.

Naming Consistency5/5

All tools share the ratchet_ prefix and follow a consistent snake_case verb_noun pattern (begin_effect, report_effect, get_policy, unwind_group). Even compound targets like get_prevented_loss preserve the same structure, so the naming convention is predictable.

Tool Count5/5

Fifteen tools is at the top of the ideal range, but the domain is substantial: effect lifecycle, leases, lookup, audit receipts, policies, budgets, circuit breakers, reconciliation, and rollback. Each tool has a distinct role and none feels redundant.

Completeness5/5

The surface covers the full effect lifecycle—begin, report, extend, resolve—plus all inspection and recovery needs: runs, groups, circuits, receipts, policy, usage, reconcile, and prevented-loss stats. No obvious dead end exists for the intended agent workflows.

Maintenance

ActivityMaintained
ResponsivenessResponsive

Resources