What it does
The server exposes two groups of tools to an MCP-compatible agent. The live-debugging core drives x64dbg, cdb (WinDbg) and Frida, providing breakpoints, stepping, register and memory access, call stacks and checkpoints. The static-analysis suite covers PE, ELF, Mach-O, .NET, APK, Unity IL2CPP, WASM/EVM, firmware and browser HAR files, using backends such as Ghidra, rizin, dnfile, ILSpy, jadx and apktool. Its built-in prompts cover packer, .NET malware, Android, PE crash and ELF triage, binary diffing and evidence reports. When a backend is missing, the tool reports it as unsupported and includes an install hint rather than returning a guessed result.
It suits someone who wants an agent to examine a binary and answer from the file's contents, for example when triaging a suspicious executable, decompiling a .NET assembly, decoding an APK, reviewing a Mach-O header or a PCAP with TLS keylog decryption, or comparing two versions of a binary function by function. The static tools run on any platform, while the live debuggers are Windows-only.
Running it requires Node.js 20 or later. Other backends are optional, and a doctor command reports which ones are present on the machine. The server runs over stdio for local clients or over streamable HTTP for shared setups. A Docker image is published to GHCR, though the Windows debuggers report as unsupported inside a Linux container. The REA_TOOLSETS setting lets clients with small context windows load only part of the tool set.
Limitations and requirements
Node.js 20 or later is required. The live debuggers (x64dbg, cdb, Frida attach) require Windows. Other analysis backends such as Ghidra, rizin, jadx and Il2CppDumper are optional and must be installed separately; tools that depend on a missing backend return an unsupported-capability error. Without an HTTP token, only a 44-tool read-only allowlist is registered. Mutating live-debug calls require confirm:true. Windows-only debuggers report as unsupported inside Docker Linux containers.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
Reverse Engine Anything Plus
Conduit live-debug core (30 frozen tools) + Rea static RE domains over MCP stdio/HTTP.
v0.13.0As shown on registry.modelcontextprotocol.io when we last read it