x64dbg-mcp-server
Enables AI assistants to automate reverse engineering and debugging workflows, reducing manual inspection time and enabling systematic analysis of binary beh…
x64dbg-MCP Server is a native MCP (Model Context Protocol) plugin for x64dbg that exposes the debugger's full functionality over HTTP. Connect any MCP-compatible AI assistant and control x64dbg programmatically: set breakpoints, step through code, read memory, dump registers, and more. Built with Zig — zero dependencies, single-binary output, cros
- Ask Claude to set breakpoints and step through binary code during reverse engineering sessions.
- Generate memory dumps and register states to analyze program behavior at specific execution points.
- Automate debugging workflows by controlling x64dbg breakpoints and execution flow remotely.
Enables AI assistants to automate reverse engineering and debugging workflows, reducing manual inspection time and enabling systematic analysis of binary behavior at scale.
Security teams and reverse engineers integrating AI-assisted malware analysis or vulnerability discovery into existing x64dbg workflows.
https://github.com/duty1g/x64dbg-mcp-server
By duty1g
How to Get It
claude mcp add x64dbg-mcp-server -- npx -y x64dbg-mcp-server
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.
Once it’s connected, paste this into Claude:
Set breakpoints and step through binary code during reverse engineering sessions
Trust Signals Auto-scanned
Data & Access
Community Pulse New
No community discussions found yet. This doesn't mean the tool isn't good — it may be new or serve a niche use case.
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
Scored from trust signals (evidence-eval-v1): 1,487 GitHub stars; contributors unknown; last commit 0d ago; license MIT.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
Scored from trust signals (evidence-eval-v1): 1,487 GitHub stars; contributors unknown; last commit 0d ago; license MIT.