Vulnfeed Mcp vs Osv Ui — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Vulnfeed Mcp vs Osv Ui
In-depth architectural comparison of the Vulnfeed Mcp and Osv Ui 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: 57/100 (Good) | Auth: API Key required
Osv Ui
Security · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
Verdict Summary: Choose Vulnfeed Mcp if you need specialized Security tools running via a local process. Choose Osv Ui 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
Visual CVE audit dashboard for npm, Python, Go, and Rust. Scan from Claude/Cursor, opens a browser UI for human review (human-in-the-loop), applies fixes with explicit confirmation. Powered by OSV.dev.
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, Osv Ui belongs to Security using local stdio subprocess. Select Vulnfeed Mcp when you need capabilities focused on security and Osv Ui when you require tools for security.
Scan a project directory for CVE vulnerabilities. Automatically detects npm, Python, Go, Rust, Java/Maven, PHP/Composer, and Ruby/Bundler manifests. Queries live CVE data from OSV.dev. Returns structured vulnerability report with severity counts, risk score, and fix recommendations. Use this as the first step before open_dashboard or apply_fixes.
open_dashboard
Launch the osv-ui visual dashboard in the browser for human review. This is the HUMAN-IN-THE-LOOP step — always offer this before applying fixes. The dashboard shows full CVE details, severity charts, and the upgrade guide. Returns the dashboard URL. If already running for this path, returns existing URL.
get_fix_commands
Get the safe upgrade commands for vulnerable packages WITHOUT executing them. Use this to show the user what will be changed before calling apply_fixes. Returns a list of commands grouped by ecosystem (npm, pip, go, cargo, Maven, Composer, Bundler).
apply_fixes
Execute package upgrade commands to fix CVEs. IMPORTANT: This is a DESTRUCTIVE action that modifies package files. ALWAYS call get_fix_commands first and confirm with the user before calling this. Returns the command output for each fix applied.