mcp-registry/io.github.pipeworx-io/osv/query_package_vulns / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/osv/query_package_vulns

The best live alternatives to mcp-registry/io.github.pipeworx-io/osv/query_package_vulns right now are mcp-registry/dev.depscope/mcp/get_vulnerabilities, mcp-registry/io.github.megabrainee/sectora/assess_dependency, mcp-registry/com.datanexusmcp/mcp-server/security_fetch_package_vulnerabilities, mcp-registry/io.github.helphub369/utility-matrix/known-vulnerability-checker, mcp-registry/io.github.traveljamboree/agentsec-mcp/cve_lookup — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/osv/query_package_vulns itself is currently "healthy".

alternative	server
mcp-registry/dev.depscope/mcp/get_vulnerabilities	dev.depscope/mcp	live status →
mcp-registry/io.github.megabrainee/sectora/assess_dependency	io.github.megabrainee/sectora	live status →
mcp-registry/com.datanexusmcp/mcp-server/security_fetch_package_vulnerabilities	com.datanexusmcp/mcp-server	live status →
mcp-registry/io.github.helphub369/utility-matrix/known-vulnerability-checker	io.github.helphub369/utility-matrix	live status →
mcp-registry/io.github.traveljamboree/agentsec-mcp/cve_lookup	io.github.traveljamboree/agentsec-mcp	live status →
mcp-registry/com.contrastcyber/api/exploit_lookup	com.contrastcyber/api	live status →
mcp-registry/io.github.fetter-io/fetter-mcp/is_vulnerable	io.github.fetter-io/fetter-mcp	live status →
mcp-registry/ai.dynamicfeed/dynamic-feed/check_vulnerability	ai.dynamicfeed/dynamic-feed	live status →
mcp-registry/io.github.fetter-io/fetter-mcp/lookup	io.github.fetter-io/fetter-mcp	live status →
mcp-registry/io.github.getgapup/mcp-knowledge/cve_security_lookup	io.github.getgapup/mcp-knowledge	live status →
mcp-registry/io.github.getgapup/gapup-mcp/cve_security_lookup	io.github.getgapup/gapup-mcp	live status →
mcp-registry/com.contrastcyber/api/check_dependencies	com.contrastcyber/api	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/osv/query_package_vulns?

mcp-registry/dev.depscope/mcp/get_vulnerabilities is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.megabrainee/sectora/assess_dependency, mcp-registry/com.datanexusmcp/mcp-server/security_fetch_package_vulnerabilities, mcp-registry/io.github.helphub369/utility-matrix/known-vulnerability-checker, mcp-registry/io.github.traveljamboree/agentsec-mcp/cve_lookup. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/osv/query_package_vulns down right now?

mcp-registry/io.github.pipeworx-io/osv/query_package_vulns's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fosv%2Fquery_package_vulns.

How does Glimind pick alternatives?

By semantic capability match (what the tool does) filtered to tools that are healthy right now — from cross-ecosystem real usage. Neutral: Glimind sells no tools.

For agents

Get a live, capability-matched substitute in one call: GET https://glimind.com/v1/alternatives/mcp-registry%2Fio.github.pipeworx-io%2Fosv%2Fquery_package_vulns or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/osv/query_package_vulns's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/osv/query_package_vulns.