# io.github.GuardBee/reverse-shield (npm · @guardbee/mcp-reverse-shield)

Audits shipped apps for how easily they can be reverse engineered

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

## Components

- npm · `@guardbee/mcp-reverse-shield`: 85/100 (this document), [markdown](https://verifymcp.io/servers/guardbee-reverse-shield/guardbee-mcp-reverse-shield.md), [page](https://verifymcp.io/servers/guardbee-reverse-shield/guardbee-mcp-reverse-shield)

## Channel facts

- Registry: `npm`
- Package: `@guardbee/mcp-reverse-shield`
- Version: `0.6.1`
- 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-04.

- **Supply Chain Security**: 98/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.
  - 30 of 97 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to GuardBee/guardbee-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 587 tokens (~146/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the io.github.GuardBee/reverse-shield MCP server?

io.github.GuardBee/reverse-shield runs locally as an npm package, launched with npx -y @guardbee/mcp-reverse-shield. 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 guardbee-reverse-shield -- npx -y @guardbee/mcp-reverse-shield
```

### Cursor

```json
{
  "mcpServers": {
    "guardbee-reverse-shield": {
      "command": "npx",
      "args": [
        "-y",
        "@guardbee/mcp-reverse-shield"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "guardbee-reverse-shield": {
      "command": "npx",
      "args": [
        "-y",
        "@guardbee/mcp-reverse-shield"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add guardbee-reverse-shield -- npx -y @guardbee/mcp-reverse-shield
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add guardbee-reverse-shield --command npx --arg -y --arg @guardbee/mcp-reverse-shield
```

### Hermes

```yaml
mcp_servers:
  guardbee-reverse-shield:
    command: "npx"
    args: ["-y", "@guardbee/mcp-reverse-shield"]
```

### Netclaw

```json
{
  "McpServers": {
    "guardbee-reverse-shield": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@guardbee/mcp-reverse-shield"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add guardbee-reverse-shield -t stdio -c npx -a -y @guardbee/mcp-reverse-shield
```

### Other

```json
{
  "mcpServers": {
    "guardbee-reverse-shield": {
      "command": "npx",
      "args": [
        "-y",
        "@guardbee/mcp-reverse-shield"
      ]
    }
  }
}
```

## 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 85, +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-11-03 (score 84, 0)

- [functional] Package version: 0.6.0 → 0.6.1

### 2026-11-02 (score 84, +35)

- [security improvement] Injection markers: unverified → pass
- [security improvement] Known CVEs: partial → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.20
- [functional improvement] MCP protocol: unverified → pass
- [functional] Dependency health: partial → 0.87
- [functional] Package version: 0.5.0 → 0.6.0
- [functional] Package version: 0.4.0 → 0.5.0

### 2026-11-01 (score 49, −34)

- [security regression] Stability: 0.13 → unverified
- [security regression] Tool safety: pass → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.4.0 → 0.5.0

### 2026-10-31 (score 83, +11)

- [security improvement] Known CVEs: unverified → partial
- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Dependency health: unverified → 0.87
- [functional] Package version: 0.3.1 → 0.4.0

### 2026-10-30 (score 72, −10)

- [security regression] Malware scan: pass → unverified
- [security regression] Known CVEs: pass → unverified
- [functional regression] Dependency health: 0.86 → unverified
- [functional] MCP protocol: Implements a current MCP spec version (2026-07-28).
- [functional] Package version: 0.2.0 → 0.3.1
- [functional] Package version: 0.2.0 → 0.3.0

### 2026-10-29 (score 82, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-10-28 (score 66, 0)

- [security improvement] Known CVEs: partial → pass
- [functional regression] Schema quality: pass → fail
- [functional improvement] Stability: unverified → 0.03
- [functional] Schema quality: good → excellent
- [functional] Dependency health: partial → 0.86
- [functional] Package version: 0.1.1 → 0.2.0

## MCP tools (4)

### `scan_artifact` (~298 tokens)

Audit a shipped build artifact for how easily it can be reverse engineered — the defensive counterpart to reverse-engineering MCPs. Accepts an APK, an Electron app (.app bundle, app folder or app.asar), a macOS/Linux/Windows binary (Mach-O, ELF, PE, .NET assembly), a JavaScript bundle or source map, or a build output directory containing any of these. Reports shipped source maps and source code, missing minification/R8/.NET obfuscation, debug info and unstripped symbols, debuggable flags and entitlements, Electron fuses that allow Node/inspector/ASAR tampering, missing code signing, embedded credentials and internal hosts, with an A–F grade.

Input parameters:

- `baseline` (string): Path to a baseline written by `guardbee-reverse-shield scan --update-baseline`; the report then lists new and fixed findings
- `exclude` (array): Skip files/dirs whose path contains one of these strings
- `ignore` (array): Accepted findings to leave out: a rule id, or rule:path-substring (e.g. bundle_secret:firebase-config.js)
- `include` (array): Only check files whose path contains one of these strings
- `maxFiles` (integer): Maximum number of files to check in a directory (default: 5000)
- `path` (string, required): Absolute or relative path to the artifact or build output directory

### `scan_url` (~116 tokens)

Check a live website the way an analyst starts: fetch the page, read its same-site JavaScript bundles, follow sourceMappingURL comments and try <bundle>.map even when the comment was stripped. Reports publicly downloadable source maps (and whether they embed the original sources), unminified or development bundles, embedded credentials and internal hosts. Third-party scripts are not fetched.

Input parameters:

- `maxScripts` (integer): Maximum number of same-site scripts to fetch (default: 25)
- `url` (string, required): Page URL (http or https)

### `suggest_fixes` (~126 tokens)

Read a project's build configuration (Vite, webpack, Next.js, Angular, Create React App, Android Gradle and manifest, React Native, electron-builder / Forge, .NET project files, Flutter) and propose the changes that close what scan_artifact reports: hidden source maps, minification, R8, debuggable and backup flags, Hermes, Electron fuses and ASAR, no embedded PDB. Returns unified diffs to review and apply (git apply); it never modifies files.

Input parameters:

- `projectPath` (string, required): Project source directory (not the build output)

### `list_checks` (~47 tokens)

List every reverse-engineering resistance check, grouped by target (web, electron, android, ios, native, dotnet, framework), with what each finding gives away and how to fix it

## Diagnostics

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

## Score history

- 2026-11-04: 85
- 2026-11-03: 84
- 2026-11-02: 84
- 2026-11-01: 49
- 2026-10-31: 83
- 2026-10-30: 72
- 2026-10-29: 82
- 2026-10-28: 66
- 2026-10-27: 66

## Common questions

### What is the io.github.GuardBee/reverse-shield MCP server?

io.github.GuardBee/reverse-shield is an MCP server listed in the public MCP registry as io.github.GuardBee/reverse-shield. Audits shipped apps for how easily they can be reverse engineered. This page covers its npm package (@guardbee/mcp-reverse-shield).

### Is the io.github.GuardBee/reverse-shield MCP server safe to use?

io.github.GuardBee/reverse-shield scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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.GuardBee/reverse-shield MCP server expose?

io.github.GuardBee/reverse-shield exposes 4 tools: scan_artifact, scan_url, suggest_fixes, list_checks. Their descriptions and schemas cost roughly 587 tokens of context every time the server is loaded.

### Is the io.github.GuardBee/reverse-shield MCP server still maintained?

io.github.GuardBee/reverse-shield is still listed as active in the MCP registry. We last reached this channel on 4 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.GuardBee/reverse-shield MCP server under?

io.github.GuardBee/reverse-shield 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/@guardbee/mcp-reverse-shield
- Socket report: https://socket.dev/npm/package/@guardbee/mcp-reverse-shield
- Repository: https://github.com/GuardBee/guardbee-mcp
- Changelog RSS feed: https://verifymcp.io/servers/guardbee-reverse-shield/guardbee-mcp-reverse-shield.xml
- Changelog JSON feed: https://verifymcp.io/servers/guardbee-reverse-shield/guardbee-mcp-reverse-shield.json
- HTML version of this page: https://verifymcp.io/servers/guardbee-reverse-shield/guardbee-mcp-reverse-shield