morluto / rea

REA · Reverse Engineer Anything · one MCP

Start at what you see.
End at what runs.

See a feature in an app you want in your own product? Ask your agent to investigate it with REA. It can inspect the app without its source code, explain how the feature works, show the evidence, and build a version for your project.

npx rea-agents setup
Read the case studies View source
Three real tracesthe project's own showcases, step by step
01DX-Ballnative · original x86
  1. sound call
  2. position-to-pan helper
  3. instructions
  4. incomplete pseudocode
  5. C
RESULT
passes 3,205 original-x86 cases · reproduces all 63 compiled function bytes
CASE
rea.tools/showcase/dx-ball
02Notionelectron · clipboard bridge
  1. renderer clipboard API
  2. preload
  3. IPC
  4. main process
  5. rich clipboard format
RESULT
the bridge traced from renderer to main process, and the rich format inspected
CASE
rea.tools/showcase/notion
03TH04DOS · PC-98 · 16-bit
  1. 16-bit instructions
  2. fixed + aimed angle calculations
  3. reconstructed C++
CHECK
compared with the historical compiler output
CASE
rea.tools/showcase/th04
What you can point it at12 targets, from the README
01
Native binariespseudocode, assembly, strings, symbols, calls, references
02
Offline ELF layoutsections, segments, symbols, relocations, mitigation candidates
03
EVM bytecodedispatch selectors, byte offsets, inferred arguments, mutability
04
Recorded Linux crashesraw notes, every recorded thread's registers and signals
05
JavaScript / Electronmodules, imports, source maps, routes, IPC, native add-ons
06
Websitespage structure, scripts, network observations, screenshots
07
Saved network capturesrequests, responses, exposed payloads, source locations
08
.NET assembliesmetadata, CIL, native dependencies, build comparisons
09
Android APKsmanifest declarations, classes, decompiled methods, references
10
Firmwareregions, extraction results, native-analysis handoffs
11
Packages and resourcesinventories, digests, plists, Apple bundle anatomy
12
Process behaviorterminal output, interactions, exit and filesystem observations

REA analyzes targets locally. Deep native analysis uses Hopper, Ghidra or IDA; static JavaScript and .NET inspection need no native engine.