Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.Hyeonu-Cha/dotnet-coverage-mcp

NUGET · DOTNET-COVERAGE-MCP · SCANNED SEP 20

MCP server for .NET coverage: run tests, parse Cobertura, find uncovered branches, append tests.

Available components

nuget · dotnet-coverage-mcp 75
0 this week 75 Trust /100
Trust breakdown (7 categories)

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 Security100
  • 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
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency48
  • 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 67 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability51
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 505 tokens (~63/item across 8 items; 8 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
  • Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "cleanup_session" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 8 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
Install

How do I install the io.github.Hyeonu-Cha/dotnet-coverage-mcp server?

io.github.Hyeonu-Cha/dotnet-coverage-mcp runs locally as a NuGet package, launched with dnx dotnet-coverage-mcp@0.1.1 --yes. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

nuget · dotnet-coverage-mcp

# add to Claude Code
claude mcp add hyeonu-cha-dotnet-coverage-mcp -- dnx dotnet-coverage-mcp@0.1.1 --yes
// .cursor/mcp.json
{
  "mcpServers": {
    "hyeonu-cha-dotnet-coverage-mcp": {
      "command": "dnx",
      "args": [
        "dotnet-coverage-mcp@0.1.1",
        "--yes"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "hyeonu-cha-dotnet-coverage-mcp": {
      "command": "dnx",
      "args": [
        "dotnet-coverage-mcp@0.1.1",
        "--yes"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add hyeonu-cha-dotnet-coverage-mcp -- dnx dotnet-coverage-mcp@0.1.1 --yes
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "hyeonu-cha-dotnet-coverage-mcp": {
      "type": "local",
      "command": [
        "dnx",
        "dotnet-coverage-mcp@0.1.1",
        "--yes"
      ],
      "enabled": true
    }
  }
}
# ~/.hermes/config.yaml
mcp_servers:
  hyeonu-cha-dotnet-coverage-mcp:
    command: "dnx"
    args: ["dotnet-coverage-mcp@0.1.1", "--yes"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "hyeonu-cha-dotnet-coverage-mcp": {
      "Transport": "stdio",
      "Command": "dnx",
      "Arguments": [
        "dotnet-coverage-mcp@0.1.1",
        "--yes"
      ]
    }
  }
}
// mcp.json
{
  "mcpServers": {
    "hyeonu-cha-dotnet-coverage-mcp": {
      "command": "dnx",
      "args": [
        "dotnet-coverage-mcp@0.1.1",
        "--yes"
      ]
    }
  }
}
Changelog

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.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 17 Sept 26 +1
    • Stability: 0.97 → pass security
  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 10 Sept 26 +1
    • Stability: 0.97 → pass security
  • 8 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 20 Sept 2026 · Analysed nuget/dotnet-coverage-mcp@0.1.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem nuget
Reason Signature present, unreadable

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 8 exposed · ~505 tokens

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 →

Tool Tokens
append_test_code ~72

Insert C# code into a test file via Roslyn AST (string fallback). Pass `insertAfterAnchor` to target a position; omit to append inside the last class.

NameTypeReqDescription
codeToAppendstringyes–
insertAfterAnchorstring|null––
testFilePathstringyes–

No output schema declared.

No examples provided.

cleanup_session ~68

Remove session state files and TestResults/coveragereport directories. Pass `sessionId` to scope, or omit to clean artifacts older than `maxAgeMinutes`.

NameTypeReqDescription
maxAgeMinutesinteger––
sessionIdstring|null––
workingDirstringyes–

No output schema declared.

No examples provided.

get_coverage_diff ~59

Diff current coverage against the saved baseline (method-level changes, including added/removed). Updates the baseline afterwards.

NameTypeReqDescription
coberturaXmlPathstringyes–
sessionIdstring|null––
workingDirstring|null––

No output schema declared.

No examples provided.

get_coverage_summary ~35

Parse Summary.json into class/method coverage data, sorted by branch coverage ascending.

NameTypeReqDescription
summaryJsonPathstringyes–

No output schema declared.

No examples provided.

get_file_coverage ~76

Per-file class/method coverage from Cobertura XML. `allMeetTarget` is true when every class meets `targetRate` for line and branch.

NameTypeReqDescription
coberturaXmlPathstringyes–
sessionIdstring|null––
sourceFileNamestringyes–
targetRatenumber––

No output schema declared.

No examples provided.

get_source_files ~50

Discover .cs files from a file/folder/.csproj/comma-separated list and group into batches sized by `lineBudget`.

NameTypeReqDescription
lineBudgetinteger––
pathstringyes–

No output schema declared.

No examples provided.

get_uncovered_branches ~56

List uncovered branches for methods matching `methodName` in Cobertura XML (partial match supported).

NameTypeReqDescription
coberturaXmlPathstringyes–
methodNamestringyes–
sessionIdstring|null––

No output schema declared.

No examples provided.

run_tests_with_coverage ~89

Run `dotnet test` with XPlat Code Coverage and generate a JSON summary. Returns paths to Summary.json and Cobertura XML.

NameTypeReqDescription
filterstringyes–
forceRestoreboolean––
includeClassstring|null––
sessionIdstring|null––
testProjectPathstringyes–
workingDirstring|null––

No output schema declared.

No examples provided.

Common questions

What is the io.github.Hyeonu-Cha/dotnet-coverage-mcp server?

io.github.Hyeonu-Cha/dotnet-coverage-mcp is listed in the public MCP registry as io.github.Hyeonu-Cha/dotnet-coverage-mcp. MCP server for .NET coverage: run tests, parse Cobertura, find uncovered branches, append tests. This page covers its NuGet package (dotnet-coverage-mcp).

Is the io.github.Hyeonu-Cha/dotnet-coverage-mcp server safe to use?

io.github.Hyeonu-Cha/dotnet-coverage-mcp scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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.Hyeonu-Cha/dotnet-coverage-mcp server expose?

io.github.Hyeonu-Cha/dotnet-coverage-mcp exposes 8 tools: get_coverage_diff, cleanup_session, get_uncovered_branches, get_coverage_summary, append_test_code, and 3 more. Their descriptions and schemas cost roughly 505 tokens of context every time the server is loaded.

Is the io.github.Hyeonu-Cha/dotnet-coverage-mcp server still maintained?

io.github.Hyeonu-Cha/dotnet-coverage-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 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.Hyeonu-Cha/dotnet-coverage-mcp server under?

io.github.Hyeonu-Cha/dotnet-coverage-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.