Melakukan reverse engineering read-only pada aplikasi Electron, binary, Go/Rust, .NET, dan APK menggunakan parser TypeScript dengan lokasi yang dapat dikutip.
Juga dikenal sebagai Firzus/agent-skills
- Stars
- 4
- Tools
- 8
- Unduhan, 30 hari
- —
- Versi terbaru
- 0.1.0-alpha.2
- Commit terakhir
- 14 Nov 2026
- Lisensi
- MIT
Apa itu reverse-engineer MCP?
Melakukan reverse engineering read-only pada aplikasi Electron, binary, Go/Rust, .NET, dan APK menggunakan parser TypeScript dengan lokasi yang dapat dikutip. Server ini menyediakan 8 tool, seperti triage, electron_surface, search.
Ringkasan dibuat dari README proyek
Tentang reverse-engineer MCP server
Server ini memungkinkan Anda menganalisis kode terkompilasi dan aplikasi Electron langsung dari dalam AI client. Server menyediakan lingkungan read-only untuk memeriksa binary, build Go atau Rust, assembly .NET, dan file APK menggunakan parser berbasis TypeScript. Alih-alih mengandalkan perintah platform yang rentan seperti otool atau strings, server ini menggunakan tool khusus untuk memberikan jawaban ringkas dan terverifikasi yang menyertakan lokasi file spesifik, nomor baris, atau memory offset.
Developer dapat menggunakan server ini dengan mengonfigurasinya sebagai MCP server via npx di pengaturan client mereka. Server ini memerlukan Node.js 24.11 atau versi terbaru dan dapat diintegrasikan secara opsional dengan Ghidra, ilspycmd, dan jadx untuk dekompilasi tingkat lanjut dan analisis managed code. Untuk menjaga performa, server melakukan caching pada hasil ekstraksi dan analisis berdasarkan SHA-256 serta memastikan semua respons tetap di bawah batas 8 KB, dengan menyediakan path ke file cache yang lebih besar jika diperlukan. Pendekatan ini memungkinkan inspeksi mendalam terhadap channel IPC Electron, integritas asar, dan section binary tanpa pernah mengeksekusi kode target tersebut.
Apa yang bisa Anda lakukan dengannya
- 1Triage properti file binaryIdentifikasi arsitektur, magic bytes, dan build markers dari sebuah file yang mencurigakan.
- 2Inspeksi internal aplikasi ElectronPeriksa ekstraksi asar, channel IPC, dan nama Node addon yang digunakan oleh aplikasi Electron.
- 3Decompile managed codeRingkas dan decompile file .NET atau Android APK untuk memahami tipe dan fungsinya.
- 4Pencarian melalui aset terkompilasiLakukan pencarian terbatas untuk string atau pola spesifik di dalam file tree atau asar.
Ditulis berdasarkan README proyek. Setiap use case diperiksa terhadap kutipan dari README tersebut.
Cara menginstal reverse-engineer MCP
Format diverifikasi 10 Nov 2026Tambahkan ke CursorTambahkan ke GooseInstal reverse-engineer MCP di Claude Code
$ claude mcp add reverse-engineer -- npx -y reverse-engineerInstal reverse-engineer MCP di Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"reverse-engineer": {
"command": "npx",
"args": [
"-y",
"reverse-engineer"
]
}
}
}Instal reverse-engineer MCP di VS Code
.vscode/mcp.json
{
"servers": {
"reverse-engineer": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"reverse-engineer"
]
}
}
}Instal reverse-engineer MCP di VS Code CLI
$ code --add-mcp '{"name":"reverse-engineer","type":"stdio","command":"npx","args":["-y","reverse-engineer"]}'Instal reverse-engineer MCP di Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"reverse-engineer": {
"command": "npx",
"args": [
"-y",
"reverse-engineer"
]
}
}
}Instal reverse-engineer MCP di Codex
$ codex mcp add reverse-engineer -- npx -y reverse-engineerInstal reverse-engineer MCP di Codex config.toml
~/.codex/config.toml
[mcp_servers.reverse-engineer] command = "npx" args = ["-y", "reverse-engineer"]
Instal reverse-engineer MCP di Gemini CLI
$ gemini mcp add -s user reverse-engineer npx -- -y reverse-engineerInstal reverse-engineer MCP di Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"reverse-engineer": {
"command": "npx",
"args": [
"-y",
"reverse-engineer"
]
}
}
}Tool reverse-engineer MCP 8
Terdeteksi dari READMEtriageelectron_surfacesearchreadbinary_inventorybuildinfodecompilemanaged
| triage | — | |
| electron_surface | — | |
| search | — | |
| read | — | |
| binary_inventory | — | |
| buildinfo | — | |
| decompile | — | |
| managed | — |
Pengecekan otomatis
Berjalan 13 Nov 2026Laporan lengkap →Lolos checks otomatis kami. Ini bukan audit keamanan: baca kodenya dan berikan server akses paling terbatas yang dibutuhkannya. Cara kerja checks
- Source repository terhubung dan dapat dijangkauLolos
- Lisensi open source (OSI)Lolos
- Ada commit atau release dalam satu tahun terakhirLolos
- Nama package tidak mirip dengan package populerLolos
- Remote endpoint menggunakan HTTPSTidak diperiksa
- Tools yang bersifat destruktif telah diberi labelLolos
- Tidak ada instruksi tersembunyi untuk modelLolos
- Tidak ada advisory kritis pada paket atau dependensinyaLolos
README
Lihat di GitHubreverse-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.exe
npx -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 <checkout>/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 install
npx 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.
Pertanyaan tentang reverse-engineer MCP
Bagaimana cara menambahkan reverse-engineer MCP ke Claude Code?
Jalankan claude mcp add reverse-engineer -- npx -y reverse-engineer di terminal Anda. Tambahkan --scope user agar tersedia di semua proyek.
Bagaimana cara menambahkan reverse-engineer MCP ke Cursor?
Buka ~/.cursor/mcp.json dan tambahkan server di bawah mcpServers, menggunakan config Cursor yang ditunjukkan di bagian instalasi di atas.
Tool apa yang disediakan reverse-engineer MCP?
Server ini menyediakan 8 tool, termasuk triage, electron_surface, search, read, binary_inventory.
Apakah server ini mampu menjalankan kode target?
Tidak, tool ini bersifat strictly read-only dan tidak akan pernah menjalankan file target tersebut.
Bagaimana server menangani output yang besar?
Jawaban secara default dijaga agar tetap ringkas (di bawah 8 KB); output yang lebih panjang akan ditulis ke cache dan jawaban akan menyediakan path untuk paging.
Apa yang terjadi jika sebuah binary malformed atau berbahaya?
Server dirancang untuk beralih ke hasil parsial daripada mengalami hang saat menemukan binary yang malformed atau berbahaya.