Vulnerability Scanner

io.github.4hmetuyarPublished by GitHub account 4hmetuyarv0.2.4Updated Nov 10, 2026

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

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Runs GuardBee security scans on a URL or brand from an AI chat, then returns findings by severity with remediation guidance.

What you can do
  • Start scans on a URL or brand ID, optionally waiting for completion, and run scan-and-report in one step
  • Check live scan status and summary counts, and list workspace scans with filters
  • Fetch findings filtered by severity, scan ID or brand ID
  • Explain each finding and suggest an actionable remediation
When to use it
Useful when you want an assistant to launch web security or compliance scans (including KVKK, GDPR or CCPA focused ones) and then triage and explain the results without leaving the chat.
Requirements
Runs as a local npm package (Node.js) over stdio, typically launched with npx. Requires a GuardBee API key in the GUARDBEE_API_KEY environment variable; GUARDBEE_BASE_URL can point to a custom endpoint. Network access to the GuardBee service is needed.
Before you install
A GuardBee API key is required and is passed as an environment variable, so keep it out of shared configs. Scans are started against third-party URLs and results are stored in your GuardBee workspace. Telemetry is off by default; setting GUARDBEE_TELEMETRY=1 sends server, tool, success, duration and short parameter values such as file paths to the telemetry package.

Installation

In SourceWeft

  1. Open Vulnerability Scanner in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@guardbee/mcp-vulnerability-scanner

🇬🇧 English | 🇹🇷 Türkçe | 🇨🇳 中文 | 🇯🇵 日本語 | 🇰🇷 한국어 | 🇧🇷 Português | 🇪🇸 Español | 🇩🇪 Deutsch

[npm version] [npm downloads] [License: MIT]

Trigger a GuardBee security scan directly from a Claude conversation. Run OWASP checks, query findings, and have the AI prioritize remediation recommendations.

Telemetry is off by default. With GUARDBEE_TELEMETRY=1 it sends the server, tool, success, duration and short parameter values such as a file path; longer strings and fields like content, token or password are replaced with a placeholder. See @guardbee/mcp-telemetry.

A GuardBee API key is required. Get one at app.guardbee.ai/developers.

Features

  • Trigger a Scan from Claude — start a GuardBee scan on any URL with one command
  • Status Queries — check scan progress and summary counts in real time
  • Finding Filters — query by severity, scan ID, or brand ID
  • Remediation Guidance — an explanation and an actionable recommendation for every finding
  • Scan Scenarios — quick, kvkkFocus, gdprFocus, ccpaFocus
  • 36 Scan Modules — all of GuardBee's modules are supported
  • 25 Unit Tests — a test suite that doesn't require API calls

Quick Start

bash
npm install -g @guardbee/mcp-vulnerability-scanner

Add to claude_desktop_config.json:

json
{  "mcpServers": {    "guardbee-vulnerability-scanner": {      "command": "npx",      "args": ["-y", "@guardbee/mcp-vulnerability-scanner"],      "env": {        "GUARDBEE_API_KEY": "gb_..."      }    }  }}

Get your API key at app.guardbee.ai/developers.

MCP Tools

ToolDescription
start_scanStarts a scan for a URL or brand ID; with wait=true waits for completion
get_scan_statusLive status and summary counts by scan ID
list_scansLists workspace scans with filters
get_findingsFetches findings filtered by severity / scanId / brandId
scan_and_reportScan + wait + return critical/high findings and remediation recommendations

Example Usage

You can ask Claude:

"Scan https://example.com and give me a security report"

"List my recent scans"

"Show critical findings for scan clz001 and explain how to fix them"

"Run a KVKK-focused scan on example.com"

Example Output

⚠️  Security scan complete for https://example.com   Scan ID  : clz001abc   🔴 Critical : 2   🟠 High     : 5   🟡 Medium   : 8   🔵 Low      : 3   ⚪ Info     : 12   ✅ Passed   : 18
Use get_findings with scanId="clz001abc" to see details and remediation steps.

Scan Scenarios

ScenarioDescription
quickAll 36 modules — comprehensive general scan
kvkkFocusFocused on KVKK compliance modules
gdprFocusFocused on GDPR compliance modules
ccpaFocusFocused on CCPA compliance modules

Environment Variables

VariableDescription
GUARDBEE_API_KEYGuardBee API key (required)
GUARDBEE_BASE_URLCustom endpoint (default: https://app.guardbee.ai)

Development

bash
npm installnpm test          # 25 unit testsnpm run build     # TypeScript compile

License

MIT — GuardBee

Feedback

Questions, ideas, or a false positive? Start a thread in GitHub Discussions or open an issue. If GuardBee is useful to you, a ⭐ on the repository helps others find it.

Source: packages/vulnerability-scanner/README.md at commit 040e072

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.4LatestSep 29, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts