io.github.egulatee/codecov
NPM · MCP-SERVER-CODECOV
MCP server for querying Codecov coverage data with configurable URL support
Available components
Last scanned (23 hours ago)
Scores higher than 99% of npm 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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency94
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to egulatee/mcp-server-codecov). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Maintenance check failed: the publisher has marked this version as deprecated on the registry, telling users to stop installing it. See how to fix → Fail
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 295 tokens (~42/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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 4 Nov 26 +1
- Stability: 0.97 → pass security
- 3 Nov 26 −1
- Stability: pass → 0.97 functional
- 28 Oct 26 +1
- Stability: 0.97 → pass security
- 27 Oct 26 −1
- Stability: pass → 0.97 functional
- 21 Oct 26 +1
- Stability: 0.97 → pass security
- 20 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +3
- Stability: 0.83 → pass security
- 15 Oct 26 −3
- Stability: pass → 0.80 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 npm/mcp-server-codecov@1.1.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | egulatee/mcp-server-codecov |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/egulatee/mcp-server-codecov/.github/workflows/release.yml@refs/tags/v1.1.0 |
| Rekor log index | 774842058 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:3e2416dce524b3cb490334a36567a625024093c862adf2554ab5b16c43e1cffbf5c59d4c7482246f2c81d7a3ead63df41bc6d1a507296535d77c3097a |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
get_commit_coverage ~63
Get coverage data for a specific commit, including overall coverage percentage and file-level changes.
| Name | Type | Req | Description |
|---|---|---|---|
| commit_sha | string | yes | Commit SHA to get coverage for |
| owner | string | yes | Repository owner (username or organization) |
| repo | string | yes | Repository name |
No output schema declared.
No examples provided.
get_file_coverage ~105
Get line-by-line coverage data for a specific file in a repository. Returns coverage percentages and line-level hit/miss information.
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | Path to the file within the repository (e.g., 'src/index.ts') |
| owner | string | yes | Repository owner (username or organization) |
| ref | string | – | Git reference (branch, tag, or commit SHA). Defaults to default branch if not specified. |
| repo | string | yes | Repository name |
No output schema declared.
No examples provided.
get_repo_coverage ~62
Get overall coverage statistics for a repository, optionally for a specific branch.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | Branch name (defaults to repository's default branch) |
| owner | string | yes | Repository owner (username or organization) |
| repo | string | yes | Repository name |
No output schema declared.
No examples provided.
How do I install the io.github.egulatee/codecov MCP server?
io.github.egulatee/codecov runs locally as an npm package, launched with npx -y mcp-server-codecov. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcp-server-codecov
claude mcp add egulatee-codecov -- npx -y mcp-server-codecov
What is the io.github.egulatee/codecov MCP server?
io.github.egulatee/codecov is an MCP server listed in the public MCP registry as io.github.egulatee/codecov. MCP server for querying Codecov coverage data with configurable URL support. This page covers its npm package (mcp-server-codecov).
Is the io.github.egulatee/codecov MCP server safe to use?
io.github.egulatee/codecov scores 96 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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.egulatee/codecov MCP server expose?
io.github.egulatee/codecov exposes 3 tools: get_file_coverage, get_commit_coverage, get_repo_coverage. Their descriptions and schemas cost roughly 230 tokens of context every time the server is loaded.
Is the io.github.egulatee/codecov MCP server still maintained?
io.github.egulatee/codecov is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.egulatee/codecov MCP server under?
io.github.egulatee/codecov declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.