Reverse Engineer Anything MCP server
Commit Nov 10, 2026Lets an AI agent decompile APKs, trace references, and inspect software binaries including Electron, .NET, Go, and Rust.
Also known as psyb0t/docker-reverse-engineer-anything, docker-reverse-engineer-anything
- Stars
- 7
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.1.2
- Last commit
- Nov 10, 2026
- License
- WTFPL
What is Reverse Engineer Anything MCP?
Reverse Engineer Anything lets an AI agent decompile APKs, trace references, and inspect software binaries including Electron, .NET, Go, and Rust.
Summary generated from the project's README
About Reverse Engineer Anything MCP server
Analyzing compiled software without source code is what this Docker-based MCP server enables for security researchers and developers. It provides an AI agent with 170 specialized tools to decompile Android APKs, inspect Electron bundles, and examine .NET, Go, Rust, and WASM binaries. By running inside a container, it offers a controlled environment for deep inspection of software components and device interaction via adb.
Users set up the server by running a Docker container with a bridge token for secure HTTP communication. The setup includes OpenJDK 21, Apktool 3.0.3, and jadx-headless-mcp, removing the need for manual installation of these dependencies. While APK analysis works immediately, users can opt-in to native decompilation by setting an environment variable to fetch Ghidra. The server supports both a streamable HTTP endpoint for remote clients and a stdio mode for local connections.
What you can do with it
- 1Decompile Android applicationsAn AI agent can decompile an APK to find where specific data is stored.
- 2Inspect compiled binariesDevelopers can use the agent to dig through Go, Rust, or .NET assemblies.
- 3Analyze Android device behaviorThe server allows an agent to interact with and poke at connected devices.
- 4Perform static code analysisThe toolset includes capabilities for analyzing JavaScript and Electron bundles.
Written from the project's README. Every use case is checked against a quote from it.
How to install Reverse Engineer Anything MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Reverse Engineer Anything MCP in Claude Code
$ claude mcp add --env 'REA_BRIDGE_TOKEN=<YOUR_REA_BRIDGE_TOKEN>' docker-reverse-engineer-anything -- docker run -i --rm docker.io/psyb0t/reverse-engineer-anything:v0.1.2Install Reverse Engineer Anything MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"docker-reverse-engineer-anything": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"docker.io/psyb0t/reverse-engineer-anything:v0.1.2"
],
"env": {
"REA_BRIDGE_TOKEN": "<YOUR_REA_BRIDGE_TOKEN>"
}
}
}
}Install Reverse Engineer Anything MCP in VS Code
.vscode/mcp.json
{
"servers": {
"docker-reverse-engineer-anything": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"docker.io/psyb0t/reverse-engineer-anything:v0.1.2"
],
"env": {
"REA_BRIDGE_TOKEN": "<YOUR_REA_BRIDGE_TOKEN>"
}
}
}
}Install Reverse Engineer Anything MCP in VS Code CLI
$ code --add-mcp '{"name":"docker-reverse-engineer-anything","type":"stdio","command":"docker","args":["run","-i","--rm","docker.io/psyb0t/reverse-engineer-anything:v0.1.2"],"env":{"REA_BRIDGE_TOKEN":"<YOUR_REA_BRIDGE_TOKEN>"}}'Install Reverse Engineer Anything MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"docker-reverse-engineer-anything": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"docker.io/psyb0t/reverse-engineer-anything:v0.1.2"
],
"env": {
"REA_BRIDGE_TOKEN": "<YOUR_REA_BRIDGE_TOKEN>"
}
}
}
}Install Reverse Engineer Anything MCP in Codex
$ codex mcp add docker-reverse-engineer-anything --env 'REA_BRIDGE_TOKEN=<YOUR_REA_BRIDGE_TOKEN>' -- docker run -i --rm docker.io/psyb0t/reverse-engineer-anything:v0.1.2Install Reverse Engineer Anything MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.docker-reverse-engineer-anything] command = "docker" args = ["run", "-i", "--rm", "docker.io/psyb0t/reverse-engineer-anything:v0.1.2"] [mcp_servers.docker-reverse-engineer-anything.env] REA_BRIDGE_TOKEN = "<YOUR_REA_BRIDGE_TOKEN>"
Install Reverse Engineer Anything MCP in Gemini CLI
$ gemini mcp add -s user -e 'REA_BRIDGE_TOKEN=<YOUR_REA_BRIDGE_TOKEN>' docker-reverse-engineer-anything docker -- run -i --rm docker.io/psyb0t/reverse-engineer-anything:v0.1.2Install Reverse Engineer Anything MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"docker-reverse-engineer-anything": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"docker.io/psyb0t/reverse-engineer-anything:v0.1.2"
],
"env": {
"REA_BRIDGE_TOKEN": "<YOUR_REA_BRIDGE_TOKEN>"
}
}
}
}Configuration
REA_BRIDGE_TOKENRequiredSecretBearer token clients must send; at least 32 characters
| Name | Description | |
|---|---|---|
| REA_BRIDGE_TOKEN | Bearer token clients must send; at least 32 characters | RequiredSecret |
Automated checks
Ran Nov 12, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablePass
- Open source license (OSI)WTFPL is not OSI-approvedFinding
- Commit or release in the last yearPass
- Package name not close to a popular packageNot checked
- Remote endpoint uses HTTPSNot checked
- Destructive tools are labelledNot checked
- No hidden instructions to the modelPass
- No critical advisory in the package or its dependenciesNot checked
README
View on GitHubreverse-engineer-anything
REA (Reverse Engineer Anything) in a Docker image, with everything it needs to tear apart Android APKs already inside, and a Streamable HTTP MCP endpoint in front of it.
REA is morluto's MCP server and CLI that lets an AI agent inspect software it has no source for: decompile APKs, trace references, read resources, poke at devices over adb, dig through Electron bundles, .NET assemblies, Go and Rust binaries. Upstream ships it as the rea-agents npm package that talks MCP over stdio and expects you to install a JDK, JADX and Apktool yourself. This image does that part for you.
This is an unofficial packaging. REA itself lives at morluto/rea and is MIT-licensed. Bugs in REA's tools go there; bugs in the image or the HTTP bridge go here.
Table of contents
- What's in the image
- Quick start
- Ways to run it
- Documentation
- Agent integrations
- Development
- Sponsor
- License
What's in the image
REA (rea-agents) 6.4.0 with its 170 MCP tools, a full OpenJDK 21, the exact jadx-headless-mcp jar REA pins, Apktool 3.0.3, adb and Node.js 24, for linux/amd64 and linux/arm64. APK analysis works out of the box, and so do REA's static JavaScript/Electron, .NET, Go, Rust, WASM, SQLite and capture tools.
Native decompilation needs Ghidra, which adds about 900 MB, so it is not baked in: set REA_INSTALL=ghidra and the container fetches it on first start, checked against a pinned SHA-256 (amd64 only). The image page has the versions and the update policy, and opt-in tools covers Ghidra, IDA and JEB.
Quick start
export REA_BRIDGE_TOKEN="$(openssl rand -hex 32)"
mkdir -p targets
cp /path/to/app.apk targets/
docker run -d --name rea \
-e REA_BRIDGE_TOKEN \
-p 127.0.0.1:8080:8080 \
--read-only \
--tmpfs /tmp:rw,nosuid,size=4g \
--tmpfs /home/rea:rw,nosuid,size=256m \
--cap-drop ALL \
--security-opt no-new-privileges \
-v "$PWD/targets:/work:ro" \
psyb0t/reverse-engineer-anything:latest
claude mcp add --transport http rea http://localhost:8080/mcp \
--header "Authorization: Bearer $REA_BRIDGE_TOKEN"
Then ask your agent something like "decompile the login flow in /work/app.apk and show me where the token gets stored". Paths are container paths: whatever you mount at /work is what REA sees.
REA can run, drive and instrument the software it looks at, and does no permission checks of its own. The container is the boundary, so keep every hardening flag above. Only analyze software you own or are authorized to examine. Security explains each flag and what to do before exposing the bridge beyond localhost.
Ways to run it
The entrypoint takes one argument:
| Command | What runs |
|---|---|
bridge |
Default. Streamable HTTP MCP on port 8080 at /mcp, bearer token required. |
mcp |
REA's own stdio MCP server, for docker run -i from a stdio-only client. |
| anything else | The REA CLI, e.g. --help or inspect-android-package /work/app.apk. |
The bridge gives each MCP session its own REA process and passes messages through untouched. Running the image has a full example for each mode.
Documentation
The full documentation lives at psyb0t.github.io/docker-reverse-engineer-anything.
| Section | What it covers |
|---|---|
| Running the image | HTTP bridge, stdio MCP and CLI, client setup, Android devices |
| What's in the image | Bundled versions, architectures, tags and the update policy |
| Opt-in tools | Ghidra on demand, and bringing your own Ghidra, IDA or JEB |
| Configuration | Every environment variable, default and valid range |
| HTTP bridge | Endpoints, sessions, status codes, limits and logs |
| Security | Hardening flags, what the bridge enforces, exposing it safely |
| Agent integrations | The skill and its CLI wrapper, the OpenClaw plugin, the MCP entry |
| Troubleshooting | Startup refusals, installer errors and HTTP errors, with fixes |
| Development | Layout, Make targets, dependencies, tests, CI and releases |
Agent integrations
- Skill for Claude Code, Codex and OpenClaw:
claude plugin install reverse-engineer-anything@psyb0t(afterclaude plugin marketplace add psyb0t/agents),codex plugin add reverse-engineer-anything@psyb0t, or from ClawHub. It teaches the agent the APK workflow and ships a locked-down CLI wrapper. - OpenClaw plugin
@psyb0t/reverse-engineer-anything: a stdio bridge to a running container. SetREA_URLandREA_BRIDGE_TOKEN. - MCP registry:
io.github.psyb0t/reverse-engineer-anything.
Details are on the agent integrations page.
Development
The host needs Docker, Make, Git and a shell. Everything else runs in containers.
make help # every target
make lint # tsc, eslint, prettier, shellcheck, hadolint
make test # bridge unit tests + the image against a real APK
make build # build psyb0t/reverse-engineer-anything locally
make run # run the bridge on 127.0.0.1:8080 (needs REA_BRIDGE_TOKEN)
make docs # build the documentation site into .testing/docs-site
make pkg-update PKG=rea-agents # move to the newest REA that clears the age gate
The development page covers the dependency rules, the tests and CI. Agents working on the code start at AGENTS.md.
Sponsor
License
WTFPL for this repository's code. REA is MIT, and the bundled tools keep their own licenses: see THIRD_PARTY_NOTICES.md.
Reverse Engineer Anything MCP questions
How do I add Reverse Engineer Anything MCP to Claude Code?
Run claude mcp add --env 'REA_BRIDGE_TOKEN=<YOUR_REA_BRIDGE_TOKEN>' docker-reverse-engineer-anything -- docker run -i --rm docker.io/psyb0t/reverse-engineer-anything:v0.1.2 in your terminal. Add --scope user to make it available in every project.
How do I add Reverse Engineer Anything MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What software can this server analyze?
The server can decompile APKs, dig through Electron bundles, .NET assemblies, Go and Rust binaries, and analyze WASM, SQLite, and JavaScript.
Does the Docker image include Ghidra?
No, Ghidra is not baked in to keep the image size smaller, but you can install it by setting the REA_INSTALL environment variable to ghidra.