updated 2026-11-10 04:07 UTC

ASP.NET Core Debugger — MCP Server for AI Agents

Repository

MCP server that lets AI agents (Claude, Cursor) debug your .NET / ASP.NET Core app

MCP Servers C# Listed MIT

Is ASP.NET Core Debugger — MCP Server for AI Agents safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4.2 / 10
Provenance None
Signed commits 42%
Last push 57d ago
Compare ASP.NET Core Debugger — MCP Server for AI Agents

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: ASP.NET Core Debugger — MCP Server for AI Agents scores 43.4/100 (Grade D), ranked #1150 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 4.2/10; 42% of recent commits are signed; last pushed 2026-09-14. Every point is earned from checkable signals — never paid placement. How scoring works →

How ASP.NET Core Debugger — MCP Server for AI Agents 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 ASP.NET Core Debugger — MCP Server for AI Agents 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 Partly signed

    github.com/magna-nz/aspnetcore-debugger-mcp, MIT, last pushed 2026-09-14. 42% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

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

    • Code Review1
    • Branch Protection6
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 6
    CI-Tests 8
    CII-Best-Practices 0
    Code-Review 1
    Contributors 0
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 6
    Packaging 10
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 10

  3. Published packages None

    No registry package. ASP.NET Core Debugger — MCP Server for AI Agents 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: 4.4/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 ASP.NET Core Debugger — MCP Server for AI Agents’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 ASP.NET Core Debugger — MCP Server for AI Agents compares in MCP Servers

  1. #656 Kronan MCP 43.6 +0.2
  2. #657 Smart Thinking 43.5 +0.1
  3. #658 ASP.NET Core Debugger — MCP Server for AI Agents 43.4 this agent
  4. #659 Ux MCP Server 43.1 −0.3
  5. #660 Apple Docs MCP 43.1 −0.3

Bars show each HVTrust score; the tick marks ASP.NET Core Debugger — MCP Server for AI Agents’s 43.4.

Where the 43.4 comes from

HVTrust dimensions vs the MCP Servers average

43.4 / 100 · 100.0% confidence

ASP.NET Core Debugger — MCP Server for AI Agents MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.4 / 25
3.4 below 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
12.1 / 17
in line with avg 12.3
Maintenance60% last-push freshness · 40% commit activity
8.2 / 20
4.0 below avg 12.2
AdoptionLog-scaled stars · package downloads
2.9 / 20
4.7 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-10-14
Rank Moved
Rank dropped 51 spots (#1055 → #1106)
2026-10-14
Activity Score Changed
Activity score down 6pts (38 → 31)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.2/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.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Refresh maintenance signals The repo was last pushed 57 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent
View MCP Servers Report missing data
27.7
Activity sub-score · out of 100
#658
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 D 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 57 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
15
Forks
4
Last Push
2026-09-14
57 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
0
Rank Change
▼1
was #1149

Analysis

Activity Inputs

27.7 / 100
StarsRepository reach
7.2 / 30
FreshnessLast push recency
17.1 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
3.3 / 20

Common questions about ASP.NET Core Debugger — MCP Server for AI Agents

Public trust evidence for ASP.NET Core Debugger — MCP Server for AI Agents is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does ASP.NET Core Debugger — MCP Server for AI Agents publish package provenance?
No published build provenance is currently detected for ASP.NET Core Debugger — MCP Server for AI Agents. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does ASP.NET Core Debugger — MCP Server for AI Agents have an OpenSSF Scorecard?
ASP.NET Core Debugger — MCP Server for AI Agents has an OpenSSF Scorecard score of 4.2/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 ASP.NET Core Debugger — MCP Server for AI Agents actively maintained?
Slowing down. Last push was 57 days ago — keep an eye on whether activity resumes.
What license does ASP.NET Core Debugger — MCP Server for AI Agents use?
ASP.NET Core Debugger — MCP Server for AI Agents ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are ASP.NET Core Debugger — MCP Server for AI Agents's commits signed?
42% of the last 100 commits to ASP.NET Core Debugger — MCP Server for AI Agents 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
ASP.NET Core Debugger — MCP Server for AI Agents 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 ASP.NET Core Debugger — MCP Server for AI Agents'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 ASP.NET Core Debugger — MCP Server for AI Agents?

For maintainers

HVTrust scores ASP.NET Core Debugger — MCP Server for AI Agents 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 27Score 4HVTrust 3Grade 2Scorecard 1Delisted 1Listed 1MCP 1
2026-10-14
Rank Moved
Rank dropped 51 spots (#1055 → #1106)
2026-10-14
Activity Score Changed
Activity score down 6pts (38 → 31)
2026-10-09
Rank Moved
Rank dropped 16 spots (#1019 → #1035)
2026-10-08
Rank Moved
Rank dropped 45 spots (#974 → #1019)
2026-10-08
Activity Score Changed
Activity score down 5pts (44 → 38)
2026-10-05
Grade Changed
Trust grade C → D
2026-09-30
Rank Moved
Rank dropped 13 spots (#936 → #949)
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 373 spots (#534 → #907)
2026-09-23
HVTrust Changed
HVTrust up 12.5pts (38.3 → 50.8)
2026-09-22
Newly Listed
First tracked at rank #534
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-20
Rank Moved
Rank dropped 10 spots (#943 → #953)
2026-09-14
Rank Moved
Rank rose 27 spots (#959 → #932)
2026-09-12
Rank Moved
Rank dropped 15 spots (#944 → #959)
2026-09-11
Rank Moved
Rank dropped 13 spots (#931 → #944)
2026-09-09
Rank Moved
Rank dropped 15 spots (#920 → #935)
2026-09-08
Rank Moved
Rank rose 118 spots (#1038 → #920)
2026-09-08
HVTrust Changed
HVTrust up 5.2pts (44.1 → 49.3)
2026-09-08
Activity Score Changed
Activity score up 16pts (30 → 45)
2026-09-07
Rank Moved
Rank dropped 31 spots (#1007 → #1038)
2026-09-06
Rank Moved
Rank dropped 36 spots (#971 → #1007)
2026-09-05
Rank Moved
Rank dropped 49 spots (#922 → #971)
2026-09-04
Rank Moved
Rank dropped 28 spots (#894 → #922)
2026-09-03
Rank Moved
Rank dropped 54 spots (#840 → #894)
2026-09-02
Rank Moved
Rank dropped 46 spots (#794 → #840)
2026-09-01
Rank Moved
Rank dropped 29 spots (#765 → #794)
2026-08-31
Rank Moved
Rank dropped 37 spots (#728 → #765)
2026-08-30
Rank Moved
Rank dropped 53 spots (#675 → #728)
2026-08-30
Activity Score Changed
Activity score down 6pts (36 → 30)
2026-08-29
Rank Moved
Rank dropped 45 spots (#630 → #675)
2026-08-28
Rank Moved
Rank dropped 21 spots (#609 → #630)
2026-08-27
Rank Moved
Rank dropped 13 spots (#596 → #609)
2026-08-26
Scorecard Added
OSSF Scorecard: 4.4/10
2026-08-26
Rank Moved
Rank rose 500 spots (#1096 → #596)
2026-08-26
HVTrust Changed
HVTrust up 26.8pts (19.8 → 46.6)
2026-08-24
Rank Moved
Rank dropped 10 spots (#1082 → #1092)
2026-08-17
Rank Moved
Rank rose 11 spots (#1086 → #1075)
2026-08-16
Rank Moved
Rank dropped 32 spots (#1054 → #1086)
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 43.4 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/asp-net-core-debugger-mcp-server-for-ai-agents.svg)](https://hvtracker.net/agents/asp-net-core-debugger-mcp-server-for-ai-agents)
HTML:
<a href="https://hvtracker.net/agents/asp-net-core-debugger-mcp-server-for-ai-agents"><img src="https://hvtracker.net/badge/asp-net-core-debugger-mcp-server-for-ai-agents.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