covera-mcp
OfficialRelated Servers
Alternatives to covera-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to run tests and inspect Windows C++ coverage without rebuilding, rank and read uncovered code, add targeted tests, and query or merge coverage databases.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceMCP server that provides instant, token-efficient test coverage data for any programming language, allowing agents to query coverage summaries and track session progress.65 npm42MIT
- FlicenseNot gradedqualityAmaintenanceEnables coding agents to coordinate profilers, benchmark tools, trace processors, and direct local targets so that explicit artifacts or commands become bounded runtime evidence with recorded provenance, coverage, and limitations. Its analysis and capture tools require no workspace setup, and durable evidence preservation remains optional.-
- AlicenseNot gradedqualityBmaintenanceEnables local repository analysis to find untested functions, link tests to code, record passing runs as proof, and calculate a combined coverage score through MCP tools.298 npmMIT
- FlicenseNot gradedqualityAmaintenanceEnables coding agents to capture and analyze bounded runtime evidence from explicit artifacts or commands, coordinating profilers, benchmark tools, trace processors, and local targets for hotspot investigation.-
- AlicenseAqualityBmaintenanceEnables users to build and continuously refresh a code index of a repository, then query it to answer architecture, impact, tracing and log questions with verifiable evidence lines. Also checks Java, Kotlin and TypeScript/JavaScript names against real sources and classpaths, and supports commit review and Minecraft/JVM analysis directly from an agent session.51Apache 2.0
TDQS
Scored across 11 tools
Most tools map to distinct steps, but covera_recovery_start and covera_recovery_collect overlap heavily — start explicitly says it can 'collect the latest from the server' and record state, which is what collect does, so an agent may not know which to call. The three read-only diagnostics (covera_doctor, covera_recovery_discover, covera_recovery_inspect) also sit close together, distinguished mainly by prose rather than by name.
All tools share the `covera_` prefix and snake_case, with recognizable subgroups (`covera_recovery_*`, `covera_coverage_*`). Minor deviations exist: covera_doctor is a bare noun with no verb, and covera_get_guide breaks the sub-domain grouping used elsewhere.
11 tools is well within a comfortable range for a server spanning two workflows (coverage build/measure and PA error recovery). Each tool corresponds to a recognizable step, and none feel like filler, aside from the mild redundancy between start and collect.
The recovery lifecycle is nearly end-to-end (discover → start/collect → inspect → verify → plan → publish) and the build side covers guide → build → measure. Gaps are minor but real: no way to abort/stop a running build, no rollback or un-publish after covera_recovery_publish, and no tool to enumerate cases or runs beyond inspecting a single case.