dsh-rea
Registers the upstream REA (Reverse Engineer Anything) MCP server into DeepSeek Harness as mcp__rea__* tools — a third-party adapter, analysis is upstream's. · 把上游 REA 的 MCP 服务接入 DeepSeek Harness,提供 mcp__rea__* 工具(第三方适配,分析能力属上游)。
What it is
Registers the upstream REA (Reverse Engineer Anything) MCP server into DeepSeek Harness as mcp__rea__* tools — a third-party adapter, analysis is upstream's. · 把上游 REA 的 MCP 服务接入 DeepSeek Harness,提供 mcp__rea__* 工具(第三方适配,分析能力属上游)。
How to install
Run this in the DSH web profile, then refresh the page.
$ dsh plugin --profile web add dsh-rea@1.2.0
DSH versions accepted
>=0.2.0-rc.0 <0.3.0
Author and traction
dushudou · ★ 9 · Updated 2026-10-16
About this plugin
dsh-rea
English · [简体中文](README.zh-CN.md)
Brings the upstream [REA — Reverse Engineer Anything](https://github.com/morluto/rea) MCP server into
DeepSeek Harness (dsh), so its tools show up in a session as mcp__rea__*.
What this is
A small DSH bundle. Its one row, rea, mounts the official MCP client plugin
(@deepseek-ai/dsh-mcp-client) for the rea --mcp stdio server already installed on your machine, and adds
a page to the Plugins sidebar with a setup check, example prompts, and settings. There is no analysis
code here.
> Third-party adapter. This repository is not part of REA, ships none of REA's code, and is not
> maintained by REA's authors. It connects REA and adds a setup page.
> Upstream: [github.com/morluto/rea](https://github.com/morluto/rea) (MIT) ·
> [docs](https://github.com/morluto/rea#what-you-can-analyze) ·
> [中文文档](https://github.com/morluto/rea/blob/main/README_zh.md#可以分析什么) ·
> [rea.tools](https://rea.tools/) · npm package rea-agents.
> REA's own problems go to its tracker; this plugin's problems go to
> [this repository's issues](https://github.com/dushudou/dsh-rea/issues).
It adds: the mcp__rea__* tool registration with cross-platform auto-detection of the command form,
and a Plugins-page guide that tells you what is missing and how to fix it.
What it can and cannot do
The analysis is upstream's; this section only restates upstream's own contract so expectations are right.
- It cannot recover complete source code. For native binaries upstream returns *pseudocode and
assembly, for Android APKs decompiled methods, for JEB units pseudocode*, and for JavaScript/Electron
modules and their relations. Upstream's tool contract states the pseudocode "is decompiler output, not
original source and not text-equivalent" to another provider's output.
- Not recoverable in practice: original identifier names, types, comments, macros and template expansion,
build scripts and assets. Optimisation (inlining, reordering), symbol stripping, obfuscation, packing and
VM protection only make the output worse.
- Every result carries confidence and limitations (
observed/derived/inferred, plus an explicit
limitations list). Read them as evidence, never as recovered source.
- Good for: understanding behaviour, locating an implementation, interoperability and compatible
re-implementation, security review, migration reference. To obtain actual source code, use the legitimate
route — the upstream repository, vendor authorisation, or the vendor's own SDK.
Cross-platform auto-detection
The shipped patch uses !!js expressions to pick the right command at runtime:
- Windows:
cmd.exe /c rea --mcp— the npm shim is a.cmdfile, so a shell is required. - macOS / Linux:
rea --mcp— the npm shim is a direct executable on PATH.
No manual editing is needed when moving between platforms. The --mcp flag is the canonical stdio-server
startup form documented in rea --help.
Verified against
| Component | Version |
|---|---|
| REA (rea-agents) | 6.5.0 (6.3.0 or newer required) |
| DeepSeek Harness | 0.2.1-alpha.5 (npm CLI) |
| @deepseek-ai/dsh-mcp-client (row provider) | 0.2.1-alpha.5, bundled by the harness |
| Node.js | 22.19+ / 24.11+ / 26+ (REA engine requirement) |
The shipped row was exercised live: rea --mcp answered the MCP initialize handshake and returned
serverInfo: { name: "rea", version: "6.5.0" } with 207 tools. Every pattern in their input schemas
(600, 45 distinct) compiles under the Rust regex engine, the check strict providers such as DeepSeek's
native model apply.
Install
Prerequisites
- Node.js on a version REA accepts (
^22.19.0 || ^24.11.0 || >=26.0.0). - The REA CLI installed globally, version 6.3.0 or newer:
npm i -g rea-agents@latest.
Older releases advertise a tool schema with a \0 regex escape that DeepSeek's native model rejects, so
every turn fails while REA is connected (see [Troubleshooting](#troubleshooting)).
- For native analysis, Ghidra 12.1.x (Hopper / IDA are alternatives under their own licences).
Static JavaScript/Electron and .NET analysis need no engine at all.
The plugin
dsh plugin --profile add dsh-rea
Compare in this category
The five most-starred plugins in the same category.
| Plugin | Author | Stars | Version | Updated |
|---|---|---|---|---|
| treg | superdesigndev | 7.7K | 0.30.0 | 2026-11-10 |
| dsh-im | xmanrui | 3.4K | 5.10.0 | 2026-11-07 |
| DeepSeekBot | BotHarness | 773 | 0.0.0 | 2026-11-10 |
| sandbase-harness | sandbaseai | 642 | 0.0.1 | 2026-11-08 |
| MisakaNet | Ikalus1988 | 558 | 3.9.0 | 2026-11-10 |