Security Suite

io.github.GuardBee由 GitHub 账号 GuardBee 发布v0.7.4更新于 Nov 7, 2026

Every GuardBee MCP security tool in one server: OWASP MCP Top 10, secrets, supply chain, TLS/DNS

概览

AI 生成的概览

GuardBee Security Suite 把 30 个安全工具包(129 个工具)整合为一个 MCP 服务器,用于扫描代码、配置、依赖、模型和网络端点。

可以做什么
  • 扫描代码与内容中的 OWASP MCP Top 10 问题、密钥、提示注入、工具投毒、OAuth 错误和 PII
  • 审计供应链:依赖 CVE、虚构包名、恶意模型文件、MCP 客户端配置和工具定义漂移
  • 检查网络目标:TLS 证书、DNS 与邮件记录、未认证的向量数据库、LLM 红队探测
  • 配置 API 密钥后可运行 GuardBee 平台扫描和 KVKK/GDPR/CCPA 合规检查
  • 通过 tools 选项或环境变量选择要提供的工具组
适用场景
适合让助手对 MCP 服务器、智能体代码库或依赖集合做安全审查,或检查 TLS、DNS 与暴露服务,而无需逐个安装 GuardBee 工具包。
运行要求
以 stdio 在本地运行,通常通过 npx 加 serve 参数启动,需要 Node.js 和 npm。platform 组(漏洞扫描、合规检查)需要环境变量 GUARDBEE_API_KEY;其他组未声明凭据。network 组和 OSV 依赖查询需要网络访问。
安装前请注意
network 组会主动连接你指定的主机,红队包会向你控制的 LLM 端点发送探测。platform 组会把数据发送到 GuardBee API,并需要 GUARDBEE_API_KEY。遥测默认关闭;设置 GUARDBEE_TELEMETRY=1 后会发送工具名、成功与否、耗时以及文件路径等短参数值。一次提供全部 129 个工具可能超出部分客户端的工具数量上限。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Security Suite,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

@guardbee/security-suite

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

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

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=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.

Quick start

json
{  "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:

json
"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

GroupWhat it covers
recommended (default)owasp-scan, secret-scanner, prompt-injection-scanner, toxic-flow-auditor, mcp-config-auditor, dependency-auditor
codeStatic checks of source code, configs and content on disk
supply-chainDependencies, hallucinated packages, model files, MCP client configs, tool-definition drift
networkChecks that reach out to a host: TLS, DNS, vector stores, a live LLM
platformTools that call the GuardBee platform (need GUARDBEE_API_KEY)
allEvery package

Packages

IdTool prefixChecksGroups
owasp-scanowasp_OWASP MCP Top 10 in one pass over a codebase or a live server, A–F graderecommended, code
secret-scannersecrets_API keys, tokens and passwords in files, git history and agent transcriptsrecommended, code
prompt-injection-scannerinjection_Prompt injection in documents, web pages and RAG contentrecommended, code
toxic-flow-auditortoxic_flow_Lethal trifecta: untrusted input, sensitive data and egress in one agentrecommended, code
mcp-config-auditormcp_config_MCP client configs (Cursor, Claude, Windsurf, VS Code) and shadow serversrecommended, supply-chain
dependency-auditordeps_Known CVEs in npm and PyPI dependencies (OSV)recommended, supply-chain
prompt-leak-scannerleak_Credentials and PII in outbound LLM prompts, before they leave your appcode
tool-poisoning-scannerpoisoning_Hidden instructions in MCP tool descriptions and schemascode
mcp-server-auditorserver_audit_Shell, eval, SSRF and secrets in an MCP server's sourcecode
oauth-auditoroauth_OAuth 2.1 mistakes in an MCP server's auth code: token passthrough, audience, PKCEcode
audit-gap-auditoraudit_gap_Tool calls without an audit trail (OWASP MCP08)code
context-oversharing-auditoroversharing_Context oversharing (MCP10): session dumps, cross-user context, unscoped recallscode
ai-code-scannerai_code_Insecure LLM integrations: exposed keys, unsafe model output, PII to third-party LLMscode
agent-graph-auditoragent_graph_Transitive excessive agency across LangGraph, CrewAI and AutoGen agentscode
a2a-auditora2a_Agent2Agent (A2A) implementation code: webhook SSRF, unauthenticated Agent Cardscode
elicitation-auditorelicitation_MCP elicitation that asks users for secrets or sends them to third partiescode
memory-poisoning-scannermemory_Untrusted input written into persistent agent memorycode
unbounded-consumption-auditorconsumption_Denial of wallet: missing token limits, timeouts and loop boundscode
threat-rulesthreat_rules_Agent Threat Rules (ATR) on text, files and agent eventscode
document-scannerdocument_PII and credentials in PDFs and images (OCR) before they reach an LLMcode
reverse-shieldreverse_How easily a shipped app can be reverse engineered (web, Electron, APK/AAB, IPA, Unity, native); fix diffs, CI baselinescode
slopsquat-scannerslopsquat_Hallucinated or brand-new package names (slopsquatting)supply-chain
model-scannermodel_Malicious pickle, joblib, NumPy, safetensors, Keras, ONNX, GGUF and TensorFlow model files, and Hugging Face repossupply-chain
rug-pull-detectorrug_pull_MCP tool definitions that change after you approved themsupply-chain
ssl-inspectorssl_TLS certificates, ciphers and HSTSnetwork
dns-intelligencedns_DNS records, SPF/DMARC/DKIM, subdomain takeovernetwork
vector-store-scannervector_store_Unauthenticated vector databases (Weaviate, Qdrant, Chroma, pgvector…)network
llm-redteamredteam_Jailbreak and extraction probes against an LLM endpoint you controlnetwork
vulnerability-scannervuln_GuardBee platform security scans and their findingsplatform
compliance-checkercompliance_KVKK, GDPR and CCPA compliance of a website via the GuardBee APIplatform

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

bash
npm install -g @guardbee/security-suite
guardbee list                                         # packages and groupsguardbee owasp-scan scan . --fail-on=high --format=sarif > owasp.sarifguardbee secret-scanner scan . --history              # any package's CLI, same argumentsguardbee mcp-config-auditor discover

The shortcuts from earlier versions still work:

ShortcutRuns
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

yaml
- 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.

来源:packages/security-suite/README.md,提交 b3f6bda

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

14
  1. v0.7.4最新Nov 7, 2026
  2. v0.7.3Nov 3, 2026
  3. v0.7.2Nov 1, 2026
  4. v0.7.1Oct 31, 2026
  5. v0.7.0Oct 30, 2026
  6. v0.5.1Oct 29, 2026
  7. v0.4.1Oct 22, 2026
  8. v0.4.0Oct 22, 2026
  9. v0.2.19Oct 14, 2026
  10. v0.2.18Oct 14, 2026
  11. v0.2.14Oct 13, 2026
  12. v0.2.11Oct 13, 2026
  13. v0.2.7Oct 11, 2026
  14. v0.2.4Oct 9, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分