Run Reverse Engineer Anything (REA) with an uncensored model

REA (Reverse Engineer Anything) is the viral MCP toolkit that lets a coding agent inspect binaries, JavaScript and Electron apps, .NET assemblies and websites, then rebuild a feature in your own project. The catch people keep hitting: Claude refuses it. A whole r/ClaudeCode thread is about Opus and Sonnet declining crash-dump and binary analysis. The fix is to run REA on a model that won’t refuse authorized work. Obscurify.ai gives you one, with an account that’s a 16-digit number instead of an email.

Authorized work only. REA itself is “for lawful research, education, interoperability, software preservation, and analysis of software you own or are authorized to examine.” Obscurify.ai’s terms agree: no breaking into systems you aren’t authorized to access, no writing or spreading malware.

Tested backbone: on 2026-11-08, OpenCode running the pqhaz/deepseek-v4.1-flash-1017-heretic model through Obscurify.ai reverse engineered a crackme we compiled ourselves — it read the binary with objdump, recovered the hardcoded password, and ran it to confirm. That is the exact agent-plus-model pairing REA drives. REA’s own setup below is verified against its README on 2026-11-08.

Before you start

  • Node.js 22.23.4+/24.22.1+/26.12.1+ and npm. REA runs locally.
  • A coding agent that supports local MCP servers. REA’s setup configures Claude Code, Codex, Cursor, Gemini CLI and others; any MCP-capable agent such as Cline or OpenCode can use it through manual MCP registration. Point that agent at Obscurify.ai (see those tutorials) so the model never refuses.
  • For deep native decompilation, REA uses an existing Ghidra, IDA, Hopper or Kuna. Static JavaScript, .NET, Go, Rust and many other formats need no native engine.
  • An Obscurify.ai API key. Create an account — a 16-digit number, no email. Add credit, then Show API Key. New accounts may get $1 of starter credit while this month’s promo budget lasts.

Set up REA

From a trusted directory (not inside the target project):

npx rea-agents setup

Choose your agents, review the changes, approve, and restart the agent. Setup registers REA’s MCP server and its workflow instructions. To use REA from the terminal instead, npm install --global rea-agents and run rea --help.

Run REA on an Obscurify.ai model

The piece REA doesn’t provide is a model that will actually do the analysis. Run your MCP-capable agent on an Obscurify.ai model with tool support. From /v1/models:

  • Uncensored, needs the Pro plan: deepseek/deepseek-v4.1-flash-uncensored or z-ai/glm-5.3-flash-uncensored.
  • Decensored / cybersecurity, any funded account: pqhaz/deepseek-v4.1-flash-1017-heretic (tested above), orca/orcacyber-minimax-m3.1-flash, heabsy/cyberheabsy.

Then ask the agent, replacing the target with your own authorized one:

Use REA to understand how search works in this app I own, show me the evidence,
and build a similar feature for my project.

The agent calls REA’s tools to inspect the target and reasons over the findings with your Obscurify.ai model — no refusal.

If something fails

  • Claude still refuses: that’s the model, not REA. Switch the agent to an Obscurify.ai uncensored or cybersecurity model as above.
  • 402 / 403: no balance, or the model isn’t on your plan (uncensored needs Pro).
  • “provider unavailable” on a native binary: REA needs Ghidra/IDA/Hopper/Kuna configured for deep decompilation; set GHIDRA_INSTALL_DIR or install Hopper.
  • 404 model_not_found: check the id against /v1/models and keep its prefix.

What stays private

REA analyzes targets on your machine. Your agent sends findings to the model; Obscurify.ai doesn’t store prompts or responses, and models with the ZDR tag run only on zero-data-retention routes. Providers see the prompt text but not who sent it. See the privacy policy.

More: Obscurify.ai for agents.