On-demand.NET runtime diagnostics for live CoreCLR apps — no code changes. Ships an MCP server (let an LLM drive the...
Copy the install, test the workflow, then decide if it earns a permanent slot.
Fresh repo activity plus visible builder pull. This is the kind of tool people test before it turns obvious.
Copy the install, test the workflow, then decide if it earns a permanent slot.
You can test this quickly and remove it cleanly if it misses.
GitHub health unknown. no security policy. Fresh enough repo health and manageable issue load keep the risk controlled.
AI Agent
Universal
Model
Multiple
Fastest way to find out if dotnet-diagnostics belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
claude mcp add dotnet-diagnostics -- npx dotnet-diagnosticsRun this first. You will know quickly if the workflow earns a permanent slot.
claude mcp remove dotnet-diagnosticsNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude.json └─ mcp_servers/ └─ dotnet-diagnostics ← registers here
On-demand.NET runtime diagnostics for live CoreCLR apps — no code changes. Ships an MCP server (let an LLM drive the investigation), a standalone CLI, and a BenchmarkDotNet diagnoser, all on one engine: counters, CPU/off-CPU/alloc sampling, heap & thread snapshots, GC/contention/threadpool events, dumps.
Source: GitHub repository
Source check: October 19, 2026
Upstream commit: October 19, 2026
Repository state: Not marked archived
Honeystax upvotes are community interest signals, not star ratings. GitHub stars and repository health are source measurements; editorial risk and trial-cost notes are Honeystax analysis.