@guardbee/mcp-vulnerability-scanner

MCPcommunity
v0.2.4io.github.4hmetuyarMITUpdated 12d agonpmGitHub

Triggers GuardBee scans, queries findings, AI-assisted remediation guidance

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
68Downloads/wk
1GitHub stars
1Forks
12d agoLast update
Package
Authorio.github.4hmetuyar
LicenseMIT
Version0.2.4
Sourcenpm+mcp-registry
npm@guardbee/mcp-vulnerability-scanner
GitHubGuardBee/guardbee-mcp
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface5 tools · none privileged
Security scan✓ Cleanv0.2.4 · todayHow well does this scan work?
EvalsNone
IndexedOct 9, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

5 tools · none privileged
Statically extracted from the published packagev0.2.4 · 15h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

start_scanStart a GuardBee security scan on a URL. Returns a scan ID you can use to check status and get findings.

Start a GuardBee security scan on a URL. Returns a scan ID you can use to check status and get findings.

No input schema was published for this tool.

get_scan_statusGet the current status and summary of a GuardBee scan by ID

Get the current status and summary of a GuardBee scan by ID

No input schema was published for this tool.

list_scansList recent GuardBee scans in your workspace

List recent GuardBee scans in your workspace

No input schema was published for this tool.

get_findingsGet vulnerability findings from a GuardBee scan with optional severity filter. Includes title, description, and remediation recommendation per finding.

Get vulnerability findings from a GuardBee scan with optional severity filter. Includes title, description, and remediation recommendation per finding.

No input schema was published for this tool.

scan_and_reportRun a full GuardBee scan and immediately return all critical and high findings with remediation guidance. Best for quick security assessments.

Run a full GuardBee scan and immediately return all critical and high findings with remediation guidance. Best for quick security assessments.

No input schema was published for this tool.

5 of 5 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Triggers GuardBee scans, queries findings, AI-assisted remediation guidance

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

5 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-10-10 — observed resolution, not a publisher declaration.

60 packages resolved · 3 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

55 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+43 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in security