updated 2026-11-10 04:07 UTC

.NET MCP Server

Repository

MCP wrapper for the .NET SDK

MCP Servers C# Listed MIT

Is .NET MCP Server safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 6.9 / 10
Provenance None
Signed commits 100%
Last push yesterday
Compare .NET MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: .NET MCP Server scores 64.0/100 (Grade C), ranked #571 of 1374 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 6.9/10; 100% of recent commits are signed; last pushed 2026-11-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How .NET MCP Server could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships .NET MCP Server and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Signed

    github.com/jongalloway/dotnet-mcp, MIT, last pushed 2026-11-09. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 6.9/10 (scanned Nov 8, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection3
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions7
    • Pinned Dependencies5
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 3
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 0
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 5
    SAST 10
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 7
    Vulnerabilities 10

  3. Published packages None

    No registry package. .NET MCP Server is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

  • 2026-08-26 OSSF Scorecard: 6.8/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues .NET MCP Server’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How .NET MCP Server compares in MCP Servers

  1. #322 Clarifyprompt MCP 64.1 +0.1
  2. #323 Glade MCP 64.1 +0.1
  3. #324 .NET MCP Server 64.0 this agent
  4. #325 Whoop MCP 63.9 −0.1
  5. #326 MCP Notion Server 63.9 −0.1

Bars show each HVTrust score; the tick marks .NET MCP Server’s 64.0.

Where the 64.0 comes from

HVTrust dimensions vs the MCP Servers average

64.0 / 100 · 100.0% confidence

.NET MCP Server MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
13.6 / 25
2.8 above avg 10.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.9 below avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
14.4 / 17
2.1 above avg 12.3
Maintenance60% last-push freshness · 40% commit activity
19.4 / 20
7.2 above avg 12.2
AdoptionLog-scaled stars · package downloads
3.8 / 20
3.8 below avg 7.6

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-11-06
Rank Moved
Rank rose 51 spots (#611 → #560)
2026-11-05
Rank Moved
Rank rose 13 spots (#624 → #611)
2026-11-02
Rank Moved
Rank rose 22 spots (#641 → #619)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.9/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Compare with another agent
View MCP Servers Report missing data
61.4
Activity sub-score · out of 100
#324
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-11-10 04:07 UTC · Repo last pushed yesterday

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
38
Forks
5
Last Push
2026-11-09
yesterday
Commits (4 wk)
73
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
17
Rank Change
▼4
was #567

Analysis

Activity Inputs

61.4 / 100
StarsRepository reach
9.5 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
23.3 / 25
CommunityFork signal
3.6 / 20

Common questions about .NET MCP Server

.NET MCP Server has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does .NET MCP Server publish package provenance?
No published build provenance is currently detected for .NET MCP Server. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does .NET MCP Server have an OpenSSF Scorecard?
.NET MCP Server has an OpenSSF Scorecard score of 6.9/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is .NET MCP Server actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does .NET MCP Server use?
.NET MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are .NET MCP Server's commits signed?
100% of the last 100 commits to .NET MCP Server are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
medium confidence
Implemented
.NET MCP Server appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to .NET MCP Server's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain .NET MCP Server?

For maintainers

HVTrust scores .NET MCP Server from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 27HVTrust 4Grade 2Score 2Scorecard 1Delisted 1Listed 1MCP 1
2026-11-06
Rank Moved
Rank rose 51 spots (#611 → #560)
2026-11-05
Rank Moved
Rank rose 13 spots (#624 → #611)
2026-11-02
Rank Moved
Rank rose 22 spots (#641 → #619)
2026-10-31
Rank Moved
Rank rose 143 spots (#791 → #648)
2026-10-31
HVTrust Changed
HVTrust up 4.6pts (57.0 → 61.6)
2026-10-31
Activity Score Changed
Activity score up 9pts (48 → 57)
2026-10-29
Rank Moved
Rank rose 144 spots (#944 → #800)
2026-10-29
HVTrust Changed
HVTrust up 4.4pts (52.4 → 56.8)
2026-10-29
Activity Score Changed
Activity score up 11pts (33 → 44)
2026-10-17
Rank Moved
Rank dropped 10 spots (#898 → #908)
2026-10-15
Rank Moved
Rank dropped 15 spots (#878 → #893)
2026-10-11
Rank Moved
Rank dropped 15 spots (#851 → #866)
2026-10-09
Rank Moved
Rank dropped 12 spots (#833 → #845)
2026-10-04
Rank Moved
Rank dropped 40 spots (#778 → #818)
2026-09-30
Rank Moved
Rank dropped 11 spots (#762 → #773)
2026-09-25
Rank Moved
Rank dropped 10 spots (#738 → #748)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank dropped 231 spots (#501 → #732)
2026-09-23
HVTrust Changed
HVTrust up 15.5pts (40.8 → 56.3)
2026-09-22
Newly Listed
First tracked at rank #501
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-08
Rank Moved
Rank dropped 11 spots (#697 → #708)
2026-09-05
Rank Moved
Rank dropped 78 spots (#618 → #696)
2026-09-04
Rank Moved
Rank dropped 21 spots (#597 → #618)
2026-09-03
Rank Moved
Rank dropped 40 spots (#557 → #597)
2026-09-02
Rank Moved
Rank dropped 19 spots (#538 → #557)
2026-09-01
Rank Moved
Rank dropped 12 spots (#526 → #538)
2026-08-31
Rank Moved
Rank dropped 31 spots (#495 → #526)
2026-08-29
Rank Moved
Rank dropped 24 spots (#476 → #500)
2026-08-27
Rank Moved
Rank dropped 13 spots (#456 → #469)
2026-08-26
Scorecard Added
OSSF Scorecard: 6.8/10
2026-08-26
Grade Changed
Trust grade D → C
2026-08-26
Rank Moved
Rank rose 545 spots (#1001 → #456)
2026-08-26
HVTrust Changed
HVTrust up 33.9pts (21.7 → 55.6)
2026-08-24
Rank Moved
Rank dropped 20 spots (#980 → #1000)
2026-08-17
Rank Moved
Rank rose 26 spots (#1009 → #983)
2026-08-16
Rank Moved
Rank dropped 38 spots (#971 → #1009)
2026-08-13
Rank Moved
Rank dropped 13 spots (#961 → #974)
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 64.0 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/net-mcp-server.svg)](https://hvtracker.net/agents/net-mcp-server)
HTML:
<a href="https://hvtracker.net/agents/net-mcp-server"><img src="https://hvtracker.net/badge/net-mcp-server.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON