MCP.Market

ASP.NET Core Debugger — MCP Server for AI Agents

by magna-nz·io.github.magna-nz/aspnetcore-debugger-mcp·v1.4.0·15 stars
No reviews yet

MCP server giving AI agents interactive .NET / ASP.NET Core debugging via netcoredbg + DAP.

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

full report

Adoption
Growing

15 stars

Reviews

Write one

Nobody has reviewed ASP.NET Core Debugger — MCP Server for AI Agents yet.

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

ASP.NET Core Debugger — MCP Server for AI Agents tools

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

Public scan report

scanner v0.1.10 · 2026-10-15 · 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 31 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 80/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How ASP.NET Core Debugger — MCP Server for AI Agents compares

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

Safety score
80/100
higher than 60% of 48,243 servers
GitHub stars
15
more than 90% of 28,706 servers

Install ASP.NET Core Debugger — MCP Server for AI Agents in Claude Code, Cursor or VS Code

The registry entry has no remote endpoint or installable package.

What the publisher says

From the ASP.NET Core Debugger — MCP Server for AI Agents repository's README, as published. We do not edit it. Read it on GitHub

ASP.NET Core Debugging MCP Server

The cross-platform .NET debugging MCP — runs on Linux, macOS, and Windows.

<!-- mcp-name: io.github.magna-nz/aspnetcore-debugger-mcp -->

An MIT-licensed MCP server that lets an AI agent (Claude, etc.) debug your .NET / ASP.NET Core app — netcoredbg bundled for every platform, nothing extra to install.

Instead of "I think the bug is around line 42, try this", the agent runs your code, pauses it, reads the actual runtime values, mutates state to test a fix, and answers grounded in what it actually saw.

Contents

  • See it in action — 5 conversations showing the agent at work
  • How it works — architecture diagram
  • Use it in 3 steps — install + register with Claude
  • Platforms — supported OS / architecture matrix
  • Tools (27) — full tool surface grouped by purpose
  • How this compares — vs. other .NET / DAP MCPs
  • Docs — install, examples, tool reference, limits
  • License

See it in action

Why is my EF Core query returning empty?

You

GET /users/active returns [], but I know there are active users in the DB. What's the

query actually doing?

Claude

I'll pause inside UserRepository.GetActiveAsync and read what EF Core actually sent.

sql

SELECT u.*

FROM Users AS u

WHERE u.IsActive = 1 AND u.TenantId = @tenantId0

@tenantId0 = 0

The SQL is correct; the parameter is wrong. TenantId = 0, but your tenants start at 1.

ICurrentUser.TenantId is being read in the repository constructor — before the request

scope resolves it. Fix: read the tenant inside the query (or apply it via HasQueryFilter

with IHttpContextAccessor) instead of capturing it at construction.

Why is my JWT auth returning 401?

You

/admin/users is 401-ing for Anna, but her token looks valid to me. What does the auth

handler actually see?

Claude

I'll break inside JwtBearerHandler.HandleAuthenticateAsync after her request lands.

Token signature: ✓ valid

Claims built:

name : anna

role : User

iss : https://auth.staging.example

aud : app-api

exp : 2026-05-26T14:12:00Z (not expired)

The token validates fine — but the claim is role=User. Your endpoint is

[Authorize(Roles="Admin")]. So the 401 is correct: Anna isn't actually an admin yet

upstream. Either her IdP record needs updating, or this policy is wrong.

Test a fix without restarting

You

I think capping discount at 100 fixes the bug. Test that hypothesis without me touching

the code.

Claude

Shortened. The full README is on GitHub.

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

Grade history

  • 2026-10-15downgradeA → Bscore 80

ASP.NET Core Debugger — MCP Server for AI Agents: common questions

Is ASP.NET Core Debugger — MCP Server for AI Agents safe?
Mostly: it is graded B (80/100). Read the ASP.NET Core Debugger — MCP Server for AI Agents safety report
Does ASP.NET Core Debugger — MCP Server for AI Agents need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is ASP.NET Core Debugger — MCP Server for AI Agents maintained?
The last commit was 52 days ago (2026-09-14). The latest release is v1.4.0.
How does ASP.NET Core Debugger — MCP Server for AI Agents compare with other MCP servers?
safety score 80/100 (higher than 60% of 48,243 servers); github stars 15 (more than 90% of 28,706 servers). Full comparison.