ClaudeMap

rea

One MCP for reverse engineering across binaries, applications and runtime behavior — from desktop installs and native binaries to Go, GPU code objects, model artifacts, IL2CPP and Godot, shipped as an npm CLI with an explicit official-sources notice

MCP Serversmcp serverreverse engineeringbinariessecurity researchnpmnodejs

REA (Reverse Engineer Anything) is a single MCP server plus npm CLI for reverse engineering across binaries, applications and runtime behavior — see a feature and understand how it works down to the binary level. The README's target table spans 42 classes, including: desktop installations (runtime candidates, supporting files, component markers and next probes), native binaries (pseudocode, assembly, strings, symbols, calls and references — requires a native analysis engine: Hopper, Ghidra, IDA or Kuna), offline ELF layout (sections, segments, original symbols/relocations and static mitigation candidates; caller-supplied pwntools on Linux x64), Go binaries (embedded compiler version, modules, replacements and build settings), GPU code objects (CUDA/HIP targets, selected kernel parameters and resources, retained PTX text), model artifacts (GGUF / safetensors metadata, tensor declarations and derived totals), IL2CPP metadata (Unity global-metadata.dat assembly images, type and method names and index ranges), Godot PCK (archive inventory and extraction, header/directory facts and content identities) and Rust binaries (embedded cargo-auditable crate names, versions, sources and dependency edges) — most are built-in, needing no extra tooling. Install with npx rea-agents setup (or npm install --global rea-agents); it requires Node.js 22.x (>=22.23.4), 24.x (>=24.22.1) or 26.12.1+, plus npm. The README carries an anti-impersonation notice: get REA only from morluto/rea, rea.tools, or the rea-agents npm package — a similar repository name or copied README does not establish that a download is official. Guides and showcases live at rea.tools.

What it does

  • 42 target classes in one MCP, including: desktop installations, native binaries, offline ELF layout, Go binaries, GPU code objects (CUDA/HIP, PTX), model artifacts (GGUF/safetensors), IL2CPP metadata (Unity), Godot PCK and Rust binaries (cargo-auditable)
  • Most targets are built-in with no extra tooling; native-binary analysis requires a native analysis engine (Hopper, Ghidra, IDA or Kuna), and offline ELF layout analysis uses caller-supplied pwntools (Linux x64)
  • Ships as the rea-agents npm package with npx rea-agents setup; updates via rea update
  • Explicit official-sources notice: only morluto/rea, rea.tools and the rea-agents npm package are official — similar names or copied READMEs are not proof of provenance
  • Docs, guides and showcases at rea.tools; community on Discord

When to use it

Use when an agent needs to answer how something works below the source level — understanding a feature of a closed desktop app, inspecting what a native binary actually calls, auditing a shipped GGUF/safetensors artifact's tensor declarations, or inventorying a Unity IL2CPP build's types and methods. Keep it on software you own or are licensed to analyze.

Getting started

With Node.js and npm installed:

npx rea-agents setup

Or install globally:

npm install --global rea-agents
rea --help

Requirements: Node.js 22.x (>=22.23.4), 24.x (>=24.22.1) or 26.12.1+, plus npm. Updates for a globally installed CLI: rea update. Register it with your MCP client per its config format; the README's docs/reference/mcp-contracts.md carries the generated tool catalog.

Things to know

Capability is target-dependent and the README states the split honestly: native binaries need a native analysis engine (Hopper, Ghidra, IDA or Kuna — external tools), offline ELF layout analysis uses caller-supplied pwntools (Linux x64), and the remaining classes are built-in — check the table before assuming a target works out of the box. Node version floors are specific (22.x >=22.23.4, 24.x >=24.22.1, or 26.12.1+). The anti-impersonation notice exists because copycat repos with similar names and copied READMEs circulate — treat only morluto/rea, rea.tools and the npm package as official, per the README's own instruction. Reverse engineering is legally sensitive in some jurisdictions; the tool is neutral, the target choice is not. MIT. 468,071 stars as of writing (2026-11-19).

Repository

morluto/rea

Charted

Related on the map

  • Blitz Strike

    MCP Server

    A penetration-testing methodology delivered as one MCP server: BLITZ maps the attack surface, EAGLE-EYE traces source-to-sink, STRIKE live-verifies every finding before it is reported.

    • mcp-server
    • security
    • pentest
    • methodology
  • Ripwire

    MCP Server

    Red Hat's "ripgrep for AI context" — a C++23 zero-dependency CLI that also speaks MCP.

    • mcp
    • code-context
    • cli
    • red-hat
  • Deja Vu

    MCP Server

    One shared session memory for 25+ coding agents — Claude Code, Codex, and Cursor finally remember the same project.

    • mcp
    • memory
    • cross-agent
    • context