How tonchovet/rea-windows-github works
REA is a bridge for reverse-engineering tools: a user opens an existing binary in Hopper, Ghidra, or IDA, then an MCP lane lists it; the README also names the Morluto map. The available source excerpts contain only filenames, so implementation ownership and internal calls cannot be established. The graph therefore focuses on documented product relationships and leaves the map’s wiring unspecified.
Main entry points: native REA MCP bridge
Components 6
Connections 8
- Engineer → Hopper: opens binary
README.md - Engineer → Ghidra: opens binary
README.md - Engineer → IDA: opens binary
README.md - REA MCP bridge → Hopper: binds through MCP
README.md - REA MCP bridge → Ghidra: binds through MCP
README.md - REA MCP bridge → IDA: provides bridge
README.md - Hopper → REA MCP bridge: lists binary
README.md - Ghidra → REA MCP bridge: lists binary
README.md