MCP Server for WinDbg Crash Analysis
Website
Model Context Protocol for WinDbg.
Is MCP Server for WinDbg Crash Analysis safe? Promising trust profile, but some evidence still deserves review.
Compare MCP Server for WinDbg Crash Analysis
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: MCP Server for WinDbg Crash Analysis scores 64.5/100 (Grade C), ranked #552 of 1374 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.2/10; 88% of recent commits are signed; no published advisory affects its latest release (mcp-windbg); last pushed 2026-10-28. Every point is earned from checkable signals — never paid placement. How scoring works →
How MCP Server for WinDbg Crash Analysis could raise its score
Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.
- Publish build provenance for its packagesPyPI Trusted Publishing attestations +14.7 → 79.2 B · #108 of 778
- Raise the OSSF Scorecard from 4.2 to 9.0lowest checks: CII-Best-Practices 0, Fuzzing 0, Pinned-Dependencies 0 +10.0 → 74.5 B · #162 of 778
- Sign every commit88% signed today +0.5 → 65.0 B · #305 of 778
Chain of custody
Scanners check what the code says. This traces who ships MCP Server for WinDbg Crash Analysis and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Signed
github.com/svnscha/mcp-windbg, MIT, last pushed 2026-10-28. 88% of the last 100 commits carry a verified signature, so changes trace to a verified account.
-
Review and release Mixed
OpenSSF Scorecard rates the repository's practices 4.2/10 (scanned Nov 6, 2026). The checks that decide who can get a change released:
- Code Review3
- Branch Protection3
- Signed Releases0
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies0
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 3CI-Tests 8CII-Best-Practices 0Code-Review 3Contributors 3Dangerous-Workflow 10Dependency-Update-Tool 10Fuzzing 0License 10Maintained 10Packaging -1Pinned-Dependencies 0SAST 0Security-Policy 0Signed-Releases 0Token-Permissions 0Vulnerabilities 0 -
Published packages Linked, not attested
- PyPI mcp-windbg Source link points back to this repo No build attestation
Without a build attestation, nothing proves the published files were built from this repository.
-
What you install today No known advisories
Latest release checked: mcp-windbg 1.6.0. No published advisory affects it (OSV, checked 2026-11-09).
Changes to this chain
- 2026-08-26 OSSF Scorecard: 4.5/10
Evidence behind this score
Coverage B: 3 of 5 independent evidence types found.
- GitHub repository data
- Package downloads
- Supply-chain checks
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues MCP Server for WinDbg Crash Analysis’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.
What this score doesn’t check
It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.
How MCP Server for WinDbg Crash Analysis compares in MCP Servers
- #312 FAOSTAT MCP 64.6 +0.1
- #313 MCP Proxmox 64.6 +0.1
- #314 MCP Server for WinDbg Crash Analysis 64.5 this agent
- #315 AgentPhone 64.5 ±0
- #316 Google Workspace MCP 64.4 −0.1
Bars show each HVTrust score; the tick marks MCP Server for WinDbg Crash Analysis’s 64.5.
Where the 64.5 comes from
HVTrust dimensions vs the MCP Servers average
64.5 / 100 · 100.0% confidenceMCP Server for WinDbg Crash Analysis MCP Servers average (778 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
64.9 / 100Common questions about MCP Server for WinDbg Crash Analysis
Does MCP Server for WinDbg Crash Analysis publish package provenance?
Does MCP Server for WinDbg Crash Analysis have an OpenSSF Scorecard?
Is MCP Server for WinDbg Crash Analysis actively maintained?
What license does MCP Server for WinDbg Crash Analysis use?
Are MCP Server for WinDbg Crash Analysis's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to MCP Server for WinDbg Crash Analysis's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain MCP Server for WinDbg Crash Analysis?
For maintainers
HVTrust scores MCP Server for WinDbg Crash Analysis from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/mcp-server-for-windbg-crash-analysis)
<a href="https://hvtracker.net/agents/mcp-server-for-windbg-crash-analysis"><img src="https://hvtracker.net/badge/mcp-server-for-windbg-crash-analysis.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON