
Security Suite
io.github.GuardBeePublished by GitHub account GuardBeev0.7.4Updated Nov 7, 2026
Every GuardBee MCP security tool in one server: OWASP MCP Top 10, secrets, supply chain, TLS/DNS
Overview
GuardBee Security Suite bundles 30 security packages (129 tools) into one MCP server for scanning code, configs, dependencies, models and network endpoints.
- What you can do
- Scan code and content for OWASP MCP Top 10 issues, secrets, prompt injection, tool poisoning, OAuth mistakes and PII
- Audit supply chain: dependency CVEs, hallucinated packages, malicious model files, MCP client configs and tool-definition drift
- Check network targets: TLS certificates, DNS and email records, unauthenticated vector stores, LLM red-team probes
- Run GuardBee platform scans and KVKK/GDPR/CCPA compliance checks when an API key is configured
- Choose which tool groups are served via the tools option or an environment variable
- When to use it
- Useful when you want an assistant to run security reviews of an MCP server, agent codebase or dependency set, or to check TLS, DNS and exposed services, without installing each GuardBee package separately.
- Requirements
- Runs locally over stdio, typically via npx with the serve argument. Node.js and npm are needed. The platform group (vulnerability scans, compliance checks) requires the GUARDBEE_API_KEY environment variable; other groups do not declare credentials. Network access is needed for the network group and for OSV dependency lookups.
Installation
In SourceWeft
- Open Security Suite in the dashboard and add it to a workspace.
- 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/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=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
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:
--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
Packages
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
The shortcuts from earlier versions still work:
GitHub Actions
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.
Source: packages/security-suite/README.md at commit b3f6bda
Tools
0Version history
14- v0.7.4LatestNov 7, 2026
- v0.7.3Nov 3, 2026
- v0.7.2Nov 1, 2026
- v0.7.1Oct 31, 2026
- v0.7.0Oct 30, 2026
- v0.5.1Oct 29, 2026
- v0.4.1Oct 22, 2026
- v0.4.0Oct 22, 2026
- v0.2.19Oct 14, 2026
- v0.2.18Oct 14, 2026
- v0.2.14Oct 13, 2026
- v0.2.11Oct 13, 2026
- v0.2.7Oct 11, 2026
- v0.2.4Oct 9, 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