GitHub
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
Computer or cloud
Sharphy
Overview
Description from the maker (original English)
CLR Intelligence and Runtime Forensic Bridge for AI Coding Agents.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiVery new★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Developer tools
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- The registry lists no key to fill in.
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"sharphy": {
"command": "dnx",
"args": [
"Sharphy.Cli",
"--yes"
]
}
}
}Run this in your terminal
claude mcp add sharphy -- dnx Sharphy.Cli --yesOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"sharphy": {
"command": "dnx",
"args": [
"Sharphy.Cli",
"--yes"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"sharphy": {
"type": "stdio",
"command": "dnx",
"args": [
"Sharphy.Cli",
"--yes"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account baharmaulidiii, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Developer toolsi
- More stars than 0% of the other 5135 servers in this category
- Published to the registry more recently than 78% of the other 5135 servers in this category
- Basic checks equal to or better than 100% of the other 5135 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Sharphy safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (1.1.1) reached the registry 8 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need .NET on your computer.
What can I use instead?
In the same category: GitHub, Desktop Commander, Cloudflare MCP
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Desktop Commander
MCP server for terminal commands, file operations, and process management
Runs on your computer
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Sharphy: CLR Intelligence & Runtime Forensic Bridge
Native Model Context Protocol (MCP) Server Empowering AI Coding Agents as Advanced .NET Runtime Diagnosticians, Memory Forensic Analysts, and Binary Architects.
Leveraging ECMA-335 Metadata Semantics, Cross-Platform Crash Dump Telemetry, and Rigid CIL Bytecode Navigation.
Architecture · Ecosystem · MCP Catalog · Agent Setup · Policies & Legal · Changelog · Contributing · Code of Conduct
[!CAUTION]
Legal Disclaimer & Limitation of Liability
Sharphy is engineered exclusively for good-faith security research, production crash dump diagnostics, vulnerability assessments, incident response, and lawful software engineering. Users bear sole civil and criminal responsibility for complying with applicable territorial cyber laws, third-party End User License Agreements (EULAs), and intellectual property rights. The developer disclaims any liability for malicious misuse or unlawful reverse engineering. Full details: DISCLAIMER.md.
[!IMPORTANT]
Install and execute Sharphy only from official distribution channels: verified NuGet packages (
Sharphy.Cliunder the verifiedSharphy.*reserved prefix), official Model Context Protocol (MCP) Registry (io.github.baharmaulidiii/sharphy), or direct compilation from the official repository at github.com/baharmaulidiii/sharphy.
Architecture Overview & Philosophy
Mainstream AI coding agents (*Cursor*, *Claude Code*, *Windsurf*, *Copilot*) operate primarily on raw source code heuristics in an editor. They suffer from runtime blindness when confronting:
- Production memory crashes and unhandled fatal exceptions
- Multi-threaded synchronization deadlocks and lock cycle contention
- Large Object Heap (LOH) fragmentation and memory leaks
- Compiled third-party binaries lacking source code availability
Sharphy serves as a deterministic runtime forensic bridge implementing the open Model Context Protocol (MCP) specification. Over an isolated JSON-RPC 2.0 Stdio channel, Sharphy exposes Microsoft low-level diagnostics and decompilation engines directly to semantic AI reasoning loops.
┌─────────────────────────────────────────────────────────────┐│ AI Coding Agent Client │ │ (Cursor / Claude Code / Windsurf / LLM) │ └──────────────────────────────┬──────────────────────────────┘ │ JSON-RPC 2.0 over Stdio ▼ ┌─────────────────────────────────────────────────────────────┐ │ Sharphy.Server (Host) │ │ ┌─────────────────────────────────────────────────────┐ │ │ │ Pure Stdio Channel (stdout: Payloads / stderr: Log)│ │ │ │ JSON-RPC Dispatcher & Tool Registry (10 Tools) │ │ │ └──────────────────────────┬──────────────────────────┘ │ └──────────────────────────────┼──────────────────────────────┘ │ Strongly-Typed In-Process Calls ▼ ┌─────────────────────────────────────────────────────────────┐ │ Sharphy.Core Engine │ │ ┌───────────────────────┐ ┌───────────────────────┐ │ │ │ ClrMD Forensics │ │ ILSpy Engine │ │ │ │ (Crash Dump & Heap) │ │ (C# Decompilation) │ │ │ ├───────────────────────┤ ├───────────────────────┤ │ │ │ Mono.Cecil Engine │ │ Roslyn & Sandbox │ │ │ │ (Metadata & Mutation) │ │ (UnsafeAccessor & ALC)│ │ │ └───────────────────────┘ └───────────────────────┘ │ └──────────────────────────────┬──────────────────────────────┘ │ Deterministic Low-Level Inspection ▼ ┌─────────────────────────────────────────────────────────────┐ │ Runtime Analysis Target │ │ • Windows / Linux Crash Dump Files (.dmp / ELF core dump) │ │ • Compiled Binary Assemblies (.dll / .exe ECMA-335) │ │ • Active Runtime Processes & Isolated AssemblyLoadContext │ └─────────────────────────────────────────────────────────────┘
Package Ecosystem & Roles
The Sharphy solution is organized into three modular projects with distinct boundaries:
| Package / Module | Distribution | Target Audience | Architectural Role & Technical Scope |
|---|---|---|---|
| `Sharphy.Cli` | .NET Global Tool | End Users & Agents | Command-line entry point. Operates as an instant zero-configuration launcher for the MCP host server (sharphy mcp start) or quick inspection utilities. |
| `Sharphy.Server` | Class Library / Host | Agent Frameworks & Hosts | Implements the official Model Context Protocol (MCP) using JSON-RPC 2.0. Enforces pure Stdio stream separation: stdout is dedicated to JSON-RPC payloads, while all internal diagnostic logging is routed to stderr. |
| `Sharphy.Core` | Class Library Engine | CLR Engineers & Builders | Pure analytical engine with no MCP protocol dependencies. Abstacts low-level libraries: Microsoft.Diagnostics.Runtime (ClrMD), ICSharpCode.Decompiler (ILSpy), Mono.Cecil, and Microsoft.CodeAnalysis.CSharp (Roslyn). |
Operational Architecture: Zero-Footprint Production Forensics
A common enterprise architectural question is whether diagnostic servers must be deployed to live production machines.
Does Sharphy need to be installed on your production servers? NO.
Sharphy follows a Zero-Footprint, Post-Mortem Forensic Workflow. The analytical engines, decompilers, and AI agents run strictly in isolated development, CI/CD, or security analyst workstations:
┌──────────────────────────────────────────────┐│ PRODUCTION ENVIRONMENT │ │ (Zero Sharphy Footprint Required) │ │ │ │ 1. Unhandled crash / freeze occurs │ │ 2. Collect memory dump via official CLI: │ │ dotnet-dump collect -p │ │ 3. Output: crash.dmp (Windows) / core (ELF) │ └──────────────────────┬───────────────────────┘ │ Secure SCP / S3 Dump Transfer ▼ ┌──────────────────────────────────────────────┐ │ ANALYST WORKSTATION / AI ENVIRONMENT │ │ (Isolated Off-Site Inspection) │ │ │ │ • AI Coding Agent (Cursor / Claude Code) │ │ • Sharphy MCP Server (Sharphy.Cli / Server) │ │ • Automated RCA: │ │ - sharphy_analyze_dump │ │ - sharphy_inspect_heap │ │ - sharphy_deadlock_detector │ └──────────────────────────────────────────────┘
Key Operational Benefits:
- Zero Production Risk: No third-party daemons, background agents, or persistent listeners are installed on mission-critical production servers.
- Standard Microsoft Tooling: Dump collection uses standard, officially supported Microsoft utilities (
dotnet-dump,createdump, or OS crash reporting). - Regulatory & Audit Compliance: Keeps production environments compliant with strict compliance standards (PCI-DSS, ISO/IEC 27001, SOC 2) by avoiding intrusive monitoring hooks.
- Air-Gapped & Offline Ready: Analysis can be performed in completely isolated, offline lab environments without remote runtime connectivity.
10 MCP Tools Catalog
Sharphy exposes ten specialized tools covering the full spectrum of .NET runtime analysis:
┌────────────────────────────────────────────────────────────────────────────┐│ SHARPHY 10 MCP TOOLS CATALOG │ ├────────────────────────┬─────────────────────────┬─────────────────────────┤ │ Memory & Forensics │ Decompilation & Diff │ Bytecode & Metadata │ ├────────────────────────┼─────────────────────────┼─────────────────────────┤ │ • sharphy_analyze_dump │ • sharphy_decompile_... │ • sharphy_inspect_me... │ │ • sharphy_inspect_heap │ • sharphy_diff_assem... │ • sharphy_extract_to... │ │ • sharphy_deadlock_... │ • sharphy_clean_obfu... │ • sharphy_patch_il │ │ │ │ • sharphy_generate_w... │ └────────────────────────┴─────────────────────────┴─────────────────────────┘
1. sharphy_analyze_dump
Automated Root Cause Analysis (RCA) on Windows (.dmp) and Linux (ELF core dump) CoreCLR memory crash dumps. Extracts crashing thread call stacks, unhandled exception objects, and faulty HRESULT codes.
2. sharphy_inspect_heap
Deep managed heap inspection, traversing GC segments, measuring generation distribution (Gen 0, Gen 1, Gen 2, LOH, POH), calculating fragmentation, and pinpointing memory leak retainers.
3. sharphy_deadlock_detector
Traverses the CLR SyncBlock synchronization cache and active thread Monitor locks, building a Wait-For Graph (WFG) to detect thread synchronization deadlock cycles.
4. sharphy_decompile_method
Reconstructs clean, modern idiomatic C# source code from compiled CIL bytecode using the embedded ILSpy engine, reconstructing async state machines and lambda captures.
5. sharphy_diff_assemblies
Performs semantic binary comparisons between two versions of an assembly, flagging added/removed types, breaking changes to public/protected APIs, and CIL instruction size shifts.
6. sharphy_inspect_metadata
Inspects ECMA-335 metadata tables, decoding TypeDef, MethodDef, FieldDef, custom attributes, P/Invoke native imports, and embedded resources.
7. sharphy_clean_obfuscation
Analyzes obfuscated assemblies, demangling Control Flow Graph (CFG) switch-flattening patterns, trimming excessi
Only the beginning is shown; read the rest in the repo