coverage-orchestrator-mcp
Related Servers
Alternatives to coverage-orchestrator-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityCmaintenanceEnables coverage-driven test generation for RHDH plugin forests by analyzing git diffs and coverage reports, recommending the cheapest test layer, and emitting actionable test briefs, including Playwright MCP prompts for UI gaps.10-

OrangePro MCPofficial
AlicenseAqualityAmaintenanceAnalyzes code to map behaviors, identify untested gaps, and generate grounded integration tests that actually run.151,071 npm17MIT- FlicenseAqualityDmaintenanceWraps existing test frameworks (Jest, Vitest, Pytest) and exposes structured, LLM-optimized results via MCP tools with progressive disclosure and diff-aware execution.111-
- AlicenseDqualityDmaintenanceMCP server for deterministic local test execution and normalized test result reporting, supporting pytest and Jest with coverage summaries.6MIT

openhonest-umbraofficial
AlicenseAqualityAmaintenanceAudits a module against its test suite and reports the cases the tests are structurally unable to see, then proves each gap with a real failing test rather than a warning. Covers Python, TypeScript, JavaScript, Java, Rust and Go.43Apache 2.0- FlicenseNot gradedqualityDmaintenanceAutomates Java/Maven test generation, JaCoCo coverage analysis, and Checkstyle checking through MCP tools. Enables iterative improvement of test coverage and code style until quality goals are met.1-
TDQS
Scored across 5 tools
Each tool has a clear, distinct purpose: setup, fetching uncovered code, running tests, verifying targets, and orchestrating improvements. No two tools serve overlapping functions.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., ensure_coverage_setup, fetch_uncovered_code, verify_coverage_target), making them predictable and easy to differentiate.
Five tools is appropriate for a coverage orchestration server, covering the essential workflow without unnecessary complexity. The scope is well-defined.
The tool set covers the full lifecycle: setup, running tests, fetching uncovered code, verification against thresholds, and orchestration of iterative improvements. No obvious gaps for the intended purpose.