A
licenseA
qualityC
maintenanceEnables AI coding agents to submit work for external review before declaring a task done, receiving evidence-backed fix lists and verdicts based on git-measured changes and calibrated quality scoring.
3
MIT
BlindReview MCP
Related Servers
Alternatives to BlindReview MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI-assisted coding workflows to validate code changes through an adversarial debate between the coding agent and a critic LLM, surfacing only deadlocked decisions for human review.93 npm1MIT
gossipcatofficial
AlicenseNot gradedqualityAmaintenanceEnables multi-agent code review with cross-verification of findings against source code, catching hallucinations and improving agent accuracy over time.126 npm41MIT- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to call real human reviewers for mid-task feedback, publishing work artifacts so reviewers can pin issues and return verdicts that guide iterative revisions until approval.38 npmMIT
- AlicenseNot gradedqualityAmaintenancePanel Review is the guardian agent for AI's highest-stakes coding decisions. Before an agent's riskiest designs, diffs, or commits ship, four frontier models, from OpenAI, Anthropic, Google, and xAI, argue them through and return severity-tagged findings, with review gates the agent cannot silently skip.15 npm2MIT
- AlicenseAqualityDmaintenanceAdversarial review system that spawns three independent contrarian reviewers to catch issues before AI coding agents execute critical changes.33 npmMIT
TDQS
A4/5.0
Scored across 3 tools
Disambiguation5/5
The three tools serve clearly distinct roles: review_decision performs the review, should_review is a deterministic gate, and record_outcome is telemetry. No overlap in purpose or output.
Naming Consistency4/5
All names use snake_case, but the pattern is not uniform: review_decision and record_outcome are verb_noun, while should_review is a modal-verb question form. Minor deviation but still readable.
Tool Count5/5
Three tools is well-scoped for a focused review workflow; each tool has a clear, non-redundant purpose. No bloat or missing essentials.
Completeness4/5
The core lifecycle (should_review → review_decision → record_outcome) is covered. A minor gap exists: no tool to list or retrieve past reviews/outcomes, but telemetry is append-only and the main workflow has no dead ends.
Maintenance
ActivityMaintained
ResponsivenessNo issues