X64dbg MCP
Drive x64dbg with your AI. MCP server: 23 mega-tools / 153 endpoints for breakpoints, memory, disasm, tracing, anti-debug & PE dumping. Claude/Cursor/Windsurf/Cline. All local.
Is X64dbg MCP safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare X64dbg MCP
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: X64dbg MCP scores 39.7/100 (Grade D), ranked #1172 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 1.3/10; recent commits are unsigned; last pushed 2026-06-08. Every point is earned from checkable signals — never paid placement. How scoring works →
How X64dbg MCP compares in MCP Servers
- #693 TradeOS 39.7 ±0
- #694 MCP Server Code Runner 39.7 ±0
- #695 X64dbg MCP 39.7 this agent
- #696 Clipboard History MCP 39.6 −0.1
- #697 Pagecast 39.5 −0.2
Bars show each HVTrust score; the tick marks X64dbg MCP’s 39.7.
Where the 39.7 comes from
HVTrust dimensions vs the MCP Servers average
39.7 / 100 · 100.0% confidenceX64dbg MCP MCP Servers average (775 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 D 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
29.5 / 100Supply Chain Trust
Common questions about X64dbg MCP
Does X64dbg MCP publish package provenance?
Does X64dbg MCP have an OpenSSF Scorecard?
Is X64dbg MCP actively maintained?
What license does X64dbg MCP use?
Are X64dbg MCP'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 X64dbg MCP'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 X64dbg MCP?
For maintainers
HVTrust scores X64dbg MCP 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/x64dbg-mcp)
<a href="https://hvtracker.net/agents/x64dbg-mcp"><img src="https://hvtracker.net/badge/x64dbg-mcp.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON