Skip to main content
Glama
Reins

Reins

Official
by botinfo-ai

Related Servers

Alternatives to Reins

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that acts as an authorization gateway between an AI agent and external systems, deterministically refusing actions that exceed granted authority and sealing every decision into an auditable chain of custody.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enforces runtime governance on AI agent actions — file access, command execution, delegation chains, and permission escalation.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that lets AI agents consult a human-approved, versioned rulebook mined from team conversations and gate actions through deterministic checks for act, approval, or escalation. It also re-checks running actions before each step and after completion, halting runs that exceed approved rules or use stale or reused decisions.
      42 PyPI
      3
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server for agent authorization that tests the full effect surface and enforces control over consequential actions before dispatch, emitting verifiable execution evidence.
      2
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      A unified MCP server providing observability, safety control, and behavior evolution for high-agency AI agents through tracing, replaying, and auditing. It features real-time firewall guardrails and ML-driven anomaly detection to monitor, block, or fork agent actions based on risk.
      MIT

    TDQS

    B3.2/5.0

    Scored across 6 tools

    Disambiguation4/5

    The motion and control tools (drive, reins_stop, reins_renew, reins_status, reins_policy) have distinct purposes, but set_led stands apart from the reins_-prefixed control/state family and could be mistaken for a non-observability action. Boundaries are clear enough that misselection is unlikely.

    Naming Consistency2/5

    Names mix plain verbs (drive, set_led) with a reins_ prefix (reins_stop, reins_status, reins_policy, reins_renew), and none of the tools strictly follow a verb_noun pattern. The split between drive/set_led and the reins_ namespace is jarring.

    Tool Count4/5

    Six tools fit the safety-lease motion domain without bloat; each (motion, stop, renew, status, policy, LED) earns a place. Slightly thin on read-only inspection but reasonable for a control server.

    Completeness4/5

    Core motion lifecycle (drive, renew lease, stop, status, policy) is covered, including safety semantics. Minor gaps: no explicit resume or LED read-back and no generic pre-flight validation for flight-like actions, but usable.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data