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
Available components
Last scanned (17 hours ago)
Scores higher than 79% of npm servers
Category Security
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. How we score → Why this is hard to score →
Supply Chain Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 102 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to GuardBee/guardbee-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 280 tokens (~70/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 67% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 24 Oct 26 +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.
- 23 Oct 26 +32
- Injection markers: unverified → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.27 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Package version: 0.2.7 → 0.3.3 functional
- 22 Oct 26 −28
- Known CVEs: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- 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. security
- Dependency health: 0.88 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.23 ▲ functional
- 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 functional
- 15 Oct 26 +29
- 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). security
- Tool coverage: unverified → 100 ▲ functional
- 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 functional
- 14 Oct 26 0
- 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. security
- 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 functional
- 13 Oct 26 0
- Package version: 0.2.5 → 0.2.6 functional
- 12 Oct 26 0
- Package version: 0.2.2 → 0.2.5 functional
- 11 Oct 26 49
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Oct 2026 · Analysed npm/@guardbee/mcp-owasp-scan@0.3.3
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | GuardBee/guardbee-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/GuardBee/guardbee-mcp/.github/workflows/release.yml@refs/heads/main |
| Rekor log index | 3396731543 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:0acca4d37818956d3e25679ed55f853ab3edbe499bf609038b0abb30bf4d6d7d718d72dd7367dd22d0ab95e219ad99c01eb0294eee7559c3163363b4d |
Background: How many MCP packages publish verified provenance →
Dependencies 102 packages
| Packages resolved | 102 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
list_owasp_coverage ~33
List OWASP MCP Top 10 categories and which GuardBee scanners cover them in this meta-scan
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
owasp_scan_catalog ~59
Audit a tools/list JSON dump for toxic flows and tool-description poisoning (MCP03/MCP10).
| Name | Type | Req | Description |
|---|---|---|---|
| catalog | string | yes | JSON string: { tools: [...] } or a bare tools array |
| label | string | – | – |
No output schema declared.
No examples provided.
owasp_scan_live ~74
Connect to a live MCP server (stdio or HTTP), call tools/list, then grade toxic-flow + tool-poisoning (MCP03/MCP10).
| Name | Type | Req | Description |
|---|---|---|---|
| args | array | – | – |
| command | string | – | stdio command to spawn |
| url | string | – | Streamable HTTP MCP URL |
No output schema declared.
No examples provided.
owasp_scan_path ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| allowlistPath | string | – | Allowlist file for Shadow MCP discover |
| discoverShadow | boolean | – | Also discover Shadow MCP on this host (MCP09) |
| maxFiles | integer | – | – |
| path | string | yes | File or directory to scan |
No output schema declared.
No examples provided.
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.
npm · @guardbee/mcp-owasp-scan
claude mcp add guardbee-owasp-scan -- npx -y @guardbee/mcp-owasp-scan
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.