Skill Detail

Inspect a paused Windows executable with x64dbg MCP

Load an authorized Windows executable, pause at a breakpoint, and collect registers, memory, disassembly, and call-stack evidence through x64dbg MCP.

Runbooks & DiagnosticsMCP
Runbooks & Diagnostics MCP Security Reviewed
⭐ 2.8k GitHub stars
COPY SKILL INSTRUCTIONS (OPTIONAL)
npx skills add agentskillexchange/skills --skill inspect-paused-windows-executable-with-x64dbg-mcp Copy
Uses the third-party skills CLI, not an ASE-owned installer. Check your agent’s compatibility. This copies instructions; complete the upstream tool setup below separately.
At a glance
Tools required
Windows, x64dbg/x32dbg, upstream native MCP plugin, HTTP MCP client with bearer-header support
Install & setup
Download x64dbg-MCP-Server-v1.7.zip from https://github.com/duty1g/x64dbg-mcp-server/releases/tag/v1.7, extract it, and copy dist/ contents into the x64dbg root. Launch the matching debugger, set the desired bind address in Plugins > x64dbg-MCP Server > Configure MCP Server, and configure the MCP URL plus generated bearer token.
Author
duty1g
Publisher
Community
Last updated
Nov 12, 2026
Quick brief

Invoke this workflow when a debugging agent needs reproducible evidence from a Windows executable rather than asking an operator to copy debugger panes by hand. Inputs are the authorized executable or process, target architecture, breakpoint or failing address, and a bounded inspection question. The output is a debugger-state report tied to a specific pause, with addresses and observed evidence.

How it works

What this skill actually does

Install the upstream v1.7 plugin by extracting its release archive and copying the contents of dist/ into the x64dbg root. Launch the matching x32 or x64 debugger. In the plugin configuration, use local-only binding for a local client and copy the generated bearer token into the client’s protected configuration. The documented HTTP MCP endpoint is http://localhost:9094/ for x64, or port 9095 for x32, with an Authorization bearer header. The upstream default listens on all interfaces; configure the intended bind address explicitly.

Start with GetDebugState. Use LoadBinary for the selected target, SetBreakpoint at the authorized inspection point, then run and WaitForPause. Confirm that the paused process and instruction pointer match the requested case. Collect GetAllRegisters, a bounded ReadMemory range, Disassemble, and GetCallStack. Step with StepOver only when the question requires it, recording the new instruction pointer and keeping before-and-after observations separate.

Return target identity, breakpoint, pause state, relevant registers, memory range, disassembly, call stack, and any unresolved symbols or failed calls. Retain the process in the operator’s requested state. This procedure is limited to loading, execution control, and observation; memory patching, unpacking, and general command execution are separate tasks. Tool calls use the upstream MCP interface, so MCP is the defensible framework. Source snapshot: v1.7 source. Installation, authentication enforcement, and debugger operation were not executed during discovery review.