VulnForge MCP
Related Servers
Alternatives to VulnForge MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI editors such as Cursor, Claude Code, Windsurf and VS Code to scan a project for common AI-introduced security mistakes — leaked keys, open Supabase/Firebase data, missing auth, unverified Stripe webhooks, SQL injection and more — and return findings with exact fix instructions. It also provides a guided prompt that walks an agent through fixing critical issues one by one and verifying each fix by re-scanning, without ever editing files or rotating keys itself.2MIT
- AlicenseNot gradedqualityDmaintenanceAutomatically detects security vulnerabilities in AI-generated code, scanning for hardcoded secrets, injection flaws, XSS, weak cryptography, authentication issues, path traversal, and vulnerable dependencies across JavaScript, Python, Java, and Go.14 npm2MIT

shipsafe-mcpofficial
AlicenseAqualityCmaintenanceEnables AI coding assistants to scan projects for security issues such as leaked API keys, missing Supabase RLS, open Firebase rules, unauthenticated routes, and hallucinated packages, then fix and verify the results.81MIT- AlicenseNot gradedqualityBmaintenanceEnables AI agents and IDE assistants to run zero-config security audits, detect secrets and vulnerable dependencies, and apply adversarial verification to reduce false positives.14 npm2MIT
- AlicenseAqualityDmaintenanceAn AI-powered security audit tool that analyzes codebases for vulnerabilities using real-time data from MITRE CWE and npm audit. It enables deep analysis of authentication, API security, and dependencies to provide structured findings and remediation steps.2115 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to scan a repository or project for malware, supply-chain attacks, leaked secrets, and web, server, cloud, and CI/CD vulnerabilities, then confirm real findings with concrete attack scenarios and fixes. Exposes scan, guide, and reference tools plus a security-review prompt that runs locally.1MIT
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.