| Compare approaches | Mechanism | When to choose it |
|---|---|---|
| REA | An open-source MCP server: your agent calls REA to inspect a local target (native binaries, JavaScript and Electron apps, .NET, websites and more) and gets findings with their evidence. | Choose REA when you want your agent to investigate software you own or may examine and explain it with evidence. |
| Binary Ninja MCP | A Binary Ninja plugin with an MCP server and a bridge (GPL-3.0) that exposes Binary Ninja's analysis to MCP clients in real time. It needs Binary Ninja and Python 3.12+, installs through Binary Ninja's Plugin Manager, can configure several MCP clients automatically and can switch between several open binaries. | Choose it when you work in Binary Ninja and want your agent in that session. REA's README lists Hopper, Ghidra and IDA as its native engines, not Binary Ninja. |
Practical setup notes for running REA on Fedora-based Linux, with the problems hit along the way and a queue of tests.
How to run REA with local models on a single 12 GB GPU, and how five models compared.
A show-and-tell thread on keeping token use down in REA workflows and what other people are using.
Often yes, but check each tool's documentation for supported targets and setup, and analyse only software you own or are authorised to examine.