OSV.dev (Open Source Vulnerabilities) MCP. Google's keyless database of vulnerabilities across open-source ecosystems (npm, PyPI, Go, Maven, crates.io, RubyGems, NuGet, and more). Query known vulnerabilities for a package (optionally at a specific version), fetch full detail for a single advisory ID, or find vulnerabilities affecting a source commit. Keyless.
Three well-named tools with clear, actionable descriptions (150 - 180 chars each). All tools have complete input schemas with required fields and parameter descriptions. Naming follows verb_noun pattern (query_*, get_*). Output schema is documented in descriptions but not formally in JSON Schema. Error handling returns structured objects with error messages and context. Main gaps: no output schema formally declared, no pagination support despite potential for large result sets, no tool annotations (readOnlyHint), and parameter descriptions lack format/constraint details (e.g., ecosystem enum values, commit hash format).
Get full detail for a single vulnerability by its OSV ID — e.g. "GHSA-jf85-cpcp-j695", "CVE-2021-23337", "PYSEC-2021-XXX". Returns summary, details, aliases, severity, affected packages/ranges, and references. Keyless.
Find vulnerabilities affecting a specific source-repository git commit via OSV.dev. Useful when you have a pinned commit hash rather than a released version. Returns the same compact vuln summary array. Keyless.
Find all known vulnerabilities for an open-source package, optionally at a specific version, via the OSV.dev database. Omit version to get every vuln known for the package. Returns a compact summary array (id, summary, aliases, severity, references). Keyless.
No formal output schema documentation. Descriptions mention return structure (compact summary array, full detail) but JSON Schema outputSchema is absent. LLMs cannot reliably parse response structure or plan downstream operations.
query_package_vulns returns up to 50 vulns but no pagination (limit, offset, next_cursor). Large packages could have hundreds of vulns; capping at 50 silently truncates results without indicating more exist. No total_count returned.
Parameter 'ecosystem' lacks enum constraint. Description lists examples ('npm', 'PyPI', 'Go', 'Maven', 'crates.io', 'RubyGems', 'NuGet') but no formal enum in schema. LLMs may hallucinate invalid ecosystem names.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 61 | 2026-07-28+ | v2 |
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). All three tools are read-only and idempotent, but this is not declared in the schema. Agents cannot infer safety properties.
Parameter descriptions lack format constraints. 'commit' parameter says 'e.g. 6879efc2c1596d11a6a6ad296f80063b558d5e0f' but does not specify length (40 hex chars for SHA-1) or pattern. LLMs may pass invalid commit hashes.