
Security Suite
io.github.4hmetuyarPublished by GitHub account 4hmetuyarv0.2.3Updated Nov 10, 2026
Bundle of secret-scanner, dependency-auditor, ssl-inspector, and dns-intelligence
Overview
GuardBee Security Suite bundles secret, dependency, TLS, DNS and AI-agent security scanners into one local MCP server and CLI.
- What you can do
- Scan code and content for secrets, prompt injection, tool poisoning, PII and OWASP MCP Top 10 issues
- Audit dependencies for CVEs, hallucinated packages, model files and MCP client configs
- Inspect hosts over the network: TLS certificates, DNS and email records, exposed vector stores
- Run jailbreak probes against an LLM endpoint you control
- Call GuardBee platform scans, compliance checks and fix suggestions when an API key is set
- Run the same checks from a CLI with SARIF output for CI pipelines
- When to use it
- Useful when you want an assistant to audit a codebase, MCP server or agent setup for security problems, or to check a domain's TLS, DNS and email configuration, without wiring up several separate scanners.
- Requirements
- Runs locally over stdio via npx from the npm package @guardbee/security-suite. No credentials are needed for the default recommended tool set; the platform group (vulnerability scans, compliance checks, security engineer fixes) requires the GUARDBEE_API_KEY environment variable. Network access is needed for the network and supply-chain checks.
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 462e3cb
Tools
0Version history
1- v0.2.3LatestSep 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