Ext Ops Panel
Open dashboard
Comparison

netcoredbg-mcp vs MCP Server for WinDbg Crash Analysis

netcoredbg-mcp is an MCP server published by thebtf. Marketplaces we read that list it: 1 (PyPI (MCP servers)). MCP Server for WinDbg Crash Analysis is an MCP server published by svnscha. Marketplaces we read that list it: 3 (Official MCP Registry, PyPI (MCP servers), Community GitHub marketplaces). As of our marketplace pass on 2026-11-09. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacenetcoredbg-mcpMCP Server for WinDbg Crash Analysis
PyPI (MCP servers) Listed
Version: 0.23.17
Downloads/month (PyPI): 332
Downloads/week (PyPI): 538
Forks (GitHub): 2
Stars (GitHub): 8
Not marked · First seen
Listed
Version: 1.6.0
Downloads/month (PyPI): 2 308
Downloads/week (PyPI): 485
Forks (GitHub): 168
Stars (GitHub): 1 663
Not marked · First seen
Official MCP Registry Not listed Listed
Version: 1.6.0
Downloads/month (PyPI): 2 308
Downloads/week (PyPI): 485
Forks (GitHub): 168
Stars (GitHub): 1 663
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

netcoredbg-mcp vs MCP Server for WinDbg Crash Analysis
Factnetcoredbg-mcpMCP Server for WinDbg Crash Analysis
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)8 (worse)1 663 (better)
Forks (GitHub) (differs)2 (worse)168 (better)
Last release (differs)2026-10-27 (better)2026-10-24 (worse)
Where it runs (differs)On your machine (netcoredbg-mcp)On your machine (mcp-windbg)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 0
Parts of the bundle (differs)Not a bundle1
LicenceMITMIT
Repository (differs)github.com/thebtf/netcoredbg-mcpgithub.com/svnscha/mcp-windbg
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

netcoredbg-mcp

In its own words, on PyPI (MCP servers):

MCP server for debugging C#/.NET code using netcoredbg

MCP Server for WinDbg Crash Analysis

In its own words, on Official MCP Registry:

A Model Context Protocol server for Windows crash dump analysis using WinDbg/CDB

How to run each

netcoredbg-mcp

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

MCP Server for WinDbg Crash Analysis As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio mcp-windbg -- uvx mcp-windbg

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of netcoredbg-mcp publish no settings it asks for, so we do not compare settings.

What it can do: netcoredbg-mcp · What it can do: MCP Server for WinDbg Crash Analysis · Compare two other plugins

Package data comes from the Python Package Index (pypi.org). Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built