Knowledge Base updated: 2026-11-19
REA knowledge base
REA is a TypeScript-based reverse-engineering assistant that exposes investigation capabilities through an MCP server and CLI. It coordinates analysis providers, external tools, native bridges, and retained evidence.
Its main capability areas are browser inspection, reverse-engineering toolchains, artifact and application reconstruction, firmware analysis, and reproducible analysis environments.
Critical investigation state is session-scoped in the server and provider layers; captured artifacts, environment bundles, and exported desktop captures preserve transferable evidence outside a live session.
flowchart TD
CLI[CLI]
MCP[MCP server]
Sessions[Session evidence]
Tools[Tool registration]
Browser[Browser analysis]
RE[RE toolchains]
Artifact[Artifact & app analysis]
Firmware[Firmware analysis]
Env[Analysis environments]
Native[Native runtime]
Bridges[Bridge implementations]
External[External tools and targets]
CLI --> MCP
MCP --> Sessions
MCP --> Tools
Tools --> Browser
Tools --> RE
Tools --> Artifact
Tools --> Firmware
Tools --> Env
Browser --> Native
RE --> Bridges
Artifact --> Native
Firmware --> Native
Native --> Bridges
Bridges --> External
flowchart LR
Request[MCP tool or CLI command] --> Session[Session / provider context]
Session --> Collect[Collect observations]
Collect --> Evidence[Retained evidence and results]
Evidence --> Output[Encoded tool or CLI output]
Glossary
- Evidence: Session-retained observations and derived results available to later operations.
- Provider: A capability-specific implementation that inspects a target or invokes an external integration.
- Bridge: A companion Python, Java, Swift, or other process used to cross runtime or product boundaries.
- Analysis environment: A bounded, exportable representation of target content and investigation state.
- Capture: Persisted browser, desktop, or artifact-derived material used for later investigation.
Invariants
- MCP operations are registered through shared server bindings rather than independently exposing arbitrary provider methods (src/…/serviceToolBindings.ts).
- Session-derived operations retain and encode evidence through server-side evidence handling (src/…/EvidenceMcpServer.ts).
- External reverse-engineering products are accessed through dedicated provider/client or bridge boundaries (src/…/GhidraProvider.ts, src/…/CutterBridgeClient.ts).
- Native binary formats are parsed through format-specific modules rather than a single generic parser (
src/native/elf/**,src/native/pe/**, src/…/**Macho*.ts). - CLI output passes through shared result-envelope and output-format handling (src/…/outputEnvelope.ts, src/…/cliResultOutput.ts).
Routing table
src/server/{createServer,EvidenceMcpServer,DeferredEvidenceMcpServer,serverInstructions,serviceToolBindings}.ts-> docs/mcp-server.md- src/…/tool*.ts -> docs/mcp-tool-registration.md
- src/…/*Evidence*.ts -> docs/session-evidence-and-results.md
src/server/http/**-> docs/server-lifecycle-and-policy.mdsrc/cli/{cliCommandRegistrations,commandManifests,options,help,interactiveSetup,cliJsonInput,cliResultOutput,outputEnvelope,outputFilter,toonOutput}.ts-> docs/command-line-interface.md- src/…/*browser*.ts -> docs/cli-browser-workflows.md
src/cli/{contractCommand,contractCliDescription,rustCommands,utilityCommands,adbCommands}.ts-> docs/cli-evidence-and-runtime-commands.mdsrc/browser/**-> docs/browser-analysis.mdsrc/browser/{WebBundleAnalysisWorker,WebBundleAnalysisWorkerServer,WebSourceMapFetcher,CdpBrowserProvider,CdpElectronProvider}.ts-> docs/browser-runtime-inspection.mdsrc/browser/history/**-> docs/browser-network-capture.mdsrc/{ghidra,ida,hopper,cutter,gdb,rizin,jeb}/**-> docs/reverse-engineering-toolchains.mdsrc/ghidra/**-> docs/ghidra-integration.mdsrc/{ida,hopper,cutter,gdb,rizin,jeb}/**-> docs/debugger-and-disassembler-integrations.mdsrc/application/{binaryDiagnostics,desktop,javascript}/**-> docs/artifact-and-application-analysis.mdsrc/application/binaryDiagnostics/**-> docs/binary-diagnostics-and-comparison.mdsrc/application/{managed,mobile,reconstruction}/**-> docs/application-reconstruction.mdsrc/application/javascript/**-> docs/javascript-and-desktop-reconstruction.mdsrc/firmware/**-> docs/firmware-and-embedded-analysis.mdsrc/application/desktop/**-> docs/desktop-application-environments.mdsrc/native/**-> docs/native-runtime-and-bridges.mdbridge/**-> docs/bridge-implementations.mdsrc/application/environment/**-> docs/analysis-environments.mdsrc/application/environment/{environmentBundle,environmentReplay,environmentServe}/**-> docs/environment-bundle-and-replay.mdsrc/client/**-> docs/client-configuration-and-setup.mdsrc/client/**/*Mcp*-> docs/mcp-client-registration.mdsrc/{firmware,cli}/**/*uefi*-> docs/uefi-firmware-inspection.md