dotnet-diagnostics
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.
No outside reports on file
dotnet-diagnostics is distributed via GitHub (pedrosakuma/dotnet-diagnostics); review its source code, dependencies, and requested permissions before use.
Based on public adoption and transparency signals as of Oct 19, 2026. Our opinion, not a code audit or security guarantee.
What it can access
- Local filesNo local folder access notedLOW
- Command executionNo shell command runner notedLOW
- Network reachLocal or standard API callsLOW
- CredentialsNo API token requiredLOW
- Package sourceGitHub (pedrosakuma/dotnet-diagnostics)PUBLIC
Inferred from this listing’s public package details and description. Check the project’s source before installing.
Install
No npm or PyPI package is listed. Install from source: github.com/pedrosakuma/dotnet-diagnostics ↗
Everything known
We found nothing about this project in the sources we read (last checked 2026-10-30). That does not mean it has no problems.
0 incidents · 0 advisories · 0 news articles · 0 community threads · checked 2026-10-30
Popularity grade: D (from public signals such as stars and downloads, not a code review). Graded 2026-10-19.
Sources we read: OSV, GitHub Advisory Database, CISA Known Exploited Vulnerabilities, 44 security news feeds and our incident library. Last checked 2026-10-30.
About Dotnet Diagnostics
Dotnet Diagnostics is an MCP server focused on Developer tools and Files & documents: 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.
It is hosted on GitHub at pedrosakuma/dotnet-diagnostics (27 GitHub stars). Based on its public metadata, it operates with standard local or API scope without broad shell execution flags noted.
Setup
These use the package this listing points to. Check the project’s own instructions before running anything.
No npm or PyPI package is listed for this MCP server. Source code and setup steps: github.com/pedrosakuma/dotnet-diagnostics.
Why this grade
Signal-based grade (1/7 points): public source code. This reflects adoption and transparency, not a code review.
Popularity and upkeep
- GitHub stars
- 27
- Listing last refreshed
- 2026-10-29
These are public popularity signals, not a maintenance check. Look at the repository’s commit history and open issues.
Risks to watch for
- Dependency & version pinning: Distributed via GitHub (pedrosakuma/dotnet-diagnostics). Pin an exact release version or commit SHA rather than floating tags so upstream updates are reviewed first.
How to lower the risk
Least-privilege permissions
- Give it access only to the specific folders, accounts or projects it needs, never your whole drive or admin account.
- Use a separate, limited API key or login just for this tool so you can switch it off without affecting anything else.
Network isolation
- Run it on a work computer or sandbox account, not one holding personal or company-sensitive data.
- If your IT team can, limit which websites and services it is allowed to contact.
Monitoring
- Check its activity history or logs weekly at first, and look at what it changed or sent.
- Turn on alerts for new logins or unusual usage on any account it connects to.
Red flags to watch for
- It asks for more access than its job requires, or prompts you to paste passwords.
- It suddenly updates with new owners, or starts contacting unfamiliar websites.
Questions
How do I install Dotnet Diagnostics?
Dotnet Diagnostics does not publish a standalone npm or PyPI package. Clone or follow the setup instructions in its source repository at github.com/pedrosakuma/dotnet-diagnostics.
Are there security reports about Dotnet Diagnostics?
No reports found for this package in our research (last checked 2026-10-30). Dotnet Diagnostics currently holds Grade D (High risk signals) based on public adoption and transparency signals. Review the permissions and source repository before granting access to local files, shell commands, or API keys.
Is Dotnet Diagnostics actively maintained?
Dotnet Diagnostics has 27 GitHub stars. Our directory data was last refreshed on 2026-10-29. Check recent commit activity, release tags, and open issues at github.com/pedrosakuma/dotnet-diagnostics before pinning it in production.
What are alternatives to Dotnet Diagnostics?
Compare Dotnet Diagnostics side by side with similar MCP servers in the Related tools section on this page, or browse all MCP servers on AgentArmorHQ.
Key facts
- Type
- App connector
- Publisher
- pedrosakuma
- Source code
- github.com/pedrosakuma/dotnet-diagnostics
- Est. context load
- ~950 tokens / turn (~5 tool schemas, 0.47% of 200k context)
- Popularity
- 27 GitHub stars
- Last updated
- 2026-10-29
- Last graded
- 2026-10-19
Community
Discussions for Dotnet Diagnostics
Ask questions or share configuration tips. Governed by our Community Rules & Terms.
No posts match this filter yet.
Be the first to ask a question or share a working tip.
Check before you install, in Claude
Your assistant answers Block, Review or No known issues for any package before it installs it.
Get this check inside Claude