REA (Reverse Engineer Anything) is a Docker-based reverse engineering toolkit that includes Android APK analysis tools such as JADX, Apktool, and ADB. Ghidra can be used if needed. This setup provides a token-protected, streaming-capable HTTP MCP endpoint, MCP stdio support, and a command-line interface (CLI).
REA is Morluto's MCP server and CLI, designed to assist AI agents in analyzing software without access to the source code. It can analyze Android APKs, trace code references, examine application resources, interact with devices using ADB, analyze Electron packages, and inspect .NET assemblies, Go binaries, and Rust programs. Unlike the npm package `rea-agents`, which requires separate installation of dependencies such as JDK, JADX, and Apktool, this Docker image contains all the necessary tools in a single environment.
An MCP server for reverse engineering applications, binaries, and runtime behavior.
Examine a function's code to understand how it works, from application logic to binary-level details.
Ask your programming agent to examine an application, game, or website. REA provides tools to analyze the internal implementation and understand how various functions work.
How it works
Reverse engineering involves examining software to understand its internal logic and behavior. REA allows an AI agent to analyze code, follow references, interpret functionalities, and recreate specific functions.
Request a function
Provide your agent with a program, application, or webpage and describe the behavior you want to understand.
Examine the software
REA provides compatible code, references, resources, and runtime observations to help the agent examine the target.
Understanding and replicating functionality
The agent analyzes the results, explains the implementation, and helps you create or adapt a similar function.
Why does the dinosaur speed up?
The faster the player runs, the faster the dinosaur becomes in the game. To replicate this behavior with adjustable speed settings, you must first identify the rule that controls acceleration.
Investigating Speed
Ask your agent to investigate the dinosaur game, explain why the speed increases, identify the relevant code, and create a simplified version with speed control.
Identifying the Speed Rule
REA helps the agent investigate the game logic and analyze the speed changes. An example rule might start with a speed of 6 and increase slightly with each update until it reaches 13.
Testing the Results
Using the identified rule, the agent can recreate the game mechanics in a small game and add a speed slider. You can then play and adjust the speed to observe the changes in behavior.
Creating the Percent Key on a Calculator
The percentage key on a calculator can follow different rules depending on the selected operation. REA can help test the implementation and replicate the corresponding calculations on a small calculator.
1. Asking about the percent key
Ask your employee to review the percent key on the Windows calculator, test its functionality after addition and multiplication, and implement both rules in a demonstration.
2. Determining the calculation rules
REA will help your employee test the code for percentage calculations. A simple example:
Using +
Calculate the percentage of the first number.
10% of 200 = 20
200 + 20 = 220
Using ×
Convert the percentage to a decimal.
10% = 0.1
200 × 0.1 = 20
3. Testing the percent key
The employee can replicate these rules on a small calculator. Select an operation, enter the number, press %, and then = to display the result.
Choosing your target
Available guides explain how to set up REA and begin auditing various types of software.
Native Binaries
Examine executable files and libraries by analyzing relationships between functions, strings, references, and calls.
JavaScript and Electron
Explore application modules, routes, inter-process communication (IPC), native dependencies, and the Electron ASAR file.
Browser and Runtime Activity
Capture browser or supported process activity and compare observations across multiple runs to
