Search for:
Information about ReA
Why this server?
Exact name match for 'ReA'. Connects agents to reverse-engineering tools for native binaries, JavaScript/Electron, .NET and runtime behavior, returning pseudocode, references and evidence.
AlicenseNot gradedqualityBmaintenanceConnects AI agents to reverse-engineering tools that inspect native binaries, JavaScript/Electron apps, .NET assemblies, websites, and runtime behavior without source code. Returns pseudocode, references, and evidence so agents can explain how a feature works or reimplement it.377,174 npm7MITWhy this server?
Another exact 'REA' server — reverse engineering across native binaries, managed code, Electron apps, websites and live runtime, with a durable workspace and evidence-linked findings.
AlicenseNot gradedqualityCmaintenanceEnables agents to reverse-engineer software across native binaries, managed code, Electron apps, websites, and live runtime behavior, returning findings linked to the evidence and limitations behind each conclusion. It also maintains a durable workspace where those behaviors can be inspected, questioned, compared against real execution, and exported as runnable handoffs.MITWhy this server?
Exposes every command of the rea-agents CLI as schema-driven MCP tools for reverse engineering binaries, JS/Electron, .NET, WASM, EVM, SQLite and Android artifacts.
AlicenseNot gradedqualityCmaintenanceExposes every command of the rea-agents CLI as dynamically generated, schema-driven MCP tools, letting clients reverse engineer binaries, JavaScript/Electron apps, .NET, WASM, EVM, SQLite and Android artifacts through natural language. Tool names and JSON Schemas are derived automatically from the CLI, so new rea releases add capabilities without code changes.MITWhy this server?
Lightweight front-end to a persistent REA server: four flat tools to search, describe and invoke 139 reverse-engineering capabilities, read-only by default.
AlicenseAqualityCmaintenancePublishes four flat, schema-light tools that let AI agents (including strict providers) search, describe, and invoke any of 139 reverse-engineering capabilities behind a persistent REA server. Enables file fingerprinting, inspection, and evidence-linked investigation of shipped software through plain-English requests, read-only by default.42MITWhy this server?
Governance proxy explicitly built between an AI agent and REA, enforcing authorization, risk tiers and a hash-chained audit log over 207 REA analysis tools.
AlicenseNot gradedqualityBmaintenanceActs as a governance proxy between an AI agent and REA, enabling authorized reverse engineering of binaries, apps, websites and firmware only after a person declares ownership or written permission for a scoped, expiring target. Enforces risk tiers on all 207 analysis tools, denies unlisted tools, blocks code-executing tools, and records every decision in a hash-chained audit log.MITWhy this server?
Performs bounded inspection of protected artifacts (JS, ASAR, native binaries, WASM, SQLite, models) with optional handoff of verified inspection views to REA.
AlicenseNot gradedqualityCmaintenanceEnables bounded, evidence-backed inspection of BLA-protected artifacts such as JavaScript, ASAR, native binaries, WASM, SQLite, and models, with optional handoff of verified inspection views to REA.552 npm36MITWhy this server?
Included in case 'ReA' is shorthand for REAPER: provides OSC/ReaScript control of the REAPER DAW for composition, MIDI, tracks and transport.
FlicenseBqualityDmaintenanceEnables AI-powered music composition and control for REAPER DAW through OSC and ReaScript integration. Supports transport control, MIDI generation, track management, and music theory operations like scales, chords, and rhythm patterns.17-Why this server?
REAPER-related alternative — parses .rpp project files and generates Lua ReaScripts, relevant if the query meant ReaScript/REAPER rather than REA.
FlicenseNot gradedqualityDmaintenanceEnables AI agents to control Reaper DAW by parsing .rpp project files and generating Lua ReaScripts for project-level tasks.-