Jukeyman Unleashed
Analyzes Android APKs, resources, and connected devices, providing manifest details, decompiled methods, package/process/log inspection, and screen captures.
Analyzes JavaScript and Electron applications, extracting modules, imports, source maps, routes, IPC, and native add-ons.
Analyzes Flutter apps, including Dart snapshot hashes, per-ABI library digests, and engine provenance.
Analyzes JavaScript applications statically, extracting modules, imports, source maps, routes, IPC, and native add-ons without requiring a native analysis engine.
Analyzes recorded Linux crashes and Linux targets, providing registers, signals, per-thread state, and mapping candidates.
Analyzes .NET assemblies, extracting metadata, CIL instructions, native dependencies, and enabling build comparisons.
Analyzes Rust binaries, extracting cargo-auditable crate names, versions, sources, and dependency edges.
Analyzes SQLite databases, extracting tables, columns, indexes, views, triggers, and selected rows.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Jukeyman Unleashed
The reverse-engineering vertical of the Jukeyman system.
Jukeyman is a super-intelligent, multi-vertical system. Each vertical owns a domain. This vertical owns reverse engineering — taking any software apart, down to the binary.
What this is
Jukeyman is a super-intelligent system built as a family of verticals — each one a deep, self-contained capability the system can call on. Jukeyman Unleashed is the reverse-engineering vertical: hand it a piece of software and it takes it apart, explains how it works, and proves every claim with evidence.
It is built on the complete upstream REA engine (morluto/rea), imported here in full,
wrapped in an RJ Business Solutions layer.
Related MCP server: REA
What it does
Point it at a target. It inspects and traces the code, returns findings with evidence (code, references, explicit unknowns — not guesses), and lets an agent ask follow-ups, explain behaviour, or rebuild the feature inside your own project.
Targets it can take apart
Target | What comes back |
Native binaries | Pseudocode, assembly, strings, symbols, calls, references |
Offline ELF layout | Sections, segments, original symbols/relocations, mitigation candidates |
Go binaries | Embedded compiler version, modules, replacements, build settings |
Rust binaries | cargo-auditable crate names, versions, sources, dependency edges |
WASM artifacts | Validation, sections, exact import/export WAT, decoded WAT |
EVM bytecode | Dispatch selectors, byte offsets, inferred arguments, mutability |
SQLite databases | Tables, columns, indexes, views, triggers, selected rows |
Recorded Linux crashes | Registers, signals, per-thread state, mapping candidates |
JavaScript / Electron apps | Modules, imports, source maps, routes, IPC, native add-ons |
Websites | Page structure, scripts, network observations, screenshots |
Saved network captures | Requests, responses, payloads, source locations |
.NET assemblies | Metadata, CIL instructions, native deps, build comparison |
Android APKs | Manifest, classes, decompiled methods, references |
Android devices | Devices, packages, processes, logs, dumps, screen captures |
JEB projects | Project units, artifact digests, pseudo-code |
Android resources | Decoded manifest, string tables, locales, version facts |
Flutter apps | Dart snapshot hashes, per-ABI library digests, engine provenance |
Firmware | Regions, extraction results, native-analysis handoffs |
Recorded packets | Fields, repeated values, filters, decode-as rules |
Packet summaries | Endpoints, DNS, TLS SNI, protocol distribution, HTTP requests |
Recorded logic signals | Decoder annotations, sample ranges, diagnostics |
Packages & resources | Inventories, digests, plists, Apple bundle anatomy |
Process behaviour | Terminal output, interactions, exit/filesystem observations |
Engines it drives
Hopper · Ghidra · IDA · Kuna decompiler · JADX (Android) · pwntools · WABT · Binwalk / Unblob · TShark · sigrok · adb · Apktool · objdump · Rizin · Frida (runtime verification) · JEB
How it works
An agent asks — over MCP, in plain language, about a local target.
This vertical inspects — it picks the right engine for the format and traces it.
Evidence comes back — code, references and explicit unknowns.
The agent acts — explains the behaviour, writes the feature, tests it.
Analysis runs locally; targets are not uploaded.
Quick start
npx rea-agents setup # registers the MCP server + agent workflow, then restart your agentAsk your agent:
"Understand how search works in , show me the evidence, and build it for my project."
From the terminal:
npx -y rea-agents@latest analyze-javascript-application /absolute/path/to/app --json
npm install --global rea-agents && rea --helpRequirements
Node.js 22.x (>=22.19), 24.x (>=24.11) or 26+, plus npm
A deep-analysis engine for native work: Hopper, Ghidra or IDA
Static JavaScript and .NET inspection need no native engine
Linux targets may need extras (procps
ps, pwntools, tshark…) — seedocs/
Repository map
src/ engine (TypeScript)
native/ native analysis bridge
bridge/ engine integration
third_party/ vendored tooling
website/ site + docs assets
docs/ complete upstream documentation
tests/ test lanes
.agents/ agent definitions AGENTS.md agent instructions
server.json MCP server manifest
UPSTREAM_README.md · LICENSE-UPSTREAM original project docs & licenseThe RJ Business Solutions layer (what we added)
Jukeyman vertical framing, branding and badges
Contribution, security and conduct policy
CI shell-lint workflow
install-tools.sh— optional external RE toolchain bootstrapUpstream docs preserved verbatim as
UPSTREAM_README.md
Built by
RJ Business Solutions — full-service technology firm for municipalities, public agencies and enterprises.
Founder & Chief Technology Architect: Rick Jefferson
https://rjbusinesssolutions.org/ · support@rjbusinesssolutions.org
SAM.gov Active · UEI XJNPP1GSNN54 · CAGE 9TR81 · 1342 NM 333 # 5254, Tijeras, NM 87059
Upstream & license
Built on REA — https://github.com/morluto/rea · https://rea.tools (MIT © morluto). This vertical: MIT © RJ Business Solutions. See LICENSE and LICENSE-UPSTREAM. Commercial engines (IDA/Hex-Rays, Hopper, JEB) require their own licenses.
This server cannot be deployed
Maintenance
Related MCP Connectors
Self-hosted MCP server: 26 deterministic dev, security, and EVM tools.
Remote MCP for Android CLI agent build gate, structured receipts, audit logs, and reviewer-ready evi
AI supply-chain BOM: agents, MCP servers, packages and recorded reach. Scan and investigate via MCP.
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables agents to inspect and reverse engineer native binaries, JavaScript/Electron applications, .NET assemblies, websites, and runtime behavior, returning evidence-backed findings that can be explained, implemented, or tested.519,887 npm3MIT
- AlicenseNot gradedqualityBmaintenanceEnables 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.519,887 npmMIT
- AlicenseNot gradedqualityAmaintenanceServes 170 reverse-engineering tools over a local stdio MCP process, letting an agent drive disassembly, decompilation, and dynamic analysis through the engines already installed on the user's machine (Ghidra, Hopper, IDA, JEB, JADX, adb, mitmproxy, Chrome). Binaries never leave the host, and every finding comes back with an evidence contract covering evidence ids, capture tool, coverage, and explicit unknowns.MIT
- AlicenseNot gradedqualityAmaintenanceEnables agents to reverse engineer native binaries, JavaScript/Electron applications, .NET assemblies, web captures, EVM bytecode, and process behavior through a provider-neutral MCP interface. Every result is an evidence envelope stating what was observed, derived, unexamined, or unprovable, with all capabilities gated by a deterministic fail-closed policy engine.Apache 2.0