# io.github.GuardBee/owasp-scan (npm · @guardbee/mcp-owasp-scan)

Unified OWASP MCP Top 10 scan — path or live tools/list, A–F grade, SARIF

- Trust score: 83/100 (high trust)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-25

## Components

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

## Channel facts

- Registry: `npm`
- Package: `@guardbee/mcp-owasp-scan`
- Version: `0.3.3`
- 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-10-25.

- **Supply Chain Security**: 99/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 102 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 2 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 280 tokens (~70/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 89/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 67% 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.GuardBee/owasp-scan MCP server?

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

### Cursor

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

### VS Code

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

### Codex

```bash
codex mcp add guardbee-owasp-scan -- npx -y @guardbee/mcp-owasp-scan
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add guardbee-owasp-scan --command npx --arg -y --arg @guardbee/mcp-owasp-scan
```

### Hermes

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

### Netclaw

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

### Vellum

```bash
assistant mcp add guardbee-owasp-scan -t stdio -c npx -a -y @guardbee/mcp-owasp-scan
```

### Other

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

## 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-10-24 (score 83, +1)

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

### 2026-10-23 (score 82, +32)

- [security improvement] Injection markers: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.27
- [functional improvement] MCP protocol: unverified → pass
- [functional] Package version: 0.2.7 → 0.3.3

### 2026-10-22 (score 50, −28)

- [security regression] Known CVEs: pass → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Known CVEs: pass → partial
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Dependency health: 0.88 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Stability: unverified → 0.23
- [functional improvement] Security disclosure: fail → pass
- [functional] Dependency health: 0.88 → partial
- [functional] Package version: 0.2.7 → 0.3.3
- [functional] Package version: 0.2.7 → 0.3.2
- [functional] Package version: 0.2.7 → 0.3.1
- [functional] Package version: 0.2.7 → 0.3.0

### 2026-10-15 (score 78, +29)

- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Tool coverage: 67
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: pass
- [functional] First check of Schema quality: good

### 2026-10-14 (score 49, 0)

- [security improvement] Known CVEs: partial → pass
- [security] Stability: Stability not yet verified: this package could not be installed in a clean environment, so we have no schema to compare.
- [security] Tool safety: Tool safety not yet verified: this package could not be installed in a clean environment, so we have no tool text to scan.
- [functional] Schema quality: Schema quality not yet verified: this package could not be installed in a clean environment, so we have no schema to assess.
- [functional] Capabilities: Protocol version not yet verified: this package could not be installed in a clean environment, so we never saw its MCP handshake.
- [functional] Tool coverage: Tool coverage not yet verified: this package could not be installed in a clean environment, so we have no tool definitions to assess.
- [functional] Dependency health: partial → 0.88
- [functional] Package version: 0.2.6 → 0.2.7

### 2026-10-13 (score 49, 0)

- [functional] Package version: 0.2.5 → 0.2.6

### 2026-10-12 (score 49, 0)

- [functional] Package version: 0.2.2 → 0.2.5

### 2026-10-11 (score 49)

First indexed and scored.

## MCP tools (4)

### `owasp_scan_path` (~114 tokens)

Run a unified OWASP MCP Top 10 scan over a filesystem path — orchestrates secret, server, oauth, audit-gap, context-oversharing, toxic-flow, and tool-poisoning auditors; returns A–F grade.

Input parameters:

- `allowlistPath` (string): Allowlist file for Shadow MCP discover
- `discoverShadow` (boolean): Also discover Shadow MCP on this host (MCP09)
- `maxFiles` (integer)
- `path` (string, required): File or directory to scan

### `owasp_scan_live` (~74 tokens)

Connect to a live MCP server (stdio or HTTP), call tools/list, then grade toxic-flow + tool-poisoning (MCP03/MCP10).

Input parameters:

- `args` (array)
- `command` (string): stdio command to spawn
- `url` (string): Streamable HTTP MCP URL

### `owasp_scan_catalog` (~59 tokens)

Audit a tools/list JSON dump for toxic flows and tool-description poisoning (MCP03/MCP10).

Input parameters:

- `catalog` (string, required): JSON string: { tools: [...] } or a bare tools array
- `label` (string)

### `list_owasp_coverage` (~33 tokens)

List OWASP MCP Top 10 categories and which GuardBee scanners cover them in this meta-scan

## Diagnostics

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

## Score history

- 2026-10-25: 83
- 2026-10-24: 83
- 2026-10-23: 82
- 2026-10-22: 50
- 2026-10-21: 78
- 2026-10-20: 78
- 2026-10-19: 78
- 2026-10-18: 78
- 2026-10-17: 78
- 2026-10-16: 78
- 2026-10-15: 78
- 2026-10-14: 49
- 2026-10-13: 49
- 2026-10-12: 49
- 2026-10-11: 49

## Common questions

### What is the io.github.GuardBee/owasp-scan MCP server?

io.github.GuardBee/owasp-scan is an MCP server listed in the public MCP registry as io.github.GuardBee/owasp-scan. Unified OWASP MCP Top 10 scan, path or live tools/list, A–F grade, SARIF. This page covers its npm package (@guardbee/mcp-owasp-scan).

### Is the io.github.GuardBee/owasp-scan MCP server safe to use?

io.github.GuardBee/owasp-scan scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 October 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/owasp-scan MCP server expose?

io.github.GuardBee/owasp-scan exposes 4 tools: owasp_scan_path, owasp_scan_live, owasp_scan_catalog, list_owasp_coverage. Their descriptions and schemas cost roughly 280 tokens of context every time the server is loaded.

### Is the io.github.GuardBee/owasp-scan MCP server still maintained?

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

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