Skip to main content
Glama

Related Servers

Alternatives to Aegis

No user-submitted related servers found.

    Related Servers

    • A
      license
      C
      quality
      B
      maintenance
      A fail-closed preflight, approval, evidence, and verification runtime for agents, preventing unsupported output from being treated as verified completion.
      3
      MIT
    • A
      license
      C
      quality
      C
      maintenance
      Enables safe coordination of Herdr coding agents with lease-scoped reviewer and writer lifecycles, semantic waits for agent states, and read-only topology inspection, while prohibiting arbitrary shell execution and unscoped lifecycle operations.
      44
      MIT
    • F
      license
      A
      quality
      A
      maintenance
      Enables coding agents to perform workspace-confined file operations, read-only Git inspection, and structured shell commands, while requiring out-of-band human approval for mutations and external executions and maintaining an audit trail.
      14
      3
      -
    • F
      license
      B
      quality
      D
      maintenance
      Structured workspace runtime for long-running coding agents, providing controlled workspace capabilities with task state, snapshots, checkpoints, drift detection, verification evidence, audit logs, and structured handoff.
      20
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      A personal agent control harness that governs AI agents by checking every consequential action against user-defined rules, logging all actions to a tamper-evident audit chain, and providing a global kill switch. It runs as an MCP server sidecar to coding agents or standalone, keeping users in charge of what their agents can do.
      4
      AGPL 3.0

    TDQS

    C2.7/5.0

    Scored across 4 tools

    Disambiguation2/5

    land_inject and decide both concern LAND context injection, making their boundary unclear. no_fake_done and trust_freeze are sequentially coupled but their distinct roles are not obvious from names alone, so an agent could easily misselect.

    Naming Consistency3/5

    All names use snake_case, but the patterns are mixed: land_inject is verb_noun, no_fake_done is a negation phrase, trust_freeze is noun_verb, and decide is a single verb. It is readable but not predictable.

    Tool Count4/5

    Four tools is a reasonable size for a specialized guardrail server. However, the overlap between land_inject and decide suggests some consolidation might be warranted.

    Completeness2/5

    The inferred domain is agent safety and enforcement, but there is no tool to unfreeze trust, check current state, or submit proof/receipts. These gaps could lead to deadlocks or agent failures.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues