x64dbg MCP v0.1.9 - optional injector compatibility fixes

ScyllaHide launch compatibility fixes and a smaller tool catalog.

• Launch tools now default to use_scyllahide="off"; auto also skips injection. Explicit force uses the requested profile through an isolated InjectorCLI configuration and an exact PID.
• The compatibility configuration disables both NtContinueHook and KillAntiAttach. The latter can implicitly enable the former in upstream ScyllaHide. The result reports the applied overrides.
• Native injector output must confirm success for the requested PID; a zero exit code alone is insufficient. Invalid profiles fail before the target launches.
• Removed the obsolete kernel-driver integration and its six tools. The full catalog contains 290 tools; compact exposes 40.
• Updated the English/Russian setup notes, generated tool reference, and Glama maintainer metadata.

Validation: Python contract tests; three simultaneous stdio clients; native builds/tests for x86 and x64; packaged runtime smoke tests. Live x64 regression checks on the previously failing target passed for Basic, Obsidium x86/x64, and auto: entry-point breakpoint, register/memory capture, verified write and restoration. Other target/profile/Windows combinations remain environment-dependent.

Download x64dbg-mcp-windows-v0.1.9.zip for both plugins, Python runtime sources, documentation, self-contained managed probes, and IDA evidence coordinators. Follow the README to install the plugins and Python requirements. Verify downloads with SHA256SUMS.txt.

MCPB clients can use x64dbg-mcp-v0.1.9.mcpb (full bundle). x64dbg-mcp-local-v0.1.9.mcpb is the smaller Smithery-compatible bundle: it includes the native plugins and Python sources but omits the optional self-contained .NET probes. See its INSTALL.md for adding managed diagnostics from the full Windows bundle. Both MCPB packages require a local Windows x64dbg installation and uv; configure the installation root during setup.

x64dbg MCP v0.1.8 — complete Windows bundle and runtime fixes

Changes

• Direct InitDebuggee now starts the matching debugger architecture, refreshes the bridge identity, and returns the current session binding.
• String/reference searches preserve complete paginated results and resolve x64dbg's hexadecimal reference addresses correctly.
• The Windows bundle includes self-contained .NET 8 managed probes for both x86 and x64, with runtime licenses and third-party notices.
• The bundle now includes the tool reference, documentation assets, and both IDA evidence coordinators.
• Build instructions and CI use the Visual Studio 2022 toolchain consistently. Session unit tests isolate their fake process lists from real bridge authentication files.

Installation

Download x64dbg-mcp-windows-v0.1.8.zip and verify it against SHA256SUMS.txt.

1. Copy plugins/MCPx64dbg.dp64 into <x64dbg-root>/x64/plugins/ and plugins/MCPx64dbg.dp32 into <x64dbg-root>/x32/plugins/.
2. Keep the complete runtime directory together, create a Python 3.11+ environment, and install runtime/requirements.txt.
3. Configure the stdio client using runtime/README.md and runtime/src/mcp_stdio_launcher.py.

The managed probes ship with their own .NET runtime. IDA integration requires a separately installed and configured IDA environment.

Validation

• GitHub CI passed on Python 3.11 and 3.14; 477 Python tests, both native plugin builds, six native tests, and both managed probe builds.
• Local checks passed for stdio multi-client operation and result contracts across inspect, standard, automation, and full tool profiles.
• The local live matrix exercised 70 scenarios across x86 and x64. The first sweep passed 68; both failed scenarios passed isolated reruns. The heap cleanup failure was traced to unit-test interference and the responsible tests were fixed.
• An x86 exception-unwind fixture encountered a startup timeout in the first sweep, then passed three consecutive isolated runs. This is retained as an observed intermittent limitation; successful reruns do not establish that the underlying timing issue is fixed.
• The published assets were downloaded and independently verified: all three SHA-256 hashes matched, all 40 tracked runtime source files matched the tagged checkout, both managed probes executed, both IDA coordinators loaded, and three stdio clients completed three tool-list requests each.

Live validation used generated deterministic fixtures on one Windows installation. It does not establish exhaustive coverage of all tools, Windows versions, or arbitrary protected targets.

x64dbg MCP v0.1.7 — target-first startup

What’s new

• New MCP sessions now use InitDebuggee as the first call when the target EXE path is known.
• It detects x86/x64, starts the matching debugger from X64DBG_ROOT, waits for the authenticated bridge, and opens the target.
• BridgeHello remains available for diagnostics and points inactive sessions back to InitDebuggee.

Quick setup

Download x64dbg-mcp-windows-v0.1.7.zip. It contains both plugins and the Python backend:

• plugins\MCPx64dbg.dp64 → <your-x64dbg-root>\x64\plugins\
• plugins\MCPx64dbg.dp32 → <your-x64dbg-root>\x32\plugins\
• runtime\src + runtime\requirements.txt

Extract the bundle, copy both plugins, create a Python 3.11+ environment inside runtime, and use the Codex, Claude Code or generic stdio configuration from the README.

SHA256SUMS.txt contains the hashes for the bundle and both plugin assets.