Introducing a new way to review your PRs.

Read the announcement

morluto / rea

Reverse engineer anything with agents, from app behavior down to native binaries.

View on GitHub

27 documents · Updated Nov 20, 2026

overview

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

Routing table