A
licenseA
qualityB
maintenanceEnables code-review gating by converting a git diff into a typed verdict with safety probabilities, severity, and recommended actions for auto-merge or human review.
1
1
MIT
QA Orchestrator
by Rbkmen
Related Servers
Alternatives to QA Orchestrator
Related Servers
- AlicenseAqualityCmaintenanceA self-hosted MCP server offering provider-independent AI routing, deterministic verification, and cryptographically signed, tamper-evident audit trails for every response.831 npm2MIT
- FlicenseAqualityFmaintenanceA local MCP server for governed support-ticket triage that reads synthetic tickets and knowledge articles, prepares evidence-backed recommendations, and records local audit events.9-
- AlicenseCqualityDmaintenanceAn MCP server that guides QA and verification processes by breaking down tasks into manageable steps and providing LLM-driven, confidence-scored tool recommendations.112 npm6MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that brings a local MLX-powered decision layer to coding agents, letting them choose short workflow actions such as task routing, risk checks, next steps, and test/review decisions without cloud APIs.Apache 2.0
- AlicenseAqualityCmaintenanceMCP server for healthcare claims workflow scoring, validation, and feedback, supporting denial risk, prior authorization, and reimbursement assessment.838 PyPIMIT
mcp-reviewofficial
AlicenseAqualityAmaintenanceAn MCP server for in-loop design review of web previews. It enables agents to submit a preview URL, receive structured findings with suggested fixes, and recheck after applying changes, while never editing code itself.51MIT
TDQS
A4.7/5.0
Scored across 5 tools
Disambiguation4/5
The five tools map to distinct lifecycle stages (prepare=stateless lookup, start=create session, advance=progress step, finish=terminal outcome, get=read state). The main risk is confusing prepare_qa_orchestration with start_qa_orchestration, but the descriptions explicitly disambiguate by stressing prepare is stateless and never creates a session. advance vs finish is also clarified by tying finish to the awaiting_host_outcome terminal state.
Naming Consistency5/5
All five tools follow a strict verb_qa_orchestration pattern: start_, prepare_, advance_, finish_, get_. The convention is uniform across the entire set with no deviations or mixed casing.
Tool Count5/5
Five tools is a tight, well-scoped set that exactly covers a session lifecycle plus a stateless helper. Each tool earns its place with no redundancy or padding.
Completeness4/5
The surface covers the full lifecycle (create, stateless lookup, progress, read, terminal finalize) and handles early stops. Minor gap: there is no explicit list/abort/cancel operation, though early stop is folded into advance + finish, so agents can still work around it.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive