{"id":"a1cf1053-0d3d-444a-a496-a89cdc4235f0","slug":"reareverse","kind":"mcp","name":"ReaReverse","summary":"Reverse engineer anything with agents, from app behavior down to native binaries.","owner":"Prompt-Motion","repoUrl":"https://github.com/Prompt-Motion/ReaReverse","license":"MIT","licenseTier":"permissive","trust":"community","stars":3,"match":null,"fewStars":true,"format":"mcp","createdAt":"2026-10-15T03:51:24.000Z","addedAt":"2026-10-21T06:56:02.882Z","logoUrl":"https://avatars.githubusercontent.com/u/338969877?u=4592a804ca59c94fed232ee9bd2b9ec1bfc51827&v=4","linkOnly":false,"collection":null,"skillPath":null,"categories":["developer-tools","memory-knowledge"],"tags":["ai-agents","binary-analysis","claude-code","cli","codex","cordis","decompiler","developer-tools"],"runtime":"node","local":true,"cloudCapable":false,"cloudCapability":"unknown","cloudReadyOnPlatform":false,"needsApiKey":false,"reviewed":false,"syncedAt":"2026-10-26T13:56:15.881Z","sample":false,"url":"https://conduits.dev/tools/reareverse","language":"TypeScript","transports":["stdio"],"install":{"npm":"rea-agents"},"requirements":{"env":[],"upstreamMayCharge":false},"tools":null,"readme":"
\n\n**English** · [简体中文](docs/readme/README_zh.md) · [繁體中文](docs/readme/README_zh-TW.md) · [日本語](docs/readme/README_ja.md) · [한국어](docs/readme/README_ko.md) · [Türkçe](docs/readme/README_tr.md) · [Русский](docs/readme/README_ru.md) · [Tiếng Việt](docs/readme/README_vi.md) · [ไทย](docs/readme/README_th.md) · [Deutsch](docs/readme/README_de.md) · [Español](docs/readme/README_es.md) · [Français](docs/readme/README_fr.md) · [Українська](docs/readme/README_uk.md) · [Polski](docs/readme/README_pl.md) · [Português (Brasil)](docs/readme/README_pt-BR.md) · [العربية](docs/readme/README_ar.md) · [فارسی](docs/readme/README_fa.md) · [Bahasa Indonesia](docs/readme/README_id.md) · [Italiano](docs/readme/README_it.md)\n· [Ελληνικά](docs/readme/README_el.md)\n\n# REA: Reverse Engineer Anything\n\n### One MCP for reverse engineering across binaries, applications, and runtime behavior.\n\n**See a feature you like. Understand how it works, down to the binary level.**\n\n[![npm version](https://img.shields.io/npm/v/rea-agents?style=flat-square&color=cb3837)](https://www.npmjs.com/package/rea-agents)\n[![MCP tool catalog](https://img.shields.io/badge/MCP-tool_catalog-5c4ee5?style=flat-square)](docs/mcp-contracts.md#generated-catalog)\n[![Node.js requirements](https://img.shields.io/badge/Node.js-requirements-339933?style=flat-square&logo=nodedotjs&logoColor=white)](#what-you-can-analyze)\n[![skills.sh](https://skills.sh/b/morluto/rea?style=flat-square)](https://skills.sh/morluto/rea/reverse-engineer-anything)\n[![MIT license](https://img.shields.io/badge/license-MIT-f4c430?style=flat-square)](LICENSE)\n[![Discord](https://img.shields.io/discord/1556595354999332884?logo=discord&logoColor=white&label=Discord&color=5865F2)](https://discord.gg/GkcryMnJDM)\n\n\"morluto%2Frea\n\n**[Website](https://reareverse.com/) · [Guides](https://reareverse.com/guides/) · [Showcases](https://reareverse.com/showcase/)**\n\n[Quick start](#quick-start) · [How REA works](#how-rea-works) · [What you can analyze](#what-you-can-analyze) · [Showcases](#showcases) · [FAQ](#faq) · [Documentation](#documentation)\n\nnpx rea-agents setup\n\n
\n\n> [!IMPORTANT]\n> Get REA from [morluto/rea](https://github.com/morluto/rea),\n> [reareverse.com](https://reareverse.com/), or the [rea-agents npm package](https://www.npmjs.com/package/rea-agents).\n> Follow the installation and release links from these official sources. A similar\n> repository name or copied README does not establish that a download is official.\n\n
\n\n
\n\n\"REA\n\n

\n\n\n\n\n\n
\n \n \"Discord\"
\n Join the Reverse Engineering Community\n
\n Discord · Q&A · Show and Tell\n
\n\n
\n\n
\n\n---\n\nSee a feature in an app that 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.\n\nREA connects your agent to tools for inspecting native binaries, JavaScript and Electron apps, .NET assemblies, and websites. You can also use the same tools from your terminal. Analysis runs locally, and results include the evidence and limitations behind each conclusion.\n\nSetup registers REA with your agent and installs matching workflow instructions. Native analysis can use an existing Hopper, Ghidra, or IDA installation; setup can optionally install Hopper with approval. Static JavaScript analysis needs no native analysis engine.\n\n> **[Visit the REA website](https://reareverse.com/)** for setup instructions, illustrated guides, and real case studies.\n\n## Quick start\n\nOn Linux, Ghidra, JADX, firmware tool launches and static JavaScript/Electron\nanalysis require a procps-compatible `ps` on REA's `PATH` for process ownership\nchecks. Recovery steps are in `docs/installation.md` under\n\"Linux owned-process prerequisite\".\n\n### Set up your agent\n\nWith Node.js and npm installed, run:\n\n```bash\nnpx rea-agents setup\n```\n\nChoose your agents, review the proposed changes, and approve them. Setup adds\nREA's MCP server and matching workflow instructions, with backups of existing\nconfiguration. Restart your agent afterward.\n\nSetup supports Claude Code, Codex, Cursor, Gemini CLI, Grok Build and\n[other agents](docs/installation.md#supported-agents). See\n[installation and setup](docs/installation.md) for provider configuration and\nmanual MCP registration.\n\n### Ask your agent\n\n```text\nUnderstand how search works in the Notes app, show me the evidence, and build a\nsimilar feature for my project.\n```\n\nReplace Notes with your target app and the feature you want to understand.\n\n### Use the terminal\n\nInspect an extracted JavaScript/Electron app directory or ASAR:\n\n```bash\nnpx -y rea-agents@latest analyze-javascript-application /absolute/path/to/app --json\n```\n\nThe result includes modules, imports, Electron boundaries and their evidence.\nReplace the path with your target, such as `\"D:/apps/example\"` on Windows.\n\nTo install the `rea` command for regular use:\n\n```bash\nnpm install --global rea-agents\nrea --help\n```\n\nFor native analysis, configure a provider first. See the\n[CLI and Evidence guide](docs/cli.md) for native commands, provider selection,\nsnapshots and scripting.\n\n### Update REA\n\nREA changes quickly, and new releases include frequent bug fixes. Keep your\ninstallation up to date.\n\nFor a CLI installed with `npm install --global` or `bun add --global`:\n\n```bash\nrea update\n```\n\nBun global updates require Bun 1.2.17 or later. With an older Bun release,\nupgrade Bun manually before running `rea update`.\n\nTo refresh your agent registrations and skill, run the setup command printed\nby the update.\n\nIf you use `npx`, update your agent setup with:\n\n```bash\nnpx rea-agents@latest setup\n```\n\nReview the setup changes and restart your agent. For one-off CLI commands,\nuse `npx rea-agents@latest` followed by the command. With Bun, use\n`bunx rea-agents@latest` in place of `npx rea-agents@latest`.\n\n## How REA works\n\nYour agent calls REA through MCP to inspect the target and trace relevant code.\nREA returns findings with their evidence. The agent uses them to ask follow-up\nquestions, explain the behavior, or write and test an implementation.\nCLI commands use the same workflows.\n\n![REA investigation flow: your agent asks about a local target, REA inspects and traces it using analysis tools, and the agent uses the returned code, references and unknowns to explain, implement and test.](website/public/assets/figures/rea-investigation-flow.svg)\n\n[Open the full-size figure](website/public/assets/figures/rea-investigation-flow.svg).\n\n\n\n## What you can analyze\n\nREA requires Node.js 22.x (>=22.19), 24.x (>=24.11), or 26+, plus npm.\nAdditional tools and host support depend on the target:\n\n| Target | What REA returns | Requirements and guide |\n| ---------------------- | ------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------- |\n| Native binaries | Pseudocode, assembly, strings, symbols, calls and references | Hopper, Ghidra or IDA; [native analysis](docs/native-investigation.md) |\n| Offline ELF layout | Sections, segments, original symbols/relocations and static mitigation candidates | Caller-supplied pwntools on Linux x64; [binary diagnostics](docs/binary-diagnostics.md) |\n| Go binaries | Embedded compiler version, modules, replacements and build settings | Built-in static ELF/PE/thin Mach-O inspection; no Go installation required |\n| Rust binaries | Embedded cargo-auditable crate names, versions, sources and dependency edges | Built-in static ELF/PE/thin Mach-O inspection; [Rust binaries](docs/rust-binaries.md) |\n| WASM artifact | Validation, sections, exact import/export WAT forms and decoded WAT | Caller-supplied WABT 1.0.42; `inspect_wasm_artifact` |\n| EVM bytecode | Dispatch selectors, byte offsets, inferred arguments and mutability | Local raw/hex carrier on Linux x64; [offline EVM guide](docs/evm-bytecode.md) |\n| SQLite databases | Tables, columns, indexes, views, triggers and selected ordinary-table rows | Local database/WAL snapshot; Node.js 24.x >=24.15 or 26+ with native SQLite limits |\n| Recorded Linux crashes | Raw notes, every recorded thread's registers/signals and optional mapping candidates | Caller-supplied pwntools on Linux x64; optional GDB/pwndbg; [recorded crashes](docs/recorded-crashes.md) |\n| JavaScript / Electron | Modules, imports, source maps, routes, IPC and native add-on relationships | Node.js and npm; Linux: procps-compatible `ps`; [application analysis](docs/javascript-application-workflows.md) |\n| Websites | Page structure, scripts, network observations and requested screenshots | A Chrome-family browser; [browser analysis](docs/browser-observation.md) |\n| Saved network captures | Requests, responses, exposed payloads and source locations | HAR or Fiddler Everywhere SAZ; mitmdump on Linux for native mitmproxy; [capture guide](docs/web-network-captures.md) |\n| .NET assemblies | Metadata, CIL instructions, declared native dependencies and build comparisons | None (static only); [managed-code guide](docs/managed-code-analysis.md) |\n| Android APKs | Manifest declarations, classes, decompiled methods and references | Headless JADX and a full JDK on Linux/macOS/Windows x64; [Android guide](docs/android-analysis.md) |\n| Android devices | Devices, packages, processes, logs, dumps, screen captures, and APK/file transfers | Caller-supplied adb (emulator or hardware); [ADB guide](docs/adb-device-analysis.md) |\n| JEB projects | Engine-backed project units, artifact digests and type/method pseudo-code | A caller-started JEB client serving MCP, selected with REA_JEB_MCP_URL; [JEB guide](docs/jeb-analysis.md) |\n| Android resources | Decoded manifest, string tables, locales and version facts | Caller-supplied Apktool launcher; [resource guide](docs/apktool-resource-analysis.md) |\n| Flutter apps | Dart snapshot hash, per-ABI library digests and engine build provenance | None (static APK parsing); [Flutter guide](docs/flutter-analysis.md) |\n| Firmware | Regions, extraction results and native-analysis handoffs | Binwalk / Unblob on Linux; [firmware guide](docs/firmware-analysis.md) |\n| Recorded packets | Selected fields, repeated values, filters and decode-as rules | Linux: TShark 4.x + prlimit; [capture guide](docs/packet-captures.md) |\n| Packet summaries | Endpoints, DNS, TLS SNI, protocol distribution and HTTP requests | Caller-supplied tshark and capinfos (Linux-verified); [pcap guide](docs/pcap-analysis.md) |\n| Recorded logic signals | Decoder annotations, sample ranges and diagnostics | Linux: sigrok-cli 0.7.2 + prlimit; [signal recordings](docs/signal-recordings.md) |\n| Packages and resources | File inventories, digests, plists, Apple bundle anatomy and extracted resources | [Artifact and JavaScript guide](docs/javascript-artifact-reconstruction.md), [Apple applications](docs/apple-application-analysis.md) |\n| Process behavior | Terminal output, interactions, exit and filesystem observations, and run comparisons | Linux/macOS with a native PTY; [process capture](docs/process-capture.md) |\n\nStatic JavaScript and .NET inspection read the supplied files without running\nthe application. Runtime capture runs or interacts with the selected target\nusing your user permissions; each runtime guide describes its effects.\n\nFor offline native-binary inspection, REA also supports caller-supplied GNU\nobjdump and Rizin. See the [reverse-engineering tools guide](docs/reverse-engineering-tools.md)\nfor provider setup, CLI commands, and Evidence limitations. REA does not install\nor update either provider.\n\n\n\nNative formats and host support vary by provider. See\n[Hopper and Ghidra setup](docs/installation.md#hopper), the\n[IDA guide](docs/ida-provider.md) (including an optional native MCP bridge), and\n[experimental Windows Ghidra support](docs/windows-ghidra-p0.md).\nGhidra also supports [16-bit DOS analysis](docs/ghidra-dos.md).\nFor large binaries, raise the provider's startup deadline with\n`REA_GHIDRA_STARTUP_TIMEOUT_MS` or `REA_HOPPER_STARTUP_TIMEOUT_MS`.\nFor provider selection, see the [CLI guide](docs/cli.md#choose-a-provider).\nCheck [release availability](docs/installation.md#released-package-and-main)\nfor features added since the latest npm release.\n\n## Showcases\n\n[![Illustrations of the DX-Ball sound-pan, Notion clipboard-bridge, and TH04 bullet-ring showcases](docs/assets/rea-showcases.png)](https://reareverse.com/showcase/)\n\n### DX-Ball: reconstruct a sound-pan calculation\n\nFollow a sound call into its position-to-pan helper, inspect the instructions,\nand turn incomplete pseudocode into C. The reconstruction passes 3,205\noriginal-x86 cases and reproduces all 63 compiled function bytes.\n\n[Read the case study](https://reareverse.com/showcase/dx-ball/) ·\n[Reconstruction repository](https://github.com/N0zoM1z0/dx-ball)\n\n### Notion: trace the Electron clipboard bridge\n\nFind the renderer's clipboard API, follow it through preload and IPC into the\nmain process, and inspect the rich clipboard format.\n\n[Read the case study](https://reareverse.com/showcase/notion/)\n\n### TH04: recover a DOS bullet-ring calculation\n\nInspect the original PC-98 game's 16-bit instructions, recover the fixed and\naimed angle calculations, and compare the reconstructed C++ with the\nhistorical compiler output.\n\n[Read the case study](https://reareverse.com/showcase/th04/) ·\n[Reconstruction repository](https://github.com/N0zoM1z0/th04)\n\nIf you've used REA on something interesting, we'd love to see it. Share your\ncase in an [issue](https://github.com/morluto/rea/issues) or a\n[pull request](https://github.com/morluto/rea/pulls), including the target,\nyour question, how REA helped, and what you found.\n\n## FAQ\n\n
\nWhich agents can use REA?\n\nAny agent that supports local MCP servers. Setup configures the\n[supported agents](docs/installation.md#supported-agents); other clients can use\n[manual MCP registration](docs/installation.md#mcp-registry).\n\n
\n\n
\nDo I need Hopper, Ghidra or IDA?\n\nDeep native analysis uses one of them. Static JavaScript and .NET inspection\nwork without a native analysis engine. Setup can install Hopper after approval;\nGhidra and IDA use your existing installations. See [provider setup](docs/installation.md#hopper).\n\n
\n\n
\nDo I need to start Hopper first?\n\nREA starts Hopper when an operation needs it. On macOS, a first-run dialog may\nask you to choose demo mode or activate your license. Complete that prompt in the\nsame user session before your first CLI/MCP operation or unattended job. Open\nHopper manually if needed. See\n[Hopper startup and troubleshooting](docs/installation.md#launcher-paths-and-troubleshooting).\n\n
\n\n
\nWhat does installing the skill from skills.sh do?\n\nThe skill supplies investigation instructions for your agent. Use `npx rea-agents setup`\nto register REA's MCP server and install the matching instructions, then restart\nyour agent. See [skill-only installation](docs/installation.md#skill-only-installation).\n\n
\n\n
\nWhat code does REA return?\n\nNative analysis returns pseudocode and assembly. JavaScript/Electron analysis\nrecovers modules and their relationships. Your agent uses these findings to\nwrite and test an implementation; the [showcases](#showcases) give worked examples.\n\n
\n\n
\nDoes REA upload my app?\n\nREA analyzes targets locally. Your agent receives the tool results, and its\nmodel provider has its own data policy.\n\n
\n\n
\nWhat should I do if I hit a bug?\n\nUpdate first; a recent release may already fix it.\n\nFor a CLI installed with `npm install --global` or `bun add --global`:\n\n```bash\nrea update\n```\n\nFor agent setup through `npx`:\n\n```bash\nnpx rea-agents@latest setup\n```\n\nIf you're using an agent, complete the [setup refresh](#update-rea) and restart\nit. Retry the same task. If the problem persists, [open an issue](https://github.com/morluto/rea/issues)\nwith your REA version, target type, steps to reproduce and error output.\n\n
\n\n## Documentation\n\nStart with the website's [worked guides](https://reareverse.com/guides/).\nFor exact options, prerequisites and result contracts:\n\n- [Installation and setup](docs/installation.md): agent registration, provider configuration, updates and uninstall.\n- [Readiness and troubleshooting](docs/installation.md#check-readiness-for-your-task): diagnose one agent or analysis engine.\n- [CLI and Evidence](docs/cli.md): commands, provider selection, snapshots, import/export and exit statuses.\n- [MCP contracts](docs/mcp-contracts.md) and [agent prompts](docs/mcp-prompts.md): tool results, sessions and guided investigations.\n- [Tool catalog](docs/mcp-contracts.md#generated-catalog): generated inventory of tools, providers and CLI commands.\n- [Roadmap](docs/roadmap.md): planned work and capability trackers.\n\nReport vulnerabilities through [SECURITY.md](SECURITY.md).\n\n## Star history\n\n🎉 **200,000 GitHub stars — thank you!**\n\nThanks to everyone using REA, reporting bugs, requesting features, testing builds, and contributing fixes.\n\n\n \n \n \n \"REA\n \n\n\n## Disclaimer\n\nSee [DISCLAIMER.md](DISCLAIMER.md) for responsible-use guidance.\n\nThe project's position on illegal or unauthorized use covers all REA versions,\ndistribution channels, and platforms; each copy retains its applicable licenses.\n\nREA is for lawful research, education, interoperability, software preservation,\nand analysis of software you own or are authorized to examine.\n\n## Contributing\n\nWe'd love your help with REA! [Open an issue](https://github.com/morluto/rea/issues) to\nreport a bug or suggest a feature, or [send a pull request](https://github.com/morluto/rea/pulls)\nto improve the code or docs.\n\nSee [CONTRIBUTING.md](CONTRIBUTING.md) for development setup and checks,\n[testing](docs/testing.md) for verification lanes, and the\n[architecture map](docs/architecture.mermaid) for the project structure.\n\n## License\n\n[MIT](LICENSE)\n\nREA-authored code is licensed under MIT. Third-party material retains its own\nlicenses and copyright notices; see\n[Third-party notices](THIRD_PARTY_NOTICES.md) for the dependency inventory,\npreserved license texts, and external-tool terms.\n\n**You must legally obtain and be authorized to use commercial tools**, including\nIDA Pro / Hex-Rays decompilers, Hopper, and JEB, under their applicable\nlicenses. REA grants no tool license, key, or activation entitlement. Trials and\ndemos remain subject to vendor terms, including user, feature, automation, and\noutput sharing restrictions. Cracked copies, stolen keys, unauthorized key\nsharing, and bypassing license restrictions are not authorized. This guidance\ndoes not amend MIT or third-party licenses.\n"}