OmniREA Live Reverse Engineering Server
Provides Android APK inspection capabilities and Android-focused reverse engineering reference material within the OmniREA toolset.
Handles ARM64 binary analysis and cross-architecture ARM64-to-x86 parity verification scenarios.
Supports Electron app reverse engineering, including ASAR unpacking and discovery of hidden .vite/.webpack build trees during triage.
Supports Linux/ELF analysis with ELF detection and native Linux commands such as readelf and nm.
Supports macOS/Mach-O analysis with Mach-O loader tooling and native macOS commands such as otool and plutil.
Supports WebAssembly analysis through WASM magic-byte detection and dedicated REAP domain playbooks.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@OmniREA Live Reverse Engineering Servertriage this binary and extract endpoints and API keys"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
OmniREA: Two-Tier Autonomous Reverse Engineering Framework
Table of Contents
Related MCP server: rizin-mcp
The Actual Problem
Most AI reverse engineering setups right now hit one of two walls:
The MCP Token Dump: You load an MCP server with 200+ tools. Before your agent even reads the first byte of your binary, 372,000 tokens of JSON schema are dumped into the prompt. Turns get sluggish, queries cost $0.10 to $0.30 each, and the context window runs out of room before you reach the actual logic.
The Dumb Grep Trap: You strip away all tools and rely entirely on
stringsandgrep. It works great for finding an unencrypted API key in two seconds—until you hit obfuscated control flow, custom XOR ciphers, or an ARM64-to-x86 bridge where regex simply cannot tell you if two functions do the same thing.
OmniREA exists to stop picking between those extremes.
It sets up an intelligent Two-Tier Pipeline: 80% of routine triage (unpacking ASARs, checking headers, finding strings, dumping PE exports) runs locally through fast terminal commands with zero tool schema overhead. When you hit a routine that actually needs decompilation, CFG analysis, or register-level proof, the agent escalates to Tier 2 with Ghidra and Unicorn CPU emulation.
flowchart TD
Target[Target Binary / APK / Electron / Bundle] --> Router{Complexity & Task Check}
subgraph Tier1 [Tier 1: Fast Path - Zero-MCP CLI]
Router -->|Triage / Strings / Endpoints / Version| FastPath[Native Terminal Recon]
FastPath --> TriageDone[Fast Answers: 0 MCP Token Overhead, ~1-2 Turns]
end
subgraph Tier2 [Tier 2: Deep Path - ReAgent + REA MCP]
Router -->|Decompilation / CFG / Structs / Cryptanalysis| Escalate[Escalate to Heavy Engine]
Escalate --> MCP[REA MCP + IDA / Ghidra / Frida]
MCP --> Parity[11-Signal Parity Verification & Differential Emulation]
end
TriageDone -.->|Need Formal Proof?| EscalateEmpirical Benchmarks (Local Machine Measurements)
Measured directly on Windows 11 (AMD Ryzen 7, Node.js v22) across real binary and source targets. Anyone can verify and reproduce these measurements locally by running npm run bench or npm run bench:compare:
1. Head-to-Head Architectural Matrix (Real Target: test/fixtures/sample-app/bundle.js)
Metric | Monolithic Heavy REA MCP | OmniREA Tier-1 Fast Path | OmniREA Tier-2 Deep Verify |
Tool Schemas In Context | 213 schemas (~382,580 tok) | 0 schemas (0 tokens) | Isolated on-demand |
Triage Execution Latency | ~1,500 – 4,000 ms per RPC | 56.6 ms ( | 58.0 ms (with solver) |
Payload Injected into LLM | ~120 – 850 KB verbose dumps | 1,531 bytes clean JSON | Structured Proof Report |
Agent Turns to Solve | 3 – 5 conversational turns | 1 turn (instant triage) | 1 turn verification |
Algorithmic Math Solving | Heavy manual loop | Flags hypothesis | Synthesizes & Proves Key |
11-Signal Parity Audit | Manual / external | N/A (Recon only) | 11/11 Verified (PASS) |
2. Micro-Level Operation Benchmarks (Native System Targets)
Operation & Target | Monolithic Heavy REA MCP | OmniREA Tier-1 Fast Path | Measured Difference |
Tool Schema Prompt Overhead | 836.9 KB JSON (~372,600 tokens) | 0.0 KB (0 tokens) | 100% token elimination |
PE Binary Triage ( | Ingests 213 tool schemas + disassembler | 61.8 – 78.8 ms ( | Instant (<80ms) (structured JSON payload) |
Credential & Endpoint Triage ( | Ingests 213 tool schemas + AST relations | 60.2 – 77.7 ms ( | Instant (<80ms) (structured JSON payload) |
Payload Size Delivered to AI | Megabytes of tool schemas & AST nodes | 261 – 1,543 bytes structured JSON | 99.9% smaller payload |
All timings are 5-pass local performance averages measured with performance.now() in Node.js via npm run bench and npm run bench:compare.
1-Click Turnkey AI Assistant Setup
You can wire OmniREA directly into Google Antigravity, Cursor IDE, Claude Code, or Claude Desktop with one command:
# Auto-detects your environment and installs everything:
npx omnirea setupOr target your specific setup explicitly:
npx omnirea setup antigravity # Copies 213 REA tool schemas + 3 skills to ~/.gemini/
npx omnirea setup cursor # Deploys .cursorrules & configures .cursor/mcp.json
npx omnirea setup claude # Deploys CLAUDE.md & configures claude_desktop_config.json
npx omnirea setup workspace # Configures the current repository directoryWhat gets installed:
213 REA Tool Schemas: Bundled directly in
mcp/rea/. Covers PE resources, AST dataflow, Frida scripts, Mach-O loaders, and Android APK inspection.3 Agent Skills: Installed into your agent's brain (
omnirea,lean-recon,deep-verify).9 In-Depth Domain Reference Manuals: Located in
skills/omnirea/references/(covering Android, Electron, PE/ELF/Mach-O, Frida, and ReAgent).16 REAP Domain Playbooks: Pre-formatted tactical workflows for games, firmware, kernel drivers, and WebAssembly.
AI Behavioral Rules:
.cursorrulesandCLAUDE.mdto force the AI to triage with fast CLI tools first before firing up heavy disassemblers.
Manual Copy-and-Paste MCP Configuration
If you prefer to configure your AI assistant manually rather than using npx omnirea setup:
Cursor IDE (.cursor/mcp.json)
{
"mcpServers": {
"rea": {
"command": "npx",
"args": ["-y", "@morluto/rea"],
"description": "OmniREA Live Reverse Engineering Server (213 Tools)"
}
}
}Claude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"rea": {
"command": "npx",
"args": ["-y", "@morluto/rea"]
}
}
}Google Antigravity & Gemini CLI
Copy the bundled mcp/rea/ directory directly into:
Windows:
%USERPROFILE%\.gemini\antigravity\mcp\reamacOS/Linux:
~/.gemini/antigravity/mcp/rea
3 Ready-to-Paste Agent Magic Prompts
Copy and paste these prompts directly into Cursor, Claude, or Antigravity for instant results:
1. Instant Application Triage
Analyze the main components, entry points, and high-confidence attack surface of <target>.
Separate your findings into Confirmed Facts (with Evidence IDs), Inferences, and Residual Unknowns.
Do not execute the binary.2. Secret & Endpoint Hunting
Scan <target> for hardcoded credentials, authorization headers, private API routes, and cloud storage URLs.
Provide the exact string window with 50 characters of surrounding context and file offsets.3. Clean-Room Algorithmic Reconstruction
Decompile the logic of <target_function> from <target_binary> and reconstruct it in clean-room Python.
Generate a CLONE_SPEC.md document verifying behavioral equivalence against the 11 ReAgent parity signals,
including register calling conventions and differential CPU emulation output.Standalone Terminal Commands
If you don't use an AI agent, you can run the CLI tools directly:
# Detect file magic, architecture, format, and hashes
npx omnirea scan ./target-binary.exe
# Extract leaked API keys, tokens, endpoints, and IPs in <1s
npx omnirea triage ./app.asar
# Tier-2: 11-signal ReAgent formal parity audit & constraint solver
npx omnirea verify ./bundle.js
# Audit your machine for disassemblers, compilers, and toolchains
npx omnirea doctor
# List all 16 domain playbooks
npx omnirea playbooksThe Two Tiers in Detail
Tier 1: Fast CLI Reconnaissance (Zero MCP Overhead)
Most reverse engineering tasks are reconnaissance. Tier 1 handles:
Magic Byte Identification: Instant PE, ELF, Mach-O, WASM, SQLite, and ZIP detection.
Windowed String Extraction: Never dumps entire files into context. Uses regex window slicing (
.{0,100}NEEDLE.{0,100}) to capture surrounding code context without token blowup.Hidden Folder Discovery: Uses
rg -uuto uncover hidden.vite/and.webpack/build trees in Electron apps.Cross-Platform Matrix: Includes native commands for Windows PowerShell (
dumpbin,Select-String), Linux (readelf,nm), and macOS (otool,plutil).
👉 See cheatsheets/cross-platform-cli.md for the complete command cheat sheet.
Tier 2: Deep Formal Verification (ReAgent + REA MCP)
When you need to decompile an obfuscated function or prove that clean-room Python or C++ code behaves identically to the original binary:
Live REA MCP Server: Interacts directly with
@morluto/rea(213 tools).The 11 ReAgent Verification Signals:
CFG topology & loop invariants
Calling convention & register usage
Stack frame layout & local variable offsets
Memory read/write access patterns
API call sequence order
Return code & exception handling parity
Cryptographic constant matching
Endianness & bit-shifting precision
Floating-point rounding parity
Dynamic timing & branching consistency
Unicorn CPU differential emulation (fuzzing registers side-by-side)
Deliverable Artifact: Produces a structured
CLONE_SPEC.mdwith complete type signatures, data structures, and equivalence test harnesses.
👉 See skills/deep-verify/SKILL.md for full verification protocol details.
The 16 REAP Domain Playbooks
# | Playbook | Focus Area |
01 | First look at an unfamiliar app, attack surface & entry points | |
02 | Follow UI button clicks down to backend logic & syscalls | |
03 | Deep triage of PE, ELF, and Mach-O executables | |
04 | Clean-room reconstruction & 11-signal ReAgent parity | |
05 | Unity IL2CPP, Unreal Engine PAKs & game logic recovery | |
06 | WebAssembly decompilation and browser portability | |
07 | IoT firmware triage, SquashFS extraction & memory maps | |
08 | APK auditing, JNI native library tracing & SSL unpinning | |
09 | Windows | |
10 | 1-day patch diffing, memory corruption sinks & crash triage | |
11 | ASAR bundle extraction, contextBridge audit & AST dataflow | |
12 | Defensive analysis of DRM, licensing, and anti-cheat checks | |
13 | PCIe TLP sniffing, IOMMU protection & FPGA firmware | |
14 | Defeating packers, string decryption & custom cipher recovery | |
15 | Cross-architecture diffing (x86_64 vs ARM64) | |
16 | Replicating closed-source AI agent toolchains & MCP servers |
Output Standard: The Tri-Bucket Format
Every OmniREA report strictly separates findings into:
Confirmed Facts: Observed directly in decompiled AST, binary bytes, or headers (citing byte offsets or Evidence IDs).
Inferences: Hypotheses deduced from observed patterns or naming conventions.
Residual Unknowns: Unverified code paths, packed blobs, or remaining gaps.
Acknowledgments & Upstream Projects
OmniREA is built upon the pioneering work of four open-source projects. For detailed attributions, see ATTRIBUTIONS.md. All upstream licenses are respected under the MIT License:
morluto/rea (MIT License): Created the original 207-tool Reverse Engineering Anything MCP server and evidence bundle architecture.
Dryxio/reagent (MIT License): Developed the 11-signal parity framework, formal C/C++ reconstruction loop, and Unicorn differential CPU emulation.
JoasASantos/REA-Prompts (MIT License): Authored the original 16 REAP investigation prompt templates and the tri-bucket reporting standard.
aicodeking/leanrea (MIT License): Proved that fast-path zero-MCP CLI reconnaissance saves 38% wall time and 60% tokens on triage queries.
Contributing
Contributions, domain playbooks, and improvements are welcome! Please read our Contributing Guide and Code of Conduct before opening a pull request.
License
OmniREA is open-source software licensed under the MIT License. See ATTRIBUTIONS.md for third-party acknowledgments.
This server cannot be deployed
Maintenance
Related MCP Connectors
Autonomous agent guardrails, bash sandboxing, MCP rugpull diffing & prompt firewalls.
Self-hosted MCP server: 26 deterministic dev, security, and EVM tools.
23-in-1 MCP server: EVM tx simulator, funding rate arb, macro radar, swap calldata & security.
Read-only smart-contract security intelligence for autonomous agents.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceA headless Ghidra server that enables AI agents to perform deep reverse-engineering tasks such as disassembly, decompilation, and patching via the Model Context Protocol. It supports extensive automation of analysis workflows in sandboxed environments through a catalog of over 200 specialized tools.195GPL 2.0
- AlicenseAqualityAmaintenanceMCP server integrating Rizin reverse engineering, RzGhidra decompiler, and capa for binary analysis, enabling LLMs to open binaries, identify capabilities, extract function addresses, and decompile to C pseudocode.107MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to locally analyze and reverse engineer binaries through a compact 12-tool MCP interface for triage, function discovery, disassembly/decompilation, cross-references, strings/imports, call graphs, memory reads, annotations, and binary diffs.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to reverse-engineer binaries they own or are authorized to test, exposing static analysis through Ghidra or IDA (functions, strings, xrefs, decompilation, disassembly, raw bytes) plus controlled Windows Sandbox runs. Every recorded claim must cite quoted evidence and addresses, which a verifier checks, and unexamined areas are reported as unknown rather than clean.Apache 2.0