mcp-convention-gate
Related Servers
Alternatives to mcp-convention-gate
No user-submitted related servers found.
Related Servers
FlicenseAqualityAmaintenanceAI code review against your team's own rules from your repository, before the pull request: two tools, review_changes and get_team_rules. Closed-source binary distributed via GitHub Releases; published in the official MCP Registry as dev.reviewgate/reviewgate.2-- FlicenseBqualityCmaintenanceEnables secure, policy-controlled operations on local git repositories through MCP, including bounded reads, context-checked patches, allowlisted tasks, and guarded git operations.10-
- AlicenseAqualityAmaintenanceA trust-first repository copilot to audit signed commit provenance, preview editor configuration safety, and manage Git hook rollouts.135Apache 2.0
- AlicenseNot gradedqualityBmaintenanceA local-first, auditable code review MCP server that freezes Git changes, creates immutable ReviewBundles, provides role-isolated contexts for correctness, security, architecture, and test reviewers, validates structured findings, and generates deterministic JSON/Markdown reports.3 npm1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceProvides tools for agents to manage a local review graph, tracking acceptance behaviors, evidence, review passes, and human waivers to decouple review convergence from shipping readiness.3MIT
- AlicenseAqualityBmaintenanceProvides 18 tools for repository snapshot, release readiness, secret scanning, and approval-gated file writes with backup and audit log.18MIT
TDQS
Scored across 5 tools
Each tool targets a distinct phase of the gate workflow: session creation, gate registration, status inspection, commit logging, and listing. There is no meaningful overlap between tool purposes, and the guarded_commit description clearly differentiates it from actually running a commit.
create_gate_session, register_gate, and list_sessions follow a clean verb_noun pattern, but gate_status is a noun phrase and guarded_commit reads as an adjective_noun rather than an action. The naming is still readable and snake_case is consistent throughout, but the deviations are noticeable enough to lower the score.
Five tools is well-scoped for a focused gate-review workflow: create, register, check, log, and list. Each tool serves a necessary function in the lifecycle, and none feel redundant or ornamental.
The core workflow is covered end-to-end: session creation, gate registration, status verification, commit logging, and session listing. Minor gaps exist, such as no way to retrieve the detailed findings recorded during register_gate or to cancel/abort a session, but these do not block the primary gate-enforcement flow.