Summary

Cheat Engine, x64dbg and an API monitor, all reachable from the conversation — with a token gate on anything destructive.

The scale is the point and also the problem: 250+ tools do not fit in one client, which is why it ships as four servers split by job and each stays under the tool ceiling. Ask for the health value and freeze it, or for every function referencing a string, and the model does the address arithmetic. Two things to weigh before installing: this injects a DLL into a live process, so anti-cheat and endpoint protection will treat it exactly as it looks, and the author labels the project experimental with APIs that may change without notice. The safety modes are not decoration — Educational blocks dangerous operations outright, and patch history means a bad write can be undone.

What it is

A Rust toolkit that injects an agent DLL into a target Windows process and exposes its internals through four MCP servers, so an assistant can inspect memory, disassemble code, set breakpoints and run code inside it.

What you get

Memory work in the Cheat Engine mould: typed reads and writes, region enumeration with protection flags, AOB pattern scanning with wildcards, and pointer chain resolution
A value scanner with 12 scan modes — exact, changed, increased, between, unknown initial and more — refined iteratively, exportable as JSON, CSV or Cheat Engine XML
A pointer scanner with configurable depth, static base filtering, stability scoring across rescans, and rescan after restart
Static analysis: disassembly through Capstone with disasm_at and disasm_function, pseudo-C decompilation, PDB symbols, cross-references and string extraction
In-process debugging: INT3 software breakpoints, four hardware breakpoints through the debug registers, single stepping, thread control, full register access and stack walking
Execution and injection: x86/x64 assembly from text, function calls across five calling conventions, shellcode run by direct call, new thread, APC injection or thread hijacking, and code cave discovery
Hooking: inline trampolines, IAT and EAT hooks, VEH and PAGE_GUARD memory breakpoints, syscall stub patching, and a ROP gadget finder
Win32 API call tracing with argument decoding, filters, presets and per-API statistics, plus parameter and return value override behind conditional breakpoints
Memory dumping with PE reconstruction, minidumps, incremental dumps and binary diffing between snapshots
External tool backends behind one API: Radare2 through r2pipe, Ghidra headless, and IDA Pro through idalib
Safety machinery: Educational, Standard and Expert modes, protected-process blocking, rate limits, undo through patch_undo and previews through patch_preview

Requirements

Windows, and a target process you are allowed to inject into — ghost-loader.exe attaches by name or PID. Built with cargo build --release. Registered as four separate servers because of the client tool ceiling: ghost-core-mcp on 13340, ghost-analysis-mcp on 13341, ghost-static-mcp on 13342 and ghost-extended-mcp on 13343, with the injected agent listening on 13338. Destructive operations are gated: call safety_request_token first and pass the token_id with the operation. The repository labels itself experimental, with APIs subject to change.

Setup effort

Build from source — clone the repository and build it, then point your client at the binary