Is MCP Server for WinDbg Crash Analysis safe to use?

MCP Server for WinDbg Crash Analysis has an HVTrust score of 67.0/100 (Grade B), ranked #402 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for MCP Server for WinDbg Crash Analysis?

MCP Server for WinDbg Crash Analysis scores 67.0/100 on HVTracker's evidence-weighted HVTrust scale. It has 1.6k GitHub stars and is categorized under MCP Servers.

MCP Server for WinDbg Crash Analysis

svnscha/mcp-windbg

Model Context Protocol for WinDbg.

MCP Servers Python Listed MIT

Is MCP Server for WinDbg Crash Analysis safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.9 / 10

Provenance None

Signed commits 81%

Last push 5d ago

Compare MCP Server for WinDbg Crash Analysis

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: MCP Server for WinDbg Crash Analysis scores 67.0/100 (Grade B), ranked #402 of 1325 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.9/10; 81% of recent commits are signed; last pushed 2026-09-21. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Server for WinDbg Crash Analysis compares in MCP Servers

#238 Sauce Api MCP 67.1 +0.1
#239 Azure DevOps (ADO) 67.0 ±0
#240 MCP Server for WinDbg Crash Analysis 67.0 this agent
#241 E18e MCP 67.0 ±0
#242 Brilliant Directories MCP 67.0 ±0

Bars show each HVTrust score; the tick marks MCP Server for WinDbg Crash Analysis’s 67.0.

Where the 67.0 comes from

HVTrust dimensions vs the MCP Servers average

67.0 / 100 · 100.0% confidence

MCP Server for WinDbg Crash Analysis MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

10.2 / 25

in line with avg 10.3

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

12.7 / 17

in line with avg 12.2

Maintenance60% last-push freshness · 40% commit activity

16.6 / 20

4.5 above avg 12.1

AdoptionLog-scaled stars · package downloads

11.0 / 20

3.8 above avg 7.2

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-24

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-24

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-24

Mcp Status Changed

Detected MCP server support changed: declared → implemented

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.9/10. Tighten the weakest checks to improve public safety evidence.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Compare with another agent Get email alerts for MCP Server for WinDbg Crash Analysis View MCP Servers Report missing data

69.1

Activity sub-score · out of 100

#240

In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B 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

2026-08-11 2026-09-26

Activity & Reach

Stars

1.6k

Forks

158

Last Push

2026-09-21

5 days ago

Commits (4 wk)

Downloads (7d)

329

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▼2

was #400

Analysis

Activity Inputs

69.1 / 100

StarsRepository reach

19.2 / 30

FreshnessLast push recency

24.3 / 25

ActivityRecent commits

15.3 / 25

CommunityFork signal

10.2 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.9 / 10

OpenSSF Scorecard · scanned Sep 20, 2026

Signed Commits

81%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 7

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 10

Common questions about MCP Server for WinDbg Crash Analysis

MCP Server for WinDbg Crash Analysis has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does MCP Server for WinDbg Crash Analysis publish package provenance?

No published build provenance is currently detected for MCP Server for WinDbg Crash Analysis. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does MCP Server for WinDbg Crash Analysis have an OpenSSF Scorecard?

MCP Server for WinDbg Crash Analysis has an OpenSSF Scorecard score of 4.9/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is MCP Server for WinDbg Crash Analysis actively maintained?

Actively maintained. The repository was pushed to within the last 5 day(s).

What license does MCP Server for WinDbg Crash Analysis use?

MCP Server for WinDbg Crash Analysis ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are MCP Server for WinDbg Crash Analysis's commits signed?

80% of the last 100 commits to MCP Server for WinDbg Crash Analysis are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

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

Scored in HVTrust

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 Server Support

high confidence

Implemented

MCP Server for WinDbg Crash Analysis appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

medium confidence

1 detected

Public provider/service dependencies detected.

Anthropic

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

How this surface has changed

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.

2026-09-24

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-24

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-24

Mcp Status Changed

Detected MCP server support changed: declared → implemented

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → declared

2026-09-03

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-03

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-09-24

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-24

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-24

Mcp Status Changed

Detected MCP server support changed: declared → implemented

2026-09-24

Rank Moved

Rank rose 60 spots (#454 → #394)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → declared

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 270 spots (#724 → #454)

2026-09-23

HVTrust Changed

HVTrust up 35.2pts (30.4 → 65.6)

2026-09-22

Newly Listed

First tracked at rank #724

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-20

Rank Moved

Rank dropped 10 spots (#379 → #389)

2026-09-13

Rank Moved

Rank dropped 10 spots (#354 → #364)

2026-09-10

Rank Moved

Rank rose 25 spots (#369 → #344)

2026-09-07

Rank Moved

Rank dropped 26 spots (#345 → #371)

2026-09-06

Rank Moved

Rank dropped 10 spots (#335 → #345)

2026-09-05

Rank Moved

Rank dropped 58 spots (#277 → #335)

2026-09-03

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-03

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-08-31

Rank Moved

Rank dropped 26 spots (#228 → #254)

2026-08-27

Rank Moved

Rank rose 22 spots (#245 → #223)

2026-08-26

Scorecard Added

OSSF Scorecard: 4.5/10

2026-08-26

Grade Changed

Trust grade D → B

2026-08-26

Rank Moved

Rank rose 402 spots (#647 → #245)

2026-08-26

HVTrust Changed

HVTrust up 26.0pts (39.5 → 65.5)

2026-08-22

Rank Moved

Rank rose 17 spots (#659 → #642)

2026-08-21

Rank Moved

Rank rose 50 spots (#709 → #659)

2026-08-21

HVTrust Changed

HVTrust up 3.3pts (35.4 → 38.7)

2026-08-21

Activity Score Changed

Activity score up 13pts (50 → 63)

2026-08-16

Rank Moved

Rank dropped 16 spots (#689 → #705)

2026-08-15

Rank Moved

Rank dropped 17 spots (#672 → #689)

2026-08-15

Activity Score Changed

Activity score down 6pts (57 → 51)

2026-08-14

Rank Moved

Rank dropped 11 spots (#661 → #672)

2026-08-10

Rank Moved

Rank dropped 26 spots (#631 → #657)

2026-08-08

Newly Listed

First tracked at rank #630

GitHub → PyPI: mcp-windbg

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/mcp-server-for-windbg-crash-analysis.svg)](https://hvtracker.net/agents/mcp-server-for-windbg-crash-analysis)
            
HTML:
            <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

Data sources
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.3 · Raw JSON