Spec Driven Development
by formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer★ 440MITUpdated 14 months ago
Install
Reverse Engineer
Overview
Description from the maker (original English)
Read-only reverse engineering of Electron apps, PE/ELF/Mach-O binaries, Go/Rust, .NET and APKs.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Other
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- The registry lists no key to fill in.
You need
- npmNode.js installed (for the npx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"reverse-engineer": {
"command": "npx",
"args": [
"-y",
"reverse-engineer",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add reverse-engineer -- npx -y reverse-engineer mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"reverse-engineer": {
"command": "npx",
"args": [
"-y",
"reverse-engineer",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"reverse-engineer": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"reverse-engineer",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account Firzus, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Otheri
- More stars than 0% of the other 32435 servers in this category
- Published to the registry more recently than 73% of the other 32435 servers in this category
- Basic checks equal to or better than 100% of the other 32435 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Reverse Engineer safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.1.0-alpha.2) reached the registry 14 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, Apify MCP Server
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Remote Desktop Commander
by desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud★ 211Updated yesterday
Install
Apify MCP Server
by apify
Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡
Runs in the cloudUpdated today
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
reverse-engineer server
The read-only MCP server and CLI behind the reverse-engineer skill. The skill is the agent-facing entry point; this server replaces the commands that are missing or fragile on a given platform (otool, strings, jq, go version -m, asar extraction) with TypeScript parsers, and answers in at most 8 KB with citable locations. Installing the skill does not install the server.
Tools
| Tool | What it returns |
|---|---|
triage | Format by magic bytes, architecture, size, SHA-256, markers (Go, Rust, Electron fuses, N-API, packers) and the next call |
electron_surface | Cached asar extraction, main, preloads and exposeInMainWorld keys, .node addons and the addon names called from JS, IPC channels grouped by call site (app wrappers included), fuses, asar integrity |
search | Bounded search in a tree, a .asar or one file (hidden folders included), with file:line:col or file@offset and a short excerpt |
read | Line ranges, a column window for minified code (instead of reformatting it), hexdumps |
binary_inventory | PE, ELF and Mach-O sections, libraries and imports, exports, Node addon names, ASCII and UTF-16 strings, PE resources |
buildinfo | Go build info (toolchain, main package, module, settings, dependencies) and Rust cargo-auditable packages |
decompile | Ghidra headless, cached per file: list functions, map a string to the functions that use it, return one function's C |
managed | .NET (via ilspycmd) and APK/DEX/JAR (via jadx): decompile once, summarize, return one type |
The catalog is about 6 KB for the 8 tools; the skill is about 5.5 KB.
Design rules:
- Compact by default. Each answer stays under
REVERSE_ENGINEER_MAX_BYTES(8192). Longer output is written to the cache, and the answer ends with its path, soreadandsearchcan page through it. - Cited facts. Every location is
file:line:col,file@0xoffset, a symbol or a string. - No blocking on common cases. A
.nodefile signed after packaging shows up as an unverified hash, not as an error. Malformed or hostile binaries degrade to partial results instead of hanging. - Read-only. The tools never run the target. They write only to their cache:
%LOCALAPPDATA%\reverse-engineer\cache,~/Library/Caches/reverse-engineer, or$XDG_CACHE_HOME/reverse-engineer(override withREVERSE_ENGINEER_CACHE). Exceptions: Ghidra refuses project paths with a dot folder, so with such a cache path (the Linux default~/.cache) its projects go to a private per-user folder in the temp directory; when the cache path contains a space, Ghidra keeps its settings in the home folder; jadx and the .NET SDK may write their own settings there on first use. - Cache by SHA-256. An extraction or an analysis is reused.
Use
Requirements: Node.js 24.11 or later. Optional: Ghidra 11+ with JDK 21 for decompile, ilspycmd (.NET 10 SDK) and jadx (JDK 21) for managed. The agent can install them with the skill's install guide: official releases go into a per-user tools root (%LOCALAPPDATA%\reverse-engineer\tools, ~/Library/Application Support/reverse-engineer/tools, or $XDG_DATA_HOME/reverse-engineer/tools; override with REVERSE_ENGINEER_TOOLS), without admin rights or a PATH change. The tools look there first, then on PATH, GHIDRA_INSTALL_DIR and the usual install folders.
The package is published to npm as an alpha prerelease, reverse-engineer, and listed in the MCP Registry as io.github.Firzus/reverse-engineer. Pin the exact version:
npx -y reverse-engineer@0.1.0-alpha.2 triage ./some.exenpx -y reverse-engineer@0.1.0-alpha.2 electron_surface "C:\Program Files\App" --focus audio,microphone
Claude Code MCP configuration (project .mcp.json):
{"mcpServers": { "reverse-engineer": { "command": "npx", "args": ["-y", "reverse-engineer@0.1.0-alpha.2", "mcp"] } } }
On Windows, use "command": "cmd" with "args": ["/c", "npx", "-y", "reverse-engineer@0.1.0-alpha.2", "mcp"]. To run an unreleased build from a clone, run the Develop commands, then point the configuration at node /mcp/reverse-engineer/dist/cli.mjs mcp.
Install the skill with npx skills add Firzus/agent-skills --skill reverse-engineer.
Develop
The toolchain is Vite+ (vite-plus, local dev dependency). .github/workflows/reverse-engineer-check.yml runs the same checks on Windows, macOS and Linux:
npm installnpx vp check # format, lint, type check npx vp test # unit tests on synthetic and hostile fixtures npx vp pack # bundle dist/cli.mjs, a single file with no runtime dependency
Tests against real targets are opt-in: set RE_TARGETS (a folder with app.asar, app.asar.unpacked/ and gh.exe), RE_NOTION_DIR (an installed Notion app), RE_GHIDRA=1, RE_DOTNET_DLL, or RE_APK.
Release
.github/workflows/reverse-engineer-publish.yml publishes to npm and the MCP Registry. Merging a version change to main publishes it, so treat the merge as the release decision. In the release pull request:
- Set the same version in
package.json,package-lock.json,server.json, the pinned commands above and in the skill'sSKILL.md; a unit test checks the first three. Whenvp packreports a new bundled dependency, add its license toTHIRD_PARTY_NOTICES.md. - Run the Develop checks, then
npm pack(it rebuildsdist/) and inspect the tarball:LICENSE,README.md,THIRD_PARTY_NOTICES.md,dist/cli.mjs,ghidra/ExportDecompiled.java,package.json.
The workflow stops when the version is already on npm and the MCP Registry. Otherwise it runs the check workflow, builds the tarball in a job without publishing rights, then publishes in the release environment, from a job that runs no project or dependency code. npm uses trusted publishing, with a prerelease published under its own dist-tag (alpha), never latest; the MCP Registry uses its GitHub OIDC login. A last job runs the published --version. When a run fails, fix the cause and use Re-run all jobs on that run: each publication step rechecks its registry and skips what already exists. Never overwrite or unpublish a version to hide a failed release; publish a new one.
npm must trust the workflow before the first automated release: in the reverse-engineer package settings, add a GitHub Actions trusted publisher with user Firzus, repository agent-skills, workflow reverse-engineer-publish.yml and environment release.
Benchmark
bench/ adapts the harness from leanrea to Windows and compares four arms: no skill, leanrea, REA (MCP and skill), and this tool. See bench/BENCHMARK.md for the method, the results and their limits.
License
MIT. The benchmark tasks and harness are adapted from leanrea, MIT-licensed; its notice is in bench/LICENSE-leanrea. Fuse names and the Go build-info layout follow the public formats documented by Electron and the Go toolchain; no code is copied from REA.