codapult-guard
OfficialRelated Servers
Alternatives to codapult-guard
No user-submitted related servers found.
Related Servers
- AlicenseCqualityDmaintenanceArchitectural Gatekeeper for AI coding. Prevents "tunnel vision" bugs by forcing the AI to verify dependencies (via AST parsing) before editing files. Supports JavaScript & TypeScript. Blocks unsafe edits until the AI proves it understands the impact3Apache 2.0
- AlicenseAqualityBmaintenanceFast architectural linter & guardrail engine for AI coding agents. Detects layer violations, leaked secrets, and enforces .cursorrules & CLAUDE.md standards in ~12ms.420 npm5MIT
- AlicenseAqualityDmaintenanceGuardrails for AI coding agents that enforces rules via compliance receipts, blocking destructive actions and syncing rules across all AI tools.2483 npm1MIT
- AlicenseAqualityBmaintenanceEnforces AST-based architectural guardrails on AI-generated code, blocking writes that violate maintainability, security, or complexity rules and prompting immediate refactoring.2MIT
- AlicenseNot gradedqualityCmaintenanceReal-time architecture governance tool that enforces Clean Architecture, DDD, SOLID, TDD, and Security rules across 8 languages using 11 specialized agents.1 npmMIT
- AlicenseAqualityAmaintenanceAgentGuard47 is runtime safety infrastructure for AI agents. It adds budget caps, loop detection, retry limits, timeouts, local traces, and incident reports so agents can stop bad runs while they are happening, not just explain them afterward.74MIT
TDQS
Scored across 14 tools
Most tools have distinct purposes (init, propose, proposal_decide, waivers, impact, explain), but the verification cluster—verify, check, and audit—overlaps significantly, with descriptions distinguishing them only subtly (build gate vs architecture rules vs full audit). Similarly, next_action, review, and analyze all produce or refresh bounded agent-facing context, creating some boundary confusion.
All 14 tools share a uniform lowercase snake_case `codapult_guard_` prefix, which is highly predictable. Slight inconsistency arises from mixing bare verbs (init, verify, propose, audit, check, review, explain, analyze) with noun forms (context, governance, waivers, impact, next_action, proposal_decide), but the pattern remains readable.
14 tools sits comfortably in the well-scoped 3-15 range and maps to discernible workflow stages (discover, init, propose, decide, verify, audit, review, manage waivers). No tool appears redundant enough to trim, and none of the surface feels padded.
The lifecycle is largely covered: discovery (context), initialization (init), rule proposal and approval (propose/proposal_decide), enforcement (verify/check/audit), review (review), exceptions (waivers), and introspection (impact, explain, governance, analyze). Minor gaps exist—no explicit reset/teardown of Guard artifacts and waiver management is a single bundled tool rather than discrete list/create/remove operations.