Aegis Guardrails
Related Servers
Alternatives to Aegis Guardrails
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables 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.2MIT
- AlicenseNot gradedqualityAmaintenanceAI 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.112 npm25MIT
- AlicenseNot gradedqualityFmaintenanceGovernance 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.74MIT
- AlicenseNot gradedqualityAmaintenanceAn MCP server that enforces repository governance rules for AI coding agents, providing tools to validate plans, diffs, and scan for architectural and safety violations.1MIT
- AlicenseNot gradedqualityDmaintenanceRuntime safety guardrails for AI coding agents. Checks file access, validates shell commands, and scores your repo's AI safety — all via MCP.6 npm8MIT
- AlicenseNot gradedqualityBmaintenanceStandardize 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 verificationMIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: capture_insight records corrections, create_rule drafts a rule, list_rules enumerates rules, report_outcome provides feedback, and scan retrieves applicable rules. No two tools perform the same action, so an agent can easily select the right one.
All tools share the aegis_ prefix and follow a verb_noun pattern except aegis_scan, which is verb-only. This minor deviation keeps the set readable and predictable.
Five tools is well within the ideal range and each covers a distinct part of the governance workflow: insight capture, rule creation, rule listing, outcome reporting, and rule scanning. There is no redundancy.
The surface lacks tools to persist, update, or delete rules—create_rule explicitly writes nothing, and there is no edit or delete operation. While listing and scanning provide read access, the lifecycle is incomplete, forcing manual file operations.