Melakukan audit keamanan termasuk pemindaian OWASP Top 10, deteksi secret, pemeriksaan kerentanan dependency, dan intelijen jaringan.
Juga dikenal sebagai GuardBee/guardbee-mcp, @guardbee/security-suite
- Stars
- 2
- Tools
- —
- Unduhan, 30 hari
- 4.079
- Versi terbaru
- 0.2.3
- Commit terakhir
- 12 Nov 2026
- Lisensi
- MIT
Apa itu GuardBee Security Suite MCP?
Melakukan audit keamanan termasuk pemindaian OWASP Top 10, deteksi secret, pemeriksaan kerentanan dependency, dan intelijen jaringan.
Ringkasan dibuat dari README proyek
Tentang GuardBee Security Suite MCP server
Security-suite menyediakan koleksi lengkap tool audit keamanan yang dirancang untuk developer dan security engineer. Tool ini berfungsi sebagai satu MCP server yang dapat mengekspos hingga 129 tool berbeda melalui 30 package khusus. Anda dapat memilih untuk menjalankan set rekomendasi berisi 31 tool atau memilih grup spesifik seperti network, code, atau supply-chain melalui argumen command line.
Server ini digunakan secara lokal melalui MCP client dengan menjalankan command via npx. Meskipun banyak tool yang bekerja secara lokal pada file dan direktori, fitur spesifik platform tertentu seperti security engineer atau compliance checker memerlukan GUARDBEE_API_KEY untuk mengakses platform GuardBee. Suite ini mencakup berbagai macam kerentanan termasuk pemindaian OWASP Top 10, deteksi secret dalam git history, pemeriksaan CVE pada dependency, serta intelijen jaringan seperti inspeksi TLS dan DNS. Suite ini dibangun untuk terintegrasi ke dalam workflow pengembangan, termasuk GitHub Actions, guna mengotomatisasi pengecekan keamanan selama proses build.
Apa yang bisa Anda lakukan dengannya
- 1Melakukan audit keamanan OWASPJalankan pemindaian satu kali pada codebase atau server live untuk mendapatkan grade A–F berdasarkan standar OWASP MCP Top 10.
- 2Mendeteksi kebocoran kredensialPindai file, git history, dan transkrip agent untuk menemukan API key, token, atau password yang terekspos.
- 3Audit risiko supply chainPeriksa CVE yang diketahui pada dependency npm dan PyPI atau identifikasi nama package yang terhalusinasi.
- 4Verifikasi konfigurasi keamanan jaringanInspeksi sertifikat TLS, cipher, dan record DNS untuk memastikan keamanan host.
Ditulis berdasarkan README proyek. Setiap use case diperiksa terhadap kutipan dari README tersebut.
Cara menginstal GuardBee Security Suite MCP
Format diverifikasi 10 Nov 2026Tambahkan ke CursorTambahkan ke GooseInstal GuardBee Security Suite MCP di Claude Code
$ claude mcp add security-suite -- npx -y @guardbee/security-suiteInstal GuardBee Security Suite MCP di Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"security-suite": {
"command": "npx",
"args": [
"-y",
"@guardbee/security-suite"
]
}
}
}Instal GuardBee Security Suite MCP di VS Code
.vscode/mcp.json
{
"servers": {
"security-suite": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@guardbee/security-suite"
]
}
}
}Instal GuardBee Security Suite MCP di VS Code CLI
$ code --add-mcp '{"name":"security-suite","type":"stdio","command":"npx","args":["-y","@guardbee/security-suite"]}'Instal GuardBee Security Suite MCP di Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"security-suite": {
"command": "npx",
"args": [
"-y",
"@guardbee/security-suite"
]
}
}
}Instal GuardBee Security Suite MCP di Codex
$ codex mcp add security-suite -- npx -y @guardbee/security-suiteInstal GuardBee Security Suite MCP di Codex config.toml
~/.codex/config.toml
[mcp_servers.security-suite] command = "npx" args = ["-y", "@guardbee/security-suite"]
Instal GuardBee Security Suite MCP di Gemini CLI
$ gemini mcp add -s user security-suite npx -- -y @guardbee/security-suiteInstal GuardBee Security Suite MCP di Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"security-suite": {
"command": "npx",
"args": [
"-y",
"@guardbee/security-suite"
]
}
}
}Pengecekan otomatis
Berjalan 14 Nov 2026Laporan lengkap →Lolos checks otomatis kami. Ini bukan audit keamanan: baca kodenya dan berikan server akses paling terbatas yang dibutuhkannya. Cara kerja checks
- Source repository terhubung dan dapat dijangkauguardbee/guardbee-mcp is public and reachablegithub.com/guardbee/guardbee-mcp ↗Lolos
- Nama paket mencantumkan repositori ini sebagai sumbernya@guardbee/security-suite names guardbee/guardbee-mcp as sourcenpmjs.com/package/@guardbee/security-suite ↗Lolos
- Provenance build (atestasi Sigstore)No build attestation published for this releaseTidak diperiksa
- Lisensi open source (OSI)MITspdx.org/licenses/MIT.html ↗Lolos
- Ada commit atau release dalam satu tahun terakhirLast commit or release 2026-11-12github.com/guardbee/guardbee-mcp ↗Lolos
- OpenSSF ScorecardTidak diperiksa
- Nama package tidak mirip dengan package populerNo popular package one edit away from @guardbee/security-suiteLolos
- Tidak ada advisory kritis pada paket atau dependensinya105 resolved dependencies checked; no critical advisoryosv.dev ↗Lolos
- Tidak ada instruksi tersembunyi untuk model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersLolos
- Tools yang bersifat destruktif telah diberi labelTidak diperiksa
- Endpoint remote merespons handshake MCPTidak diperiksa
README
Lihat di 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.
Pertanyaan tentang GuardBee Security Suite MCP
Bagaimana cara menambahkan GuardBee Security Suite MCP ke Claude Code?
Jalankan claude mcp add security-suite -- npx -y @guardbee/security-suite di terminal Anda. Tambahkan --scope user agar tersedia di semua proyek.
Bagaimana cara menambahkan GuardBee Security Suite MCP ke Cursor?
Buka ~/.cursor/mcp.json dan tambahkan server di bawah mcpServers, menggunakan config Cursor yang ditunjukkan di bagian instalasi di atas.
Apa saja tool yang disertakan dalam instalasi default?
Set rekomendasi default mencakup 31 tool yang mencakup pemindaian OWASP MCP Top 10, secrets, prompt injection, toxic flows, config MCP client, dan CVE pada dependency.
Apakah telemetry diaktifkan secara default?
Tidak, telemetry dinonaktifkan secara default.
Apakah saya memerlukan API key untuk semua tool?
Tidak, API key hanya diperlukan untuk tool yang memanggil platform GuardBee, seperti security engineer atau compliance checker.