mcp-registry/io.github.pipeworx-io/osv/query_by_commit / alternatives
mcp-registry/io.github.pipeworx-io/osv/query_by_commitThe best live alternatives to mcp-registry/io.github.pipeworx-io/osv/query_by_commit right now are mcp-registry/com.contrastcyber/api/exploit_lookup, mcp-registry/dev.depscope/mcp/get_vulnerabilities, mcp-registry/com.contrastcyber/api/check_dependencies, mcp-registry/io.github.artchristech/fillin/query_cves, mcp-registry/io.github.megabrainee/sectora/assess_dependency — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/osv/query_by_commit itself is currently "healthy".
mcp-registry/com.contrastcyber/api/exploit_lookup is the top capability-matched alternative that's live right now. Other options: mcp-registry/dev.depscope/mcp/get_vulnerabilities, mcp-registry/com.contrastcyber/api/check_dependencies, mcp-registry/io.github.artchristech/fillin/query_cves, mcp-registry/io.github.megabrainee/sectora/assess_dependency. Glimind ranks alternatives by semantic similarity and live health.
mcp-registry/io.github.pipeworx-io/osv/query_by_commit's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fosv%2Fquery_by_commit.
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%2Fio.github.pipeworx-io%2Fosv%2Fquery_by_commit
or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/osv/query_by_commit's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/osv/query_by_commit.