mcp-registry/com.datanexusmcp/mcp-server/security_fetch_package_vulnerabilities / alternatives
mcp-registry/com.datanexusmcp/mcp-server/security_fetch_package_vulnerabilitiesThe best live alternatives to mcp-registry/com.datanexusmcp/mcp-server/security_fetch_package_vulnerabilities right now are mcp-registry/dev.depscope/mcp/get_vulnerabilities, mcp-registry/io.github.pipeworx-io/osv/query_batch, mcp-registry/io.github.megabrainee/sectora/assess_dependency, mcp-registry/io.github.pipeworx-io/osv/query_package_vulns, mcp-registry/io.github.fetter-io/fetter-mcp/is_vulnerable — capability-matched and ranked by current reliability. mcp-registry/com.datanexusmcp/mcp-server/security_fetch_package_vulnerabilities itself is currently "healthy".
mcp-registry/dev.depscope/mcp/get_vulnerabilities is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/osv/query_batch, mcp-registry/io.github.megabrainee/sectora/assess_dependency, mcp-registry/io.github.pipeworx-io/osv/query_package_vulns, mcp-registry/io.github.fetter-io/fetter-mcp/is_vulnerable. Glimind ranks alternatives by semantic similarity and live health.
mcp-registry/com.datanexusmcp/mcp-server/security_fetch_package_vulnerabilities's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fcom.datanexusmcp%2Fmcp-server%2Fsecurity_fetch_package_vulnerabilities.
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.
Get a live, capability-matched substitute in one call: GET https://glimind.com/v1/alternatives/mcp-registry%2Fcom.datanexusmcp%2Fmcp-server%2Fsecurity_fetch_package_vulnerabilities
or MCP find_alternatives. Check mcp-registry/com.datanexusmcp/mcp-server/security_fetch_package_vulnerabilities's live status: https://glimind.com/tool/mcp-registry/com.datanexusmcp/mcp-server/security_fetch_package_vulnerabilities.