Triggers security scans, queries findings, and provides AI-assisted remediation guidance for web vulnerabilities and compliance.
Also known as GuardBee/guardbee-mcp, @guardbee/mcp-vulnerability-scanner
- Stars
- 2
- Tools
- 5
- Downloads, 30 days
- 1,957
- Latest version
- 0.2.4
- Last commit
- Nov 12, 2026
- License
- MIT
What is GuardBee Vulnerability Scanner MCP?
GuardBee Vulnerability Scanner triggers security scans, queries findings, and provides AI-assisted remediation guidance for web vulnerabilities and compliance. It exposes 5 tools, such as start_scan, get_scan_status, list_scans.
Summary generated from the project's README
About GuardBee Vulnerability Scanner MCP server
Security professionals and developers can trigger web vulnerability scans and manage compliance checks directly from a Claude conversation. By connecting this server to a Claude desktop client using a required GuardBee API key, users can initiate security assessments on specific URLs or brand IDs. The server supports 36 different scan modules and provides real-time updates on scan progress.
Users can choose from specific scan scenarios including quick, kvkkFocus, gdprFocus, and ccpaFocus to target different regulatory requirements. The toolset includes functions like start_scan to begin an assessment, get_scan_status to monitor live progress, and get_findings to retrieve specific vulnerabilities filtered by severity or scan ID. It also offers a scan_and_report tool that combines scanning with the retrieval of critical findings and remediation steps.
Beyond just identifying issues, the server provides actionable remediation guidance for every finding discovered. This allows an AI client to explain security risks and suggest concrete ways to fix them. The system is configured via environment variables such as GUARDBEE_API_KEY and can be customized with a GUARDBEE_BASE_URL if a custom endpoint is needed.
What you can do with it
- 1Monitor scan progressCheck the live status and summary counts of an ongoing security scan.
- 2Analyze compliance vulnerabilitiesRun a targeted scan specifically designed to check for GDPR compliance modules.
- 3Get remediation instructionsRetrieve critical security findings and the specific steps required to fix them.
Written from the project's README. Every use case is checked against a quote from it.
How to install GuardBee Vulnerability Scanner MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall GuardBee Vulnerability Scanner MCP in Claude Code
$ claude mcp add vulnerability-scanner -- npx -y @guardbee/mcp-vulnerability-scannerInstall GuardBee Vulnerability Scanner MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"vulnerability-scanner": {
"command": "npx",
"args": [
"-y",
"@guardbee/mcp-vulnerability-scanner"
]
}
}
}Install GuardBee Vulnerability Scanner MCP in VS Code
.vscode/mcp.json
{
"servers": {
"vulnerability-scanner": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@guardbee/mcp-vulnerability-scanner"
]
}
}
}Install GuardBee Vulnerability Scanner MCP in VS Code CLI
$ code --add-mcp '{"name":"vulnerability-scanner","type":"stdio","command":"npx","args":["-y","@guardbee/mcp-vulnerability-scanner"]}'Install GuardBee Vulnerability Scanner MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"vulnerability-scanner": {
"command": "npx",
"args": [
"-y",
"@guardbee/mcp-vulnerability-scanner"
]
}
}
}Install GuardBee Vulnerability Scanner MCP in Codex
$ codex mcp add vulnerability-scanner -- npx -y @guardbee/mcp-vulnerability-scannerInstall GuardBee Vulnerability Scanner MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.vulnerability-scanner] command = "npx" args = ["-y", "@guardbee/mcp-vulnerability-scanner"]
Install GuardBee Vulnerability Scanner MCP in Gemini CLI
$ gemini mcp add -s user vulnerability-scanner npx -- -y @guardbee/mcp-vulnerability-scannerInstall GuardBee Vulnerability Scanner MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"vulnerability-scanner": {
"command": "npx",
"args": [
"-y",
"@guardbee/mcp-vulnerability-scanner"
]
}
}
}GuardBee Vulnerability Scanner MCP tools 5
Detected from the READMEstart_scanget_scan_statuslist_scansget_findingsscan_and_report
| start_scan | — | |
| get_scan_status | — | |
| list_scans | — | |
| get_findings | — | |
| scan_and_report | — |
Configuration
GUARDBEE_API_KEY
| Name | Description | |
|---|---|---|
| GUARDBEE_API_KEY | — |
Automated checks
Ran Nov 12, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablePass
- Open source license (OSI)Pass
- Commit or release in the last yearPass
- Package name not close to a popular packagePass
- Remote endpoint uses HTTPSNot checked
- Destructive tools are labelledPass
- No hidden instructions to the modelPass
- No critical advisory in the package or its dependenciesPass
README
View on GitHub@guardbee/mcp-vulnerability-scanner
🇬🇧 English | 🇹🇷 Türkçe | 🇨🇳 中文 | 🇯🇵 日本語 | 🇰🇷 한국어 | 🇧🇷 Português | 🇪🇸 Español | 🇩🇪 Deutsch
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=1it sends the server, tool, success, duration and short parameter values such as a file path; longer strings and fields likecontent,tokenorpasswordare 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
npm install -g @guardbee/mcp-vulnerability-scanner
Add to claude_desktop_config.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
| Tool | Description |
|---|---|
start_scan |
Starts a scan for a URL or brand ID; with wait=true waits for completion |
get_scan_status |
Live status and summary counts by scan ID |
list_scans |
Lists workspace scans with filters |
get_findings |
Fetches findings filtered by severity / scanId / brandId |
scan_and_report |
Scan + 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
| Scenario | Description |
|---|---|
quick |
All 36 modules — comprehensive general scan |
kvkkFocus |
Focused on KVKK compliance modules |
gdprFocus |
Focused on GDPR compliance modules |
ccpaFocus |
Focused on CCPA compliance modules |
Environment Variables
| Variable | Description |
|---|---|
GUARDBEE_API_KEY |
GuardBee API key (required) |
GUARDBEE_BASE_URL |
Custom endpoint (default: https://app.guardbee.ai) |
Development
npm install
npm test # 25 unit tests
npm 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.
GuardBee Vulnerability Scanner MCP questions
How do I add GuardBee Vulnerability Scanner MCP to Claude Code?
Run claude mcp add vulnerability-scanner -- npx -y @guardbee/mcp-vulnerability-scanner in your terminal. Add --scope user to make it available in every project.
How do I add GuardBee Vulnerability Scanner MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does GuardBee Vulnerability Scanner MCP provide?
It exposes 5 tools, including start_scan, get_scan_status, list_scans, get_findings, scan_and_report.
Can I get help fixing the security issues found?
Yes, the tool provides explanations and actionable recommendations for every finding to assist with remediation.