DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to find the original entry point of a packed binary with X64 DBG MCP Server

Use an AI assistant to load a packed executable in x64dbg, detect its OEP, and dump the module to disk.

Authorization notice. X64 DBG MCP Server is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Reverse engineering. Unpacking and dumping third-party executables should only be done with authorization and for lawful analysis.

Credentials. The Bearer token grants full debugger control, so keep it private and rotate it with Generate if it is exposed.

Who it is forA malware analyst or reverse engineer who has a packed executable and needs the unpacked code for static review.

The problemPacked executables hide their real code behind a loader, so manual unpacking in the debugger takes many steps and careful tracing.

The outcomeThe assistant reports the detected Original Entry Point and the path of a dumped module file that can be examined further.

What you need first

  • Windows with x64dbg installed, or a Windows target for the plugin
  • The release contents of dist/ or Zig 0.16-dev or later to build from source
  • An MCP-compatible AI assistant client that can send HTTP requests with a Bearer token
  • Authorization to analyze the target software

Steps

  1. Build the plugin with zig build -Doptimize=ReleaseSafe --prefix dist or download the latest release.
  2. Copy the contents of dist/ into your x64dbg root folder.
  3. Launch x64dbg. The MCP server starts automatically on 0.0.0.0:9094 for x64.
  4. Copy the Bearer token from Plugins > x64dbg-MCP Server > Configure MCP Server... and add the Streamable HTTP config with the Authorization header to your MCP client config.
  5. Ask the assistant to load the target, call DetectOEP, then call DumpModule.

Prompt for your agent

Using the x64dbg-MCP-Server MCP tools at http://localhost:9094/ with my Bearer token, load <target executable path>, call DetectOEP, then call DumpModule. Report the Original Entry Point address and the dump file path. Verify that the dump file exists on disk.

Caveat. The README lists DetectOEP and DumpModule as tools, but it does not describe their output format, so check the returned values against the dump file.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page