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.814 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.17 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
- AlicenseAqualityBmaintenanceMCP server for healthcare claims workflow scoring, validation, and feedback, supporting denial risk, prior authorization, and reimbursement assessment.8MIT
mcp-reviewofficial
AlicenseAqualityBmaintenanceAn 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.52MIT
TDQS
A4.5/5.0
Scored across 12 tools
Disambiguation4/5
Most tools have clearly distinct lifecycle roles: start, advance, finish, renew, get, list, delete, prepare, and static policy/catalog lookups. The main possible confusion is among the three static/preparation tools (catalog, single-profile prepare, and bundle prepare), but their descriptions give enough guidance to distinguish them.
Naming Consistency4/5
The tools overwhelmingly follow a snake_case verb_noun pattern, mostly centered on qa_orchestration. Minor deviations include prepare_qa_orchestration vs. prepare_qa_orchestration_bundle, get_qa_orchestration_catalog/model_policy, list_qa_orchestrations plural form, and resolve_git_review_input outside the qa_orchestration prefix.
Tool Count5/5
Twelve tools are well-scoped for a QA orchestration lifecycle covering session creation, state advancement, finalization, deletion, renewal, listing, preparation, policy, catalog, and Git input resolution. Each tool appears to earn its place without excessive fragmentation.
Completeness5/5
The surface covers the full session lifecycle and supporting operations: start, advance, finish, renew, get, list, delete, plus static catalog/model-policy lookup and review-input preparation. It also handles stateless checklist preparation and Git diff resolution, leaving no obvious lifecycle gap.
Maintenance
ActivityActive
ResponsivenessNo recent community issues