Performs security audits including OWASP Top 10 scans, secret detection, dependency vulnerability checks, and network intelligence.
Also known as GuardBee/guardbee-mcp, @guardbee/security-suite
- Stars
- 2
- Tools
- —
- Downloads, 30 days
- 4,079
- Latest version
- 0.2.3
- Last commit
- Nov 12, 2026
- License
- MIT
What is GuardBee Security Suite MCP?
GuardBee Security Suite performs security audits including OWASP Top 10 scans, secret detection, dependency vulnerability checks, and network intelligence.
Summary generated from the project's README
About GuardBee Security Suite MCP server
Security-suite provides a comprehensive collection of security auditing tools designed for developers and security engineers. It functions as a single MCP server that can expose up to 129 different tools across 30 specialized packages. Users can choose to serve a recommended set of 31 tools or select specific groups like network, code, or supply-chain via command line arguments.
This server is used locally through an MCP client by running the command via npx. While many tools work locally on files and directories, certain platform-specific features like the security engineer or compliance checker require a GUARDBEE_API_KEY to access the GuardBee platform. The suite covers a wide range of vulnerabilities including OWASP Top 10 scans, secret detection in git history, dependency CVE checks, and network intelligence such as TLS and DNS inspections. It is built to integrate into development workflows, including GitHub Actions, to automate security checks during the build process.
What you can do with it
- 1Perform OWASP security auditsRun a single-pass scan over a codebase or a live server to receive an A–F grade based on OWASP MCP Top 10 standards.
- 2Detect leaked credentialsScan files, git history, and agent transcripts to find exposed API keys, tokens, or passwords.
- 3Audit supply chain risksCheck for known CVEs in npm and PyPI dependencies or identify hallucinated package names.
- 4Verify network security configurationsInspect TLS certificates, ciphers, and DNS records to ensure host security.
Written from the project's README. Every use case is checked against a quote from it.
How to install GuardBee Security Suite MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall GuardBee Security Suite MCP in Claude Code
$ claude mcp add security-suite -- npx -y @guardbee/security-suiteInstall GuardBee Security Suite MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"security-suite": {
"command": "npx",
"args": [
"-y",
"@guardbee/security-suite"
]
}
}
}Install GuardBee Security Suite MCP in VS Code
.vscode/mcp.json
{
"servers": {
"security-suite": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@guardbee/security-suite"
]
}
}
}Install GuardBee Security Suite MCP in VS Code CLI
$ code --add-mcp '{"name":"security-suite","type":"stdio","command":"npx","args":["-y","@guardbee/security-suite"]}'Install GuardBee Security Suite MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"security-suite": {
"command": "npx",
"args": [
"-y",
"@guardbee/security-suite"
]
}
}
}Install GuardBee Security Suite MCP in Codex
$ codex mcp add security-suite -- npx -y @guardbee/security-suiteInstall GuardBee Security Suite MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.security-suite] command = "npx" args = ["-y", "@guardbee/security-suite"]
Install GuardBee Security Suite MCP in Gemini CLI
$ gemini mcp add -s user security-suite npx -- -y @guardbee/security-suiteInstall GuardBee Security Suite MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"security-suite": {
"command": "npx",
"args": [
"-y",
"@guardbee/security-suite"
]
}
}
}Automated checks
Ran Nov 14, 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 reachableguardbee/guardbee-mcp is public and reachablegithub.com/guardbee/guardbee-mcp ↗Pass
- Package names this repository as its source@guardbee/security-suite names guardbee/guardbee-mcp as sourcenpmjs.com/package/@guardbee/security-suite ↗Pass
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-12github.com/guardbee/guardbee-mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from @guardbee/security-suitePass
- No critical advisory in the package or its dependencies105 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHub@guardbee/security-suite
🇬🇧 English | 🇹🇷 Türkçe | 🇨🇳 中文 | 🇯🇵 日本語 | 🇰🇷 한국어 | 🇧🇷 Português | 🇪🇸 Español | 🇩🇪 Deutsch
Every GuardBee MCP security tool from one install. guardbee serve is one MCP server with the tools of the packages you pick; guardbee <package> … runs any package's CLI. 30 packages, 129 MCP tools.
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.
Quick start
{
"mcpServers": {
"guardbee": {
"command": "npx",
"args": ["-y", "@guardbee/security-suite", "serve"]
}
}
}
That serves the recommended set (31 tools): a one-pass OWASP MCP Top 10 scan, secrets, prompt injection, toxic flows, MCP client configs and dependency CVEs. Pick others with --tools:
"args": ["-y", "@guardbee/security-suite", "serve", "--tools=recommended,network"]
--tools takes group names and package ids, comma-separated, or all (129 tools; some clients cap the number of tools, Cursor among them). GUARDBEE_SUITE_TOOLS does the same as an environment variable. Each tool's name starts with its package's prefix, so two packages' scan_text tools do not collide: secrets_scan_text, injection_scan_text. Names that already say it stay as they are (owasp_scan_path, inspect_ssl).
Groups
| Group | What it covers |
|---|---|
recommended (default) |
owasp-scan, secret-scanner, prompt-injection-scanner, toxic-flow-auditor, mcp-config-auditor, dependency-auditor |
code |
Static checks of source code, configs and content on disk |
supply-chain |
Dependencies, hallucinated packages, model files, MCP client configs, tool-definition drift |
network |
Checks that reach out to a host: TLS, DNS, vector stores, a live LLM |
platform |
Tools that call the GuardBee platform (need GUARDBEE_API_KEY) |
all |
Every package |
Packages
| Id | Tool prefix | Checks | Groups |
|---|---|---|---|
owasp-scan |
owasp_ |
OWASP MCP Top 10 in one pass over a codebase or a live server, A–F grade | recommended, code |
secret-scanner |
secrets_ |
API keys, tokens and passwords in files, git history and agent transcripts | recommended, code |
prompt-injection-scanner |
injection_ |
Prompt injection in documents, web pages and RAG content | recommended, code |
toxic-flow-auditor |
toxic_flow_ |
Lethal trifecta: untrusted input, sensitive data and egress in one agent | recommended, code |
mcp-config-auditor |
mcp_config_ |
MCP client configs (Cursor, Claude, Windsurf, VS Code) and shadow servers | recommended, supply-chain |
dependency-auditor |
deps_ |
Known CVEs in npm and PyPI dependencies (OSV) | recommended, supply-chain |
prompt-leak-scanner |
leak_ |
Credentials and PII in outbound LLM prompts, before they leave your app | code |
tool-poisoning-scanner |
poisoning_ |
Hidden instructions in MCP tool descriptions and schemas | code |
mcp-server-auditor |
server_audit_ |
Shell, eval, SSRF and secrets in an MCP server's source | code |
oauth-auditor |
oauth_ |
OAuth 2.1 mistakes in an MCP server's auth code: token passthrough, audience, PKCE | code |
audit-gap-auditor |
audit_gap_ |
Tool calls without an audit trail (OWASP MCP08) | code |
context-oversharing-auditor |
oversharing_ |
Context oversharing (MCP10): session dumps, cross-user context, unscoped recalls | code |
ai-code-scanner |
ai_code_ |
Insecure LLM integrations: exposed keys, unsafe model output, PII to third-party LLMs | code |
agent-graph-auditor |
agent_graph_ |
Transitive excessive agency across LangGraph, CrewAI and AutoGen agents | code |
a2a-auditor |
a2a_ |
Agent2Agent (A2A) implementation code: webhook SSRF, unauthenticated Agent Cards | code |
elicitation-auditor |
elicitation_ |
MCP elicitation that asks users for secrets or sends them to third parties | code |
memory-poisoning-scanner |
memory_ |
Untrusted input written into persistent agent memory | code |
unbounded-consumption-auditor |
consumption_ |
Denial of wallet: missing token limits, timeouts and loop bounds | code |
threat-rules |
threat_rules_ |
Agent Threat Rules (ATR) on text, files and agent events | code |
document-scanner |
document_ |
PII and credentials in PDFs and images (OCR) before they reach an LLM | code |
reverse-shield |
reverse_ |
How easily a shipped app can be reverse engineered (web, Electron, APK/AAB, IPA, Unity, native); fix diffs, CI baselines | code |
slopsquat-scanner |
slopsquat_ |
Hallucinated or brand-new package names (slopsquatting) | supply-chain |
model-scanner |
model_ |
Malicious pickle, joblib, NumPy, safetensors, Keras, ONNX, GGUF and TensorFlow model files, and Hugging Face repos | supply-chain |
rug-pull-detector |
rug_pull_ |
MCP tool definitions that change after you approved them | supply-chain |
ssl-inspector |
ssl_ |
TLS certificates, ciphers and HSTS | network |
dns-intelligence |
dns_ |
DNS records, SPF/DMARC/DKIM, subdomain takeover | network |
vector-store-scanner |
vector_store_ |
Unauthenticated vector databases (Weaviate, Qdrant, Chroma, pgvector…) | network |
llm-redteam |
redteam_ |
Jailbreak and extraction probes against an LLM endpoint you control | network |
vulnerability-scanner |
vuln_ |
GuardBee platform security scans and their findings | platform |
compliance-checker |
compliance_ |
KVKK, GDPR and CCPA compliance of a website via the GuardBee API | platform |
security-engineer |
engineer_ |
Fix GuardBee AI Security Engineer findings in your repo and verify the fixes (GUARDBEE_API_KEY) |
platform |
guardbee list prints this table. The proxy (mcp-security-proxy) and the database gateway (mcp-db-gateway) are not in the suite: they sit in front of other servers rather than answering tool calls.
CLI
npm install -g @guardbee/security-suite
guardbee list # packages and groups
guardbee owasp-scan scan . --fail-on=high --format=sarif > owasp.sarif
guardbee secret-scanner scan . --history # any package's CLI, same arguments
guardbee mcp-config-auditor discover
The shortcuts from earlier versions still work:
| Shortcut | Runs |
|---|---|
guardbee secret-scan <path> |
secret-scanner scan |
guardbee dep-audit <dir> |
dependency-auditor audit |
guardbee ssl-inspect <domain>… |
ssl-inspector inspect |
guardbee dns-check <domain> |
dns-intelligence check |
GitHub Actions
- run: npx -y @guardbee/security-suite owasp-scan scan . --format=sarif --fail-on=high > owasp.sarif
- run: npx -y @guardbee/security-suite dep-audit . --fail-on=high
- uses: github/codeql-action/upload-sarif@v3
if: always()
with:
sarif_file: owasp.sarif
Upgrading from 0.2
guardbee serve used to expose five tools from four packages with plain names (scan_directory, scan_file, audit_dependencies, inspect_ssl, check_dns). It now serves the recommended group with prefixed names: the same checks are secrets_scan_directory, secrets_scan_file, deps_audit_directory, and, with --tools=recommended,network, inspect_ssl and enumerate_dns / dns_check_email_security. Agents that call tools by name need the new names.
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 Security Suite MCP questions
How do I add GuardBee Security Suite MCP to Claude Code?
Run claude mcp add security-suite -- npx -y @guardbee/security-suite in your terminal. Add --scope user to make it available in every project.
How do I add GuardBee Security Suite 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 are included in the default installation?
The default recommended set includes 31 tools covering OWASP MCP Top 10 scans, secrets, prompt injection, toxic flows, MCP client configs, and dependency CVEs.
Is telemetry enabled by default?
No, telemetry is turned off by default.
Do I need an API key for all tools?
No, an API key is only required for tools that call the GuardBee platform, such as the security engineer or compliance checker.