VibeGuard
Related Servers
Alternatives to VibeGuard
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceProvides a local-first MCP server for AI-native software delivery, enabling structured specifications, human approval gates, controlled repository operations, verification evidence, review, and traceability.Apache 2.0
- AlicenseBqualityDmaintenanceLocal MCP server providing project cognition capabilities for AI coding agents, including context packs, impact analysis, and git diff review through stdio communication.103MIT
- AlicenseNot gradedqualityAmaintenanceThis MCP server exposes a local structural code graph and project memory so AI coding agents can retrieve focused code entities, relationships, and prior mistakes before reading full files. It enables bounded context queries, caller/callee and impact analysis, and carryover of recorded session information through a CLI, hooks, and an authenticated local dashboard.24 npmMIT
- AlicenseNot gradedqualityAmaintenanceA local MCP server that enables AI coding agents and editors to run tests and save versioned, signed test receipts with required-test inventories, register newest-first undo commands with transactional rollback, and log agent-reported spending under a staged circuit breaker. It can also flag when later edits make a receipt stale so CI checks can gate on evidence labels.567 npmMIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that exposes guardrails for AI coding agents as tools, enabling clients to set task scopes, verify locked behaviors and snapshots, build repository context packs, and record decisions so changes stay within agreed boundaries.1,541 npmMIT
- AlicenseAqualityDmaintenanceA local-first, model-neutral MCP server for collecting and normalizing change-scoped release evidence. It provides deterministic Git change summaries, evidence collection, and review bundles for agent review.74 npmApache 2.0
TDQS
Scored across 4 tools
The four tools map cleanly to distinct stages: health is diagnostic, clarify produces a spec, review evaluates a diff against the spec, and test derives and runs targeted regression. There is no meaningful overlap between their purposes, and the workflow ordering is obvious.
All tool names are concise lowercase single words, which is consistent and readable. The only minor deviation is that health is a noun/state check while clarify, review, and test are action verbs.
Four tools is well-scoped for a spec-driven guard workflow: clarify, review, and test form the core pipeline, and health supports diagnostics. Each tool earns its place without obvious redundancy or missing stages.
The surface covers the full clarify → review → test lifecycle plus health, with sensible degradation behavior when no spec exists. Minor gaps remain around explicitly reading generated artifacts (spec.json, changes.json, test-results.json) or initializing/resetting configuration, though agents can likely work around these via the filesystem.