io.github.goldbergyoni/test-coverage-mcp
NPM · TEST-COVERAGE-MCP · SCANNED AUG 3
Analyze test coverage from LCOV files - makes AI agents coverage-aware without wasting tokens
Available components
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 →
Supply Chain Security70
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.20.2, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (90 of 94), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency44
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 268 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 143 tokens (~35/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · test-coverage-mcp
claude mcp add goldbergyoni-test-coverage-mcp -- npx -y test-coverage-mcp
codex mcp add goldbergyoni-test-coverage-mcp -- npx -y test-coverage-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"goldbergyoni-test-coverage-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"test-coverage-mcp"
],
"enabled": true
}
}
} openclaw mcp add goldbergyoni-test-coverage-mcp --command npx --arg -y --arg test-coverage-mcp
mcp_servers:
goldbergyoni-test-coverage-mcp:
command: "npx"
args: ["-y", "test-coverage-mcp"] {
"mcpServers": {
"goldbergyoni-test-coverage-mcp": {
"command": "npx",
"args": [
"-y",
"test-coverage-mcp"
]
}
}
} 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 Aug 26 +4
- Stability: unverified → 0.27 ▲ functional
- 2 Aug 26 +53
- CVE-2026-25536 affects this package: high ▼ security
- CVE-2025-66414 affects this package: high ▼ security
- CVE-2026-0621 affects this package: high ▼ security
- Known CVEs: unverified → fail ▼ security
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- MCP protocol: unverified → fail ▼ functional
- Schema quality: unverified → excellent ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- License: unverified → pass ▲ functional
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Licence: MIT functional
- 1 Aug 26 −2
- Dependency health: partial → unverified ▼ functional
- 31 Jul 26 −39
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 46
First indexed and scored.
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Vulnerabilities 3 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-345p-7cg4-v4c7 | CVE-2026-25536 | high | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N | yes |
| GHSA-8r9q-7v3j-jr4g | CVE-2026-0621 | high | yes | |
| GHSA-w48q-cv73-mx4w | CVE-2025-66414 | high | yes |
Dependencies 90 packages
90 packages in the resolved dependency tree · 89 deprecated · 30 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
coverage_file_summary ~36
Analyzes an LCOV coverage file and returns line coverage percentage for a specific file. Use this to check coverage for individual files.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
coverage_summary ~41
Analyzes an LCOV coverage file and returns overall project line coverage percentage. Use this before making code changes to establish a baseline or after changes to verify impact.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_diff_since_start ~37
Compares current coverage against the recorded baseline and returns the impact (positive or negative). Use this after making changes to see coverage impact.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
start_recording ~29
Records the current coverage as a baseline snapshot. Use this before making code changes to later compare against.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.