VulnForge MCP
# VulnForge MCP (`vulnforge-mcp`)
> 🏛️ **Official Organization Transfer Notice**
> This project has been officially transferred to the **[KRC Labs](https://github.com/KRC-Labs)** engineering organization.
> All active runtime engineering, public releases, and technical documentation are maintained under KRC Labs.
---
### 🔗 Official Resources & Portal (공식 링크 및 리소스)
- 🏛️ **Organization (공식 조직)**: [https://github.com/KRC-Labs](https://github.com/KRC-Labs)
- 🌐 **Interactive Systems Showcase (실시간 시스템 쇼케이스)**: [https://krc-labs.github.io/](https://krc-labs.github.io/)
- 📊 **Status & Release Hub (시스템 현황 & 변경 로그)**: [https://github.com/KRC-Labs/status](https://github.com/KRC-Labs/status)
---
<details open>
<summary><b>🌐 Multi-Language Official Notice (10 Languages / 10개국어 지원 안내)</b></summary>
<br>
| Flag / Language | Official Migration Notice (1:1 Translation) |
| :---: | :--- |
| 🇺🇸 **English** | This project has been officially transferred to **[KRC Labs](https://github.com/KRC-Labs)**. All active runtimes and documentation are maintained under KRC Labs. |
| 🇰🇷 **한국어** | 이 프로젝트는 공식 엔지니어링 조직인 **[KRC Labs](https://github.com/KRC-Labs)**로 정식 이관되었습니다. 모든 시스템 런타임 및 기술 문서는 KRC Labs에서 통합 관리됩니다. |
| 🇯🇵 **日本語** | 本プロジェクトは公式エンジニアリング組織 **[KRC Labs](https://github.com/KRC-Labs)** へ正式移管されました。すべてのランタイム開発および技術文書は KRC Labs にて管理されます。 |
| 🇨🇳 **简体中文** | 本项目已正式迁移至官方工程组织 **[KRC Labs](https://github.com/KRC-Labs)**。所有活跃的运行时工程与技术文档均由 KRC Labs 统一维护。 |
| 🇩🇪 **Deutsch** | Dieses Projekt wurde offiziell an **[KRC Labs](https://github.com/KRC-Labs)** übertragen. Sämtliche Laufzeitentwicklungen und Dokumentationen werden von KRC Labs verwaltet. |
| 🇫🇷 **Français** | Ce projet a été officiellement transféré à l'organisation d'ingénierie **[KRC Labs](https://github.com/KRC-Labs)**. L'ensemble des runtimes et de la documentation est géré par KRC Labs. |
| 🇪🇸 **Español** | Este proyecto ha sido transferido oficialmente a **[KRC Labs](https://github.com/KRC-Labs)**. Toda la ingeniería de ejecución activa y la documentación técnica se gestionan en KRC Labs. |
| 🇷🇺 **Русский** | Данный проект официально передан инженерной организации **[KRC Labs](https://github.com/KRC-Labs)**. Вся разработка и техническая документация поддерживаются в KRC Labs. |
| 🇮🇳 **हिन्दी** | यह प्रोजेक्ट आधिकारिक रूप से **[KRC Labs](https://github.com/KRC-Labs)** को स्थानांतरित कर दिया गया है। सभी रनटाइम और तकनीकी दस्तावेज़ KRC Labs द्वारा प्रबंधित किए जाते हैं। |
| 🇵🇹 **Português** | Este projeto foi oficialmente transferido para a **[KRC Labs](https://github.com/KRC-Labs)**. Todo o desenvolvimento ativo e a documentação técnica são mantidos pela KRC Labs. |
</details>
---
<sub>© KRC Labs. All rights reserved.</sub>
TDQS
Scored across 24 tools
Most tools target distinct security domains, but several clusters overlap heavily: audit_sbom, audit_cosign, audit_intoto, audit_model_supply_chain, and audit_p2p_gossip all cover supply-chain/attestation concerns, while audit_ebpf, audit_wasm_ebpf, audit_microsegmentation, and fuzz_wasm_runtime overlap runtime/kernel surfaces. Descriptions do help differentiate them, but an agent could still misselect when asked for a broad layer such as 'supply chain audit'. The presence of full_scan alongside granular audits adds another selection ambiguity.
Almost all tools use a consistent vulnforge_ prefix with snake_case verb/noun patterns such as audit_*, fuzz_*, inject_patch, and verify_patch. The only minor deviations are full_scan lacking the audit/fuzz verb style and some names combining multiple nouns, but the convention remains predictable overall.
Twenty-four tools is heavy for a single server and likely reflects a very broad security audit suite rather than a tightly scoped toolset. Most tools do earn their place by covering distinct security domains, but the count is borderline excessive and increases selection burden.
The surface covers a wide audit lifecycle: domain-specific audits, fuzzing, patch injection, patch verification, and an end-to-end full scan. Minor gaps exist around reporting/export, triage workflows, and general result management, but agents can work around these for most audit workflows.