Osv
NPM · @PIPEWORX/MCP-OSV · 2 COMPONENTS
OSV.dev (Open Source Vulnerabilities) MCP.
Available components
Last scanned (11 hours ago)
Scores higher than 69% of npm servers
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-osv). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 551 tokens (~137/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 81
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-osv@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-osv |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-osv/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3685208743 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:40266557499d95f88a7d663698fc3f532c93069862badd4ae6792e8e5e3bc76cbad45ac7e7e5801d0f108802c18492e4dbb9ae6e6724e3d3f3aa11522 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_vulnerability ~120
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | A vulnerability ID, e.g. "GHSA-jf85-cpcp-j695", "CVE-2021-23337", "PYSEC-2021-1". |
No output schema declared.
No examples provided.
query_batch ~114
Batch vulnerability query against OSV.dev (up to 1000 entries per call) — for SBOM-style "scan every dependency in this lockfile" workflows. Pass an array of {package:{name,ecosystem}, version?} or {commit} entries. Returns the vuln IDs matched per query (use get_vulnerability for full detail per ID). Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| queries | array | yes | Up to 1000 query objects. Each: {package:{name,ecosystem}, version?} or {commit}. |
No output schema declared.
No examples provided.
query_by_commit ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| commit | string | yes | A git commit hash, e.g. "6879efc2c1596d11a6a6ad296f80063b558d5e0f". |
No output schema declared.
No examples provided.
query_package_vulns ~175
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | yes | Package ecosystem. Examples: "npm", "PyPI", "Go", "Maven", "crates.io", "RubyGems", "NuGet". |
| name | string | yes | Package name, e.g. "lodash", "django", "log4j-core", "serde". |
| version | string | – | Optional package version, e.g. "4.17.20". If given, only vulns affecting that version are returned; if omitted, all vulns for the package are returned. |
No output schema declared.
No examples provided.
How do I install the Osv MCP server?
Osv runs locally as an npm package, launched with npx -y @pipeworx/mcp-osv. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-osv
claude mcp add pipeworx-io-osv -- npx -y @pipeworx/mcp-osv
What is the Osv MCP server?
Osv is an MCP server listed in the public MCP registry as io.github.pipeworx-io/osv. OSV.dev (Open Source Vulnerabilities) MCP. This page covers its npm package (@pipeworx/mcp-osv).
Is the Osv MCP server safe to use?
Osv scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Osv MCP server expose?
Osv exposes 4 tools: query_package_vulns, get_vulnerability, query_by_commit, query_batch. Their descriptions and schemas cost roughly 500 tokens of context every time the server is loaded.
Is the Osv MCP server still maintained?
Osv is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Osv MCP server under?
Osv declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.