Review Gate
OfficialRelated Servers
Alternatives to Review Gate
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceSelf-hosted MCP engine for private code reviews, providing deterministic static analysis and AST-level search over diffs, with findings passed to a review agent of your choice.52AGPL 3.0
- FlicenseNot gradedqualityBmaintenancePolicy-as-code gate for AI-SDLC, providing MCP tools to review prompts, diff tool manifests, vet MCP servers, and run evaluation suites for LLM agent repos.1-
- AlicenseAqualityBmaintenanceDeterministic code review MCP server that provides tools for file selection, rule matching, comment positioning, and reflection, ensuring stable review quality without LLM calls.516 npm1MIT
- AlicenseNot gradedqualityCmaintenanceOpen-source AI code review MCP server for local git diff auditing with deterministic security rules and AI-powered analysis using any OpenAI-compatible model.4MIT
- FlicenseAqualityCmaintenanceAI-powered code review tool that detects AI-generated code defects invisible to traditional linters — hallucinated packages, deprecated APIs, cross-file contradictions, hidden security anti-patterns, and over-engineering. Works as a standalone CLI, GitHub Action, or MCP server. Supports TypeScript, Python, Java, Go, and Kotlin. Free for individuals, no API key required.439-
- AlicenseNot gradedqualityAmaintenanceAI code reviews and git activity digests with machine-readable risk scoring, available as an MCP server for use within an agent session.1MIT
TDQS
Scored across 2 tools
The two tools have entirely distinct roles: one retrieves team standards, the other evaluates changes against them. There is no overlap or ambiguity in their purposes.
Both tools follow a clear verb_noun pattern: get_team_rules and review_changes. The naming is consistent, predictable, and reflects their actions accurately.
With only two tools, the set feels thin even though the server's purpose is narrowly focused on code-review gating. It is borderline but defensible for a single-purpose integration.
The tool surface covers the full core workflow: fetch the team's standards before implementing, then review changes before push. The review tool itself handles iteration and reporting, so there are no obvious dead ends for the stated domain.