Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.bromoket/x64dbg

NPM · X64DBG-MCP-SERVER

MCP server for x64dbg debugger - 23 mega-tools for AI-powered reverse engineering and debugging

Available components

0 this week 72 Trust /100

Last scanned (12 hours ago)

Scores higher than 44% of npm servers

Category Security

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability54
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 823 tokens (~35/item across 23 items; 23 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage77
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 32% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "x64dbg_debug" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 23 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 13 Nov 26 +1
    • Stability: 0.97 → pass security
  • 11 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 5 Nov 26 +1
    • Stability: 0.97 → pass security
  • 3 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 28 Oct 26 +1
    • Stability: 0.97 → pass security
  • 27 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 24 Oct 26 −5
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
  • 17 Oct 26 0
    • Stability: 0.83 → pass security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/x64dbg-mcp-server@2.3.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 93 packages
Packages resolved 93
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 23 exposed · ~823 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
x64dbg_address_convert ~82

Convert Virtual Address (VA) to File Offset, or File Offset to VA

NameTypeReqDescription
actionstringyesConversion direction
addressstring–Virtual address (required for va_to_file)
modulestring–Module name (required for file_to_va)
offsetstring–File offset hex (required for file_to_va)

No output schema declared.

No examples provided.

x64dbg_analysis ~54

Get function info, xrefs, basic blocks or source location for an address

NameTypeReqDescription
actionstringyesInformation to get
querystring–Address to look up (or mnemonic for mnemonic_brief)

No output schema declared.

No examples provided.

x64dbg_antidebug ~35

Anti-debugging analysis: Read PEB/TEB/DEP, or hide debugger

NameTypeReqDescription
action–yes–

No output schema declared.

No examples provided.

x64dbg_breakpoints ~35

Unified tool for all breakpoint operations (set, get, list, configure, toggle, remove)

NameTypeReqDescription
action–yes–

No output schema declared.

No examples provided.

x64dbg_command ~31

Execute x64dbg commands, scripts, eval expressions, or manage debug session

NameTypeReqDescription
action–yes–

No output schema declared.

No examples provided.

x64dbg_control_flow ~28

Get CFG/branch/loop info or manage function definitions

NameTypeReqDescription
action–yes–

No output schema declared.

No examples provided.

x64dbg_database ~53

List known constants, error codes, defined structs, or search strings in a module

NameTypeReqDescription
actionstringyesType of list to retrieve
modulestring–Module name (required for strings action)

No output schema declared.

No examples provided.

x64dbg_debug ~30

Execute core debugger actions (run, pause, step, state, etc.)

NameTypeReqDescription
action–yes–

No output schema declared.

No examples provided.

x64dbg_disassembly ~31

Disassemble or assemble instructions (at address, function, info, assemble)

NameTypeReqDescription
action–yes–

No output schema declared.

No examples provided.

x64dbg_dumping ~34

Dump modules, fix IAT, or get PE header/sections/imports/exports

NameTypeReqDescription
action–yes–

No output schema declared.

No examples provided.

x64dbg_exceptions ~30

Manage exception breakpoints, list Windows exception codes, or skip exceptions

NameTypeReqDescription
action–yes–

No output schema declared.

No examples provided.

x64dbg_handles ~32

List handles/tcp/windows/heaps, get handle name, or close a handle

NameTypeReqDescription
action–yes–

No output schema declared.

No examples provided.

x64dbg_memory ~33

Core memory operations: read, write, info, allocate, free, protect, map

NameTypeReqDescription
action–yes–

No output schema declared.

No examples provided.

x64dbg_modules ~32

List modules or get info (base, section, party) for a specific module

NameTypeReqDescription
action–yes–

No output schema declared.

No examples provided.

x64dbg_patches ~27

List, apply, restore patches or export patched module

NameTypeReqDescription
action–yes–

No output schema declared.

No examples provided.

x64dbg_process ~36

Get process info (basic, detailed, cmdline, elevated, dbversion) or set cmdline

NameTypeReqDescription
action–yes–

No output schema declared.

No examples provided.

x64dbg_registers ~35

Get or set CPU register values (all, specific, flags, avx512, set)

NameTypeReqDescription
action–yes–

No output schema declared.

No examples provided.

x64dbg_search ~28

Pattern/string search, symbol autocomplete, or get string at address

NameTypeReqDescription
action–yes–

No output schema declared.

No examples provided.

x64dbg_stack ~31

Stack operations: call stack, read raw, get pointers/SEH/comments

NameTypeReqDescription
action–yes–

No output schema declared.

No examples provided.

x64dbg_symbols ~25

Symbol, label, comment, and bookmark operations

NameTypeReqDescription
action–yes–

No output schema declared.

No examples provided.

x64dbg_threads ~36

Thread operations: list, get current/specific/teb/name, or switch/suspend/resume

NameTypeReqDescription
action–yes–

No output schema declared.

No examples provided.

x64dbg_tracing ~33

Execution tracing operations: step into/over, run, animate, get trace info

NameTypeReqDescription
action–yes–

No output schema declared.

No examples provided.

x64dbg_watchdog ~32

Check if a watch expression watchdog has been triggered

NameTypeReqDescription
idstring–Watch ID (decimal)

No output schema declared.

No examples provided.

Install

How do I install the io.github.bromoket/x64dbg MCP server?

io.github.bromoket/x64dbg runs locally as an npm package, launched with npx -y x64dbg-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · x64dbg-mcp-server

# add to Claude Code
claude mcp add bromoket-x64dbg -- npx -y x64dbg-mcp-server
Common questions

What is the io.github.bromoket/x64dbg MCP server?

io.github.bromoket/x64dbg is an MCP server listed in the public MCP registry as io.github.bromoket/x64dbg. MCP server for x64dbg debugger - 23 mega-tools for AI-powered reverse engineering and debugging. This page covers its npm package (x64dbg-mcp-server).

Is the io.github.bromoket/x64dbg MCP server safe to use?

io.github.bromoket/x64dbg scores 72 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.bromoket/x64dbg MCP server expose?

io.github.bromoket/x64dbg exposes 23 tools: x64dbg_debug, x64dbg_registers, x64dbg_memory, x64dbg_disassembly, x64dbg_breakpoints, and 18 more. Their descriptions and schemas cost roughly 823 tokens of context every time the server is loaded.

Is the io.github.bromoket/x64dbg MCP server still maintained?

io.github.bromoket/x64dbg is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.bromoket/x64dbg MCP server under?

io.github.bromoket/x64dbg declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the io.github.bromoket/x64dbg MCP server?

VerifyMCP ran 16 checks on io.github.bromoket/x64dbg, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.