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.
    4
    Apache 2.0

Related Servers

  • agentraas

    sumedhchatse
    F
    license
    Not graded
    quality
    A
    maintenance
    Enables AI agents to execute real-world API actions with exactly-once reliability, deduplication, auditing, and human-in-the-loop safeguards via MCP.
    2
    -

  • veor

    winterbim
    A
    license
    Not graded
    quality
    B
    maintenance
    Provides a governed execution boundary for AI agents, enforcing deterministic policy, one-shot human approvals, and signed receipts for MCP tool effects.
    MIT

  • shield-kya

    The-Pixel-Boys
    A
    license
    Not graded
    quality
    A
    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.
    844 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.
    9 npm
    MIT
Deploy Server
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

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