Skip to main content
Glama

Related Servers

Alternatives to Aegis Guardrails

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables AI coding assistants to enforce repository rules and block unauthorized file edits or commands, even after context compaction, by running as a local zero-config MCP server.
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      AI Constraint Engine that enforces CLAUDE.md, .cursorrules, and AGENTS.md rules as laws. 51 MCP tools for semantic conflict detection, patch review, drift scoring, pre-commit hooks, and Guardian Mode. Catches euphemisms, temporal evasion, and hidden violations that keyword matching misses.
      137 npm
      26
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      Governance kernel for AI agents — policy enforcement, code safety verification, multi-model hallucination detection (CMVK), trust attestation (IATP), and immutable audit trails. Works with Claude Desktop, Cursor, and any MCP client.
      74
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enforces repository governance rules for AI coding agents, providing tools to validate plans, diffs, and scan for architectural and safety violations.
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Standardize Context, Not Intelligence. An open protocol and native MCP server for preserving, organizing, and serving structured project context (architecture, decision logs, domain rules, and roadmap) to AI coding assistants (Cursor, Claude Desktop, Antigravity) with built-in CLI verification
      MIT

    TDQS

    A4.1/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool has a distinct role, and the descriptions explicitly resolve the two potential overlaps (aegis_scan vs aegis_list_rules, aegis_report_outcome vs aegis_capture_insight) by stating which one records state. The only residual confusion is that scan and list_rules both return rule sets, so an agent must read the fine print to pick correctly.

    Naming Consistency4/5

    All names share the aegis_ prefix and follow a verb_noun pattern (create_rule, list_rules, report_outcome, capture_insight), with aegis_scan as the single verb-only deviation. Readable and predictable overall.

    Tool Count5/5

    Five tools map cleanly onto the guardrails workflow: browse rules, generate a new rule, scan before editing, report verification outcome, and capture user corrections. Nothing appears redundant or padded at this size.

    Completeness3/5

    The rule lifecycle is incomplete: there is no tool to read, update, retire, or delete an existing rule (aegis_create_rule only builds a prompt and writes nothing), and captured insights cannot be reviewed or dismissed by the agent. These are notable gaps an agent would hit when maintaining rules, though core scan/report flows are covered.

    Maintenance

    ActivityActive
    ResponsivenessUsually handled