MCP.Market

Dotnet Coverage MCP server

by Hyeonu-Cha·io.github.Hyeonu-Cha/dotnet-coverage-mcp·v0.1.1·1 stars
No reviews yet

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

A88/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A88/100

full report

Adoption
New

1 stars

Reviews

Write one

Nobody has reviewed Dotnet Coverage yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Dotnet Coverage tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • –Code scanpackage could not be scannedn/a
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 7 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Dotnet Coverage compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
88/100
higher than 75% of 48,255 servers
GitHub stars
1
more than 65% of 28,688 servers

Install Dotnet Coverage in Claude Code, Cursor or VS Code

The registry entry has no remote endpoint or installable package.

What the publisher says

From the Dotnet Coverage repository's README, as published. We do not edit it. Read it on GitHub

dotnet-coverage-mcp

<!-- mcp-name: io.github.Hyeonu-Cha/dotnet-coverage-mcp -->

An MCP (Model Context Protocol) server that gives AI assistants — Claude Code, Gemini CLI, and others — direct access to .NET test-coverage tooling. Run dotnet test, parse Cobertura XML, identify uncovered branches, diff coverage between runs, and append test code — all over stdio.

Purpose

This server lets an AI assistant run unit tests, collect coverage data, and analyse results — all without leaving the chat. Instead of manually running dotnet test and parsing reports, the AI can call the server's tools directly to:

  • Discover source files and build smart batches by line budget
  • Run a filtered set of tests and collect coverage
  • Read compact, AI-optimised coverage summaries (method-level line/branch rates)
  • Check per-file coverage against a configurable target rate (default 80%)
  • Identify uncovered branches as structured JSON
  • Diff coverage between runs to see only what changed
  • Append new test code to an existing test file with atomic writes

How It Works

The server starts as a console process and communicates over stdio using the MCP protocol. An MCP-compatible client (Claude Code, Gemini CLI, etc.) launches the process and calls its tools as if they were functions.

AI Client  <--stdio/MCP-->  dotnet-coverage-mcp  <--shell-->  dotnet test + reportgenerator

Available Tools

Batch Workflow

For projects with many source files, the recommended workflow is:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Dotnet Coverage: common questions

Is Dotnet Coverage MCP server safe?
Yes, by our scan: it is graded A (88/100). Read the Dotnet Coverage safety report
Does Dotnet Coverage need an API key?
No secret keys are declared. It reads 2 settings from the environment.
Is Dotnet Coverage maintained?
The last commit was 45 days ago (2026-09-20). The latest release is v0.1.1.
How does Dotnet Coverage compare with other MCP servers?
safety score 88/100 (higher than 75% of 48,255 servers); github stars 1 (more than 65% of 28,688 servers). Full comparison.