io.github.felixgeelhaar/coverctl
MCPB · LINUX-X64 · 6 COMPONENTS
Go code coverage analysis tool with MCP server for AI-powered coverage workflows
Last scanned (19 hours ago)
Scores higher than 76% of MCPB servers
Category Testing and QA
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
Provenance & Transparency10
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 154 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 690 tokens (~98/item across 7 items; 3 tools + 4 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +1
- Stability: 0.97 → pass security
- 2 Nov 26 −1
- Stability: pass → 0.97 functional
- 1 Nov 26 +2
- Provenance: unverified → fail ▼ security
- Security disclosure: unverified → pass ▲ functional
- Maintenance: unverified → pass ▲ functional
- 31 Oct 26 0
- Security disclosure: pass → unverified ▼ functional
- 30 Oct 26 0
- Provenance: fail → unverified ▼ security
- 28 Oct 26 0
- Provenance: unverified → fail ▼ security
- 27 Oct 26 0
- Stability: 0.97 → pass security
- 26 Oct 26 −1
- Provenance: fail → unverified ▼ security
- Maintenance: pass → unverified ▼ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed mcpb/https://github.com/felixgeelhaar/coverctl/releases/download/v1.16.0/coverctl-mcp-linux-amd64.mcpb
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check ~378
Run the project's test suite with coverage and enforce per-domain policy thresholds defined in .coverctl.yaml. Auto-detects the language and invokes the appropriate test runner (go test, pytest, npm test, mvn, gradle, cargo, dotnet, etc.). Returns per-domain pass/fail, file-level coverage, and warnings. Exit-equivalent: passed=true on success, passed=false on policy violation or runner error.
| Name | Type | Req | Description |
|---|---|---|---|
| configPath | string | – | Path to .coverctl.yaml config file |
| domains | array | – | Filter to specific domains |
| failUnder | number | – | Fail if coverage below threshold |
| fromProfile | boolean | – | Use existing coverage profile instead of running tests |
| incremental | boolean | – | Only test packages with changed files |
| incrementalRef | string | – | Git ref to compare against for incremental mode (default: HEAD~1) |
| profile | string | – | Coverage profile output path |
| race | boolean | – | Enable race detector (Go-specific; ignored by other runners) |
| ratchet | boolean | – | Fail if coverage decreases |
| run | string | – | Run only tests matching pattern (Go: -run regex; pytest: -k expression; mapped per runner) |
| short | boolean | – | Skip long-running tests (Go: -short; other runners may have analogous flags) |
| tags | string | – | Build tags forwarded to the test runner (Go: -tags; other runners may ignore) |
| testArgs | array | – | Additional arguments forwarded to the test runner. MCP input is sanitized: flags that load arbitrary code (--rootdir |
| timeout | string | – | Test timeout in Go duration syntax (e.g. '10m' |
| verbose | boolean | – | Verbose test output |
| verbosity | string | – | Output detail: 'brief' (failing rows only |
No output schema declared.
No examples provided.
debt ~107
Compute coverage debt: the gap between current coverage and required thresholds, ranked per domain and per file. Returns a health score (0-100) and the items contributing the most debt. Use this to direct test-writing effort to the highest-impact gaps.
| Name | Type | Req | Description |
|---|---|---|---|
| configPath | string | – | Path to .coverctl.yaml config file |
| profile | string | – | Path to coverage profile |
| verbosity | string | – | Output detail: 'brief' | 'normal' (default) | 'verbose' |
No output schema declared.
No examples provided.
suggest ~144
Analyze current coverage and suggest threshold values for each domain. Strategies: 'current' (set thresholds slightly below current observed coverage to lock in the status quo), 'aggressive' (set targets above current to push improvement), 'conservative' (small incremental gains). Use writeConfig=true to apply suggestions; coverctl backs up the existing file first.
| Name | Type | Req | Description |
|---|---|---|---|
| configPath | string | – | Path to .coverctl.yaml config file |
| profile | string | – | Path to coverage profile |
| strategy | string | – | Suggestion strategy: current (default)|aggressive|conservative |
| writeConfig | boolean | – | Write suggested thresholds to config file (creates backup if file exists) |
No output schema declared.
No examples provided.
How do I install the io.github.felixgeelhaar/coverctl MCP server?
io.github.felixgeelhaar/coverctl ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. The MCP registry declares no SHA-256 for this bundle, so there is no published digest to check the download against.
mcpb · linux-x64
Download bundleThe MCP registry declares no SHA-256 for this bundle, so there is no published digest to check it against. Open it with an MCPB-capable host such as Claude Desktop.
What is the io.github.felixgeelhaar/coverctl MCP server?
io.github.felixgeelhaar/coverctl is an MCP server listed in the public MCP registry as io.github.felixgeelhaar/coverctl. Go code coverage analysis tool with MCP server for AI-powered coverage workflows. This page covers its MCPB bundle (https://github.com/felixgeelhaar/coverctl/releases/download/v1.16.0/coverctl-mcp-linux-amd64.mcpb).
Is the io.github.felixgeelhaar/coverctl MCP server safe to use?
io.github.felixgeelhaar/coverctl scores 46 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.felixgeelhaar/coverctl MCP server expose?
io.github.felixgeelhaar/coverctl exposes 3 tools: debt, check, suggest. Their descriptions and schemas cost roughly 629 tokens of context every time the server is loaded.