Is X64dbg MCP safe to use?

X64dbg MCP has an HVTrust score of 38.1/100 (Grade D), ranked #1246 of 1378 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for X64dbg MCP?

X64dbg MCP scores 38.1/100 on HVTracker's evidence-weighted HVTrust scale. It has 132 GitHub stars and is categorized under MCP Servers.

X64dbg MCP

Repository

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.

MCP Servers C++ Listed MIT

Is X64dbg MCP safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 1.3 / 10

Provenance None

Signed commits 0%

Last push 132d ago

Advisories None known

Compare X64dbg MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: X64dbg MCP scores 38.1/100 (Grade D), ranked #1246 of 1378 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; no published advisory affects its latest release (x64dbg-mcp-server); last pushed 2026-06-08. Every point is earned from checkable signals — never paid placement. How scoring works →

How X64dbg MCP 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.

Raise the OSSF Scorecard from 1.3 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Code-Review 0 +16.1 → 54.2 C · #479 of 781
Publish build provenance for its packagesnpm publish --provenance from CI +14.7 → 52.8 C · #515 of 781
Sign every commit0% signed today +5.0 → 43.1 D · #667 of 781

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships X64dbg MCP 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 Unsigned

github.com/bromoket/x64dbg_mcp, MIT, last pushed 2026-06-08. None of the last 100 commits carry a verified signature, so no change traces to a verified identity.
Review and release Weak

OpenSSF Scorecard rates the repository's practices 1.3/10 (scanned Oct 6, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection0
- Signed Releases0
- Dangerous Workflown/a
- Token Permissionsn/a
- Pinned Dependenciesn/a
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 0

CI-Tests -1

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow -1

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies -1

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions -1

Vulnerabilities 0
Published packages Linked, not attested
- npm x64dbg-mcp-server 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: x64dbg-mcp-server 2.3.0. No published advisory affects it (OSV, checked 2026-10-17).

Changes to this chain

2026-09-04 OSSF Scorecard: 1.7/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 X64dbg MCP’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.

Signed credential (JSON) How to verify

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 X64dbg MCP compares in MCP Servers

#719 Context+ 38.2 +0.1
#720 Clipboard History MCP 38.1 ±0
#721 X64dbg MCP 38.1 this agent
#722 Hummingbot MCP 38.0 −0.1
#723 MCP Server for Binge-watch 37.8 −0.3

Bars show each HVTrust score; the tick marks X64dbg MCP’s 38.1.

Where the 38.1 comes from

HVTrust dimensions vs the MCP Servers average

38.1 / 100 · 100.0% confidence

X64dbg MCP MCP Servers average (781 agents)

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

1.6 / 25

9.0 below avg 10.6

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.8 below avg 13.6

Transparency50% declared license · 50% OSSF Scorecard

9.6 / 17

2.7 below avg 12.3

Maintenance60% last-push freshness · 40% commit activity

3.2 / 20

9.0 below avg 12.2

AdoptionLog-scaled stars · package downloads

8.2 / 20

0.8 above avg 7.4

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-10-09

Rank Moved

Rank dropped 12 spots (#1198 → #1210)

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 1.3/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.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Refresh maintenance signals The repo was last pushed 132 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for X64dbg MCP View MCP Servers Report missing data

26.4

Activity sub-score · out of 100

#721

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

2026-09-29 2026-10-17

Activity & Reach

Stars

132

Forks

Last Push

2026-06-08

132 days ago

Commits (4 wk)

Downloads (7d)

217

npm

HN mentions (30d)

—

Open Issues

Rank Change

was #1246

Analysis

Activity Inputs

26.4 / 100

StarsRepository reach

12.7 / 30

FreshnessLast push recency

6.7 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

6.9 / 20

Common questions about X64dbg MCP

Public trust evidence for X64dbg MCP is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.

Does X64dbg MCP publish package provenance?

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

Does X64dbg MCP have an OpenSSF Scorecard?

X64dbg MCP has an OpenSSF Scorecard score of 1.3/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 X64dbg MCP actively maintained?

Slowing down. Last push was 132 days ago — keep an eye on whether activity resumes.

What license does X64dbg MCP use?

X64dbg MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are X64dbg MCP's commits signed?

0% of the last 100 commits to X64dbg MCP 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

X64dbg MCP appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

low confidence

None detected

No clear third-party provider dependency detected.

Credential signal: API keys or service config markers documented.

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 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.

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-06

Activity Went Stale

No commits for 90 days

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-10-09

Rank Moved

Rank dropped 12 spots (#1198 → #1210)

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Rank Moved

Rank rose 77 spots (#1247 → #1170)

2026-09-23

HVTrust Changed

HVTrust up 24.1pts (15.7 → 39.8)

2026-09-22

Newly Listed

First tracked at rank #1247

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-12

Rank Moved

Rank dropped 11 spots (#1143 → #1154)

2026-09-09

Rank Moved

Rank dropped 15 spots (#1121 → #1136)

2026-09-08

Rank Moved

Rank dropped 28 spots (#1093 → #1121)

2026-09-07

Rank Moved

Rank dropped 27 spots (#1066 → #1093)

2026-09-06

Activity Went Stale

No commits for 90 days

2026-09-06

Rank Moved

Rank dropped 17 spots (#1049 → #1066)

2026-09-05

Rank Moved

Rank rose 198 spots (#1247 → #1049)

2026-09-05

HVTrust Changed

HVTrust up 14.7pts (27.3 → 42.0)

2026-09-04

Scorecard Added

OSSF Scorecard: 1.7/10

2026-09-04

Rank Moved

Rank rose 61 spots (#1308 → #1247)

2026-09-04

HVTrust Changed

HVTrust up 10.4pts (16.9 → 27.3)

2026-09-02

Rank Moved

Rank dropped 153 spots (#1151 → #1304)

2026-09-02

HVTrust Changed

HVTrust down 10.5pts (27.4 → 16.9)

2026-09-01

Rank Moved

Rank dropped 42 spots (#1109 → #1151)

2026-08-31

Rank Moved

Rank rose 168 spots (#1277 → #1109)

2026-08-31

HVTrust Changed

HVTrust up 10.4pts (17.0 → 27.4)

2026-08-30

Rank Moved

Rank dropped 246 spots (#1031 → #1277)

2026-08-30

HVTrust Changed

HVTrust down 10.4pts (27.4 → 17.0)

2026-08-29

Rank Moved

Rank dropped 52 spots (#979 → #1031)

2026-08-28

Rank Moved

Rank dropped 37 spots (#942 → #979)

2026-08-27

Rank Moved

Rank dropped 26 spots (#916 → #942)

2026-08-26

Rank Moved

Rank dropped 111 spots (#805 → #916)

2026-08-24

Rank Moved

Rank rose 401 spots (#1205 → #804)

2026-08-24

HVTrust Changed

HVTrust up 10.5pts (17.1 → 27.6)

2026-08-22

Rank Moved

Rank dropped 400 spots (#803 → #1203)

2026-08-22

HVTrust Changed

HVTrust down 10.6pts (27.8 → 17.2)

2026-08-19

Rank Moved

Rank rose 395 spots (#1200 → #805)

2026-08-19

HVTrust Changed

HVTrust up 10.5pts (17.3 → 27.8)

2026-08-17

Rank Moved

Rank dropped 396 spots (#804 → #1200)

2026-08-17

HVTrust Changed

HVTrust down 10.6pts (27.9 → 17.3)

2026-08-16

Rank Moved

Rank dropped 15 spots (#789 → #804)

2026-08-13

Rank Moved

Rank rose 390 spots (#1177 → #787)

2026-08-13

HVTrust Changed

HVTrust up 10.6pts (17.4 → 28.0)

2026-08-12

Rank Moved

Rank dropped 399 spots (#778 → #1177)

2026-08-12

HVTrust Changed

HVTrust down 11.7pts (29.1 → 17.4)

2026-08-10

Rank Moved

Rank dropped 41 spots (#736 → #777)

2026-08-08

Newly Listed

First tracked at rank #1103

GitHub → npm: x64dbg-mcp-server

Embed Badge Badge guide for maintainers →

For maintainers

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

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

X64dbg MCP

How X64dbg MCP could raise its score

Chain of custody

Source Unsigned

Review and release Weak

Published packages Linked, not attested

What you install today No known advisories

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How X64dbg MCP compares in MCP Servers

Where the 38.1 comes from

HVTrust dimensions vs the MCP Servers average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about X64dbg MCP

AI agent surface

Maintain X64dbg MCP?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in MCP Servers