Vulnfeed MCP vs Vet — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Vulnfeed MCP vs Vet
In-depth architectural comparison of the Vulnfeed MCP and Vet MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Vulnfeed MCP
Security · Local stdio
Quality: 56/100 (Good) | Auth: API Key required
Vet
Security · Local stdio
Quality: 53/100 (Good) | Auth: API Key required
Verdict Summary: Choose Vulnfeed MCP if you need specialized Security tools running via a local process. Choose Vet if your workspace requires Security integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Vulnfeed MCP when:
You need dedicated capabilities in the Security domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Freemium).
You have access to required keys: VULNFEED_API_KEY.
Dependency vulnerability scanner with EPSS exploit probability scoring. Scans lockfiles (npm, pip, Go, Cargo, Ruby, Composer, Gradle, NuGet, Mix), prioritizes by real-world exploit likelihood, recommends fix versions. 9 MCP tools for scanning, monitoring, and alerting. Free tier + x402 micropayments. pip install vulnfeed-mcp
vet-mcp checks open source packages—like those suggested by AI coding tools—for vulnerabilities and malicious code. It supports npm and PyPI, and runs locally via Docker or as a standalone binary for fast, automated vetting.
Category & Scope
Tools & Capabilities Breakdown
Vulnfeed MCP Tools (9)
scan_project
Auto-detect and scan all lockfiles in a directory
scan_lockfile
Scan a specific lockfile
check_package
Check a single package for vulnerabilities
lookup_cve
Detailed CVE info with EPSS + fix versions
monitor_project
Register for continuous monitoring
check_alerts
New vulns since last scan
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Vulnfeed MCP is categorized under Security and uses a local stdio subprocess. In contrast, Vet belongs to Security using local stdio subprocess. Select Vulnfeed MCP when you need capabilities focused on security and Vet when you require tools for security.