Atlas / MCP servers / wasdubya / X64dbg

X64dbgSAFE

mcp/wasdubya/x64dbg

Model Context Protocol for x64dbg & x32dbg

Verdict
SAFE
Grade
B
Trust score
89 /100
Exposed tools
56 56r · 0w · 0d
Transport
—
License
GPL-3.0
Stars
585
01

Overview

From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.

x64dbg MCP

An MCP server that can bridge various LLMS (Claude and Cursor tested) with the x64dbg debugger, providing direct access to debugging applications through prompts. Features (Build from Source for Latest)

  • 40+ x64dbg SDK Tools - Provides access to almost every single debugging feature given by the SDK for smart debugging.
  • Cross-Architecture Support - Works with both x64dbg and x32dbg.
  • API Compatibility - Runable from cmd using the args given in the python file.

Quick Setup in 3 Steps

  1. Download Plugin
  2. Grab .dp64 or .dp32 from this repo's build/release directory
  3. Copy to your local: [x64dbg_dir]/release/x64/plugins/
  1. Configure Claude Desktop
  2. Copy x64dbgmcp.py from this repos src directory, ensure to ``pip install mcp requests``
  3. Update local claudedesktopconfig.json with path to x64dbgmcp.py
{
"mcpServers": {
"x64dbg": {
"command": "Path\\To\\Python",
"args": [
"Path\\to\\x64dbg.py"
]
}
}
}
  1. Start Debugging
  2. Launch x64dbg
  3. Start Claude Desktop
  4. Check plugin loaded successfully (ALT+L in x64dbg for logs)

Build from Source for Latest Features! CMake and MSVC should be installed and on PATH

  • git clone https://github.com/wasdubya/x64dbgmcp
  • cd x64dbgmcp
  • cmake -S . -B build (will resolve the pluginsdk automatically, so no need to worry about dependencies.)
  • cmake --build build
Read from source at commit 1d463ee3b4faOBSERVED · 2026-09-30
02

Exposed tools (56)

56 read · 0 write · 0 destructive.

ToolRiskDescription
AssemblerAssembleread
AssemblerAssembleMemread
CommentGetread
CommentSetread
DebugDeleteBreakpointread
DebugPauseread
DebugRunread
DebugSetBreakpointread
DebugStepInread
DebugStepOutread
DebugStepOverread
DebugStopread
DeleteHardwareBreakpointread
DisasmGetInstructionRangeread
EnumHandlesread
EnumTcpConnectionsread
ExecCommandread
FlagGetread
FlagSetread
GetBranchDestinationread
GetBreakpointListread
GetCallStackread
GetMemoryMapread
GetModuleListread
GetPatchAtread
GetPatchListread
GetRegisterDumpread
GetTebAddressread
GetThreadListread
IsDebugActiveread
IsDebuggingread
LabelGetread
LabelListread
LabelSetread
MemoryBaseread
MemoryGetProtectread
MemoryIsValidPtrread
MemoryReadread
MemoryRemoteAllocread
MemoryRemoteFreeread
MemoryWriteread
MiscParseExpressionread
MiscRemoteGetProcAddressread
PatternFindMemread
QuerySymbolsread
RegisterGetread
RegisterSetread
SetHardwareBreakpointread
SetPageRightsread
StackPeekread
StackPopread
StackPushread
StepInWithDisasmread
StringGetAtread
XrefCountread
XrefGetread
03

Trust audit

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

LayerWhat it checksResult
L0Provenance & inventoryPASS
L1Static analysis of the codeWARN
L2Instruction surface (what it tells the agent)PASS
L3Class-specific surfacePASS
L4Behavioural (sandbox)SKIPPED

What the source does

Filesystem
none-observed
Network
declared (4 observation(s))
Shell
none-observed
Dependencies
pinned
Secrets in source
none-found

Findings (1)

MEDIUMNetwork egress · net.raw_ip · CWE-200, CWE-319
src/x64dbg.py:10
DEFAULT_X64DBG_SERVER = "http://127.0.0.1:8888/"

Gates applied: no_behavioural_pass.

Audited 2026-09-30 · audit v0.4.1 · source sha 1d463ee3b4fafull audit observations/trust-audit/mcp-server/wasdubya__x64dbg.json · Report an issue / request a re-scan
04

Audit history

Every audit this server has had. A grade with a past is a grade somebody is still checking.

DateSourceVerdictGradeScoreChange
2026-09-301d463ee3b4faSAFEB89first audit
05

Questions

What is the X64dbg MCP server?

Model Context Protocol for x64dbg & x32dbg

What tools does X64dbg expose?

56 in total: 56 read-only, 0 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.

Is X64dbg safe to connect to an agent?

The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.

What credentials does X64dbg need?

It reads ANTHROPIC_API_KEY from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.

How current is this page?

The grade is for one exact copy of the source (1d463ee3b4fa), read on 2026-09-30. The repository is watched and re-audited when it changes.

Advertisement