# io.github.Firzus/reverse-engineer (npm · reverse-engineer)

Read-only reverse engineering of Electron apps, PE/ELF/Mach-O binaries, Go/Rust, .NET and APKs.

- Trust score: 86/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `reverse-engineer`: 86/100 (this document), [markdown](https://verifymcp.io/servers/firzus-reverse-engineer/reverse-engineer.md), [page](https://verifymcp.io/servers/firzus-reverse-engineer/reverse-engineer)

## Channel facts

- Registry: `npm`
- Package: `reverse-engineer`
- Version: `0.1.0-alpha.2`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to Firzus/agent-skills).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 12 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 846 tokens (~105/item across 8 items; 8 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 86/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 58% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.Firzus/reverse-engineer MCP server?

io.github.Firzus/reverse-engineer runs locally as an npm package, launched with npx -y reverse-engineer. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add firzus-reverse-engineer -- npx -y reverse-engineer
```

### Cursor

```json
{
  "mcpServers": {
    "firzus-reverse-engineer": {
      "command": "npx",
      "args": [
        "-y",
        "reverse-engineer"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "firzus-reverse-engineer": {
      "command": "npx",
      "args": [
        "-y",
        "reverse-engineer"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add firzus-reverse-engineer -- npx -y reverse-engineer
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "firzus-reverse-engineer": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "reverse-engineer"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add firzus-reverse-engineer --command npx --arg -y --arg reverse-engineer
```

### Hermes

```yaml
mcp_servers:
  firzus-reverse-engineer:
    command: "npx"
    args: ["-y", "reverse-engineer"]
```

### Netclaw

```json
{
  "McpServers": {
    "firzus-reverse-engineer": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "reverse-engineer"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add firzus-reverse-engineer -t stdio -c npx -a -y reverse-engineer
```

### Other

```json
{
  "mcpServers": {
    "firzus-reverse-engineer": {
      "command": "npx",
      "args": [
        "-y",
        "reverse-engineer"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 83, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 83, +1)

- [functional regression] Security disclosure: fail → unverified

### 2026-10-27 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 81, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-10-23 (score 65, −3)

- [security regression] Malware scan: pass → unverified
- [security improvement] Provenance: fail → pass
- [security] The attested source repository moved: Firzus/agent-skills
- [functional improvement] Stability: unverified → 0.13
- [functional] Package version: 0.1.0-alpha.1 → 0.1.0-alpha.2

## MCP tools (8)

### `triage` (~56 tokens)

Identify a file or directory: format, architecture, size, SHA-256, markers (Go, Rust, Electron, N-API, packers) and the next tool to call.

Input parameters:

- `path` (string, required): File or directory

### `electron_surface` (~112 tokens)

Electron app map: extracts app.asar (cached), main entry, preloads and exposed APIs, native .node addons and the addon names called from JS, IPC channels grouped by call site, fuses, asar integrity. Use focus (one or more words) to filter on one feature.

Input parameters:

- `focus` (string): Feature words, comma-separated, e.g. audio,microphone; filters channels and lists matching identifiers
- `path` (string, required): App directory, resources directory, executable or .asar

### `search` (~154 tokens)

Search a directory, an extracted app, a .asar (auto-extracted) or one file. Hidden folders included, node_modules skipped by default. Returns file:line:col (or file@offset for binaries) with a short excerpt.

Input parameters:

- `context` (integer): Characters of context on each side
- `glob` (string): Filter, e.g. *.js or .webpack/**/*.js
- `ignore_case` (boolean)
- `include_deps` (boolean): Also search node_modules
- `max` (integer)
- `path` (string, required): Directory, .asar or file
- `pattern` (string, required): Literal text, or a JavaScript regex when regex=true
- `regex` (boolean)

### `read` (~128 tokens)

Read a slice: lines start..end; for minified code a column window (start=line, col, length); for binaries a hexdump at offset. A directory path lists its entries.

Input parameters:

- `col` (integer): Column in line `start` for minified code
- `end` (integer): Last line, default start+79
- `length` (integer): Characters (col/offset mode) or bytes
- `offset` (integer): Byte offset (hexdump for binaries)
- `path` (string, required)
- `start` (integer): First line (1-based)

### `binary_inventory` (~98 tokens)

PE, ELF or Mach-O inventory. part=summary (default): format, sections, libraries with imports, exports, Node addon names, notable strings. Other parts list one table, paged with skip and filtered by a regex.

Input parameters:

- `filter` (string): Case-insensitive regex on names or strings
- `max` (integer)
- `part` (string)
- `path` (string, required)
- `skip` (integer)

### `buildinfo` (~63 tokens)

Go build info (toolchain, main package, module, build settings, dependency versions) and Rust cargo-auditable dependencies, parsed from the binary without running it.

Input parameters:

- `filter` (string): Regex on dependency paths or crate names
- `path` (string, required)

### `decompile` (~103 tokens)

Ghidra headless decompilation, cached per file. First call analyzes the binary (can take minutes). function=NAME|ADDRESS returns its C; containing=TEXT lists functions that reference a string; neither lists functions.

Input parameters:

- `containing` (string): Find functions that reference this string
- `function` (string): Function name, FUN_xxx or address
- `max` (integer)
- `path` (string, required)
- `skip` (integer)

### `managed` (~74 tokens)

.NET assemblies (via ilspycmd) and APK/DEX/JAR (via jadx): decompile once into the cache, summarize namespaces, manifest, P/Invoke and native libraries; type=Name returns one type's source.

Input parameters:

- `path` (string, required)
- `type` (string): Fully qualified or short type name

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/firzus-reverse-engineer/reverse-engineer#diagnostics

## Score history

- 2026-11-05: 86
- 2026-11-04: 86
- 2026-11-03: 85
- 2026-11-02: 85
- 2026-11-01: 84
- 2026-10-31: 84
- 2026-10-30: 83
- 2026-10-29: 83
- 2026-10-28: 82
- 2026-10-27: 82
- 2026-10-26: 81
- 2026-10-25: 81
- 2026-10-24: 81
- 2026-10-23: 65
- 2026-10-22: 68
- 2026-10-21: 68
- 2026-10-20: 68
- 2026-10-19: 53

## Common questions

### What is the io.github.Firzus/reverse-engineer MCP server?

io.github.Firzus/reverse-engineer is an MCP server listed in the public MCP registry as io.github.Firzus/reverse-engineer. Read-only reverse engineering of Electron apps, PE/ELF/Mach-O binaries, Go/Rust, .NET and APKs. This page covers its npm package (reverse-engineer).

### Is the io.github.Firzus/reverse-engineer MCP server safe to use?

io.github.Firzus/reverse-engineer scores 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.Firzus/reverse-engineer MCP server expose?

io.github.Firzus/reverse-engineer exposes 8 tools: triage, electron_surface, search, read, binary_inventory, and 3 more. Their descriptions and schemas cost roughly 788 tokens of context every time the server is loaded.

### Is the io.github.Firzus/reverse-engineer MCP server still maintained?

io.github.Firzus/reverse-engineer is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the io.github.Firzus/reverse-engineer MCP server under?

io.github.Firzus/reverse-engineer declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/reverse-engineer
- Socket report: https://socket.dev/npm/package/reverse-engineer
- Repository: https://github.com/Firzus/agent-skills
- Changelog RSS feed: https://verifymcp.io/servers/firzus-reverse-engineer/reverse-engineer.xml
- Changelog JSON feed: https://verifymcp.io/servers/firzus-reverse-engineer/reverse-engineer.json
- HTML version of this page: https://verifymcp.io/servers/firzus-reverse-engineer/reverse-engineer
