Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.mrfentmen/osv-mcp

NPM · OSV-MCP

MCP server for OSV open source vulnerability data and package security checks.

Available components

0 this week 79 Trust /100

Last scanned (13 hours ago)

Scores higher than 63% of npm servers

Category Security

Trust breakdown (7 categories)

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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 405 tokens (~81/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage97
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 92% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 0
    • Stability: 0.97 → pass security
  • 20 Nov 26 0
    • Stability: pass → 0.97 functional
  • 14 Nov 26 0
    • Stability: 0.97 → pass security
  • 13 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 8 Nov 26 0
    • Provenance: pass → unverified ▼ security
    • Schema quality: 53 → 81 ▼ functional
    • Tool coverage: 80% → 92% ▲ functional
    • Package version: 1.0.0 → 1.0.1 functional
  • 6 Nov 26 +1
    • Stability: 0.97 → pass security
  • 4 Nov 26 +1
    • Security disclosure: unverified → fail ▼ functional
Diagnostics

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 21 Nov 2026 · Analysed npm/osv-mcp@1.0.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 93 packages
Packages resolved 93
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~405 tokens

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 →

Tool Tokens
advisory_database ~154

Search the GitHub Advisory Database: advisories affecting one package version, or the latest advisories for an ecosystem, with severity, CVSS, CWE and patch status.

NameTypeReqDescription
ecosystemstring–GitHub ecosystem name: npm, pip, go, maven, nuget, rubygems, rust, packagist, actions. Defaults to npm.
limitinteger–Max advisories, default 5.
package_namestring–Package name to look up advisories for. Takes priority over ecosystem.
severitystring–Severity filter: low, moderate, high or critical. Only used when no package name is given.
versionstring–Exact version of that package.

No output schema declared.

No examples provided.

check_package ~70

Check a package and optional version for known open source vulnerabilities.

NameTypeReqDescription
ecosystemstringyesOSV ecosystem, for example npm, PyPI, Go, crates.io, Maven, or NuGet
namestringyesPackage name
versionstring–Exact installed version, if known

No output schema declared.

No examples provided.

get_vulnerability ~51

Retrieve one OSV vulnerability by ID, such as GHSA, CVE, or OSV identifier.

NameTypeReqDescription
idstringyesVulnerability identifier, for example GHSA-... or CVE-...

No output schema declared.

No examples provided.

package_releases ~92

Release history for a package from deps.dev: how many versions exist, when each was published, and the licenses and advisory links for a specific version.

NameTypeReqDescription
namestringyesPackage name.
systemstringyesdeps.dev system name, for example npm, PyPI, Go, crates.io, NuGet or Maven.
versionstring–Exact version to report licenses and advisories for.

No output schema declared.

No examples provided.

scan_packages ~38

Scan several package references in one OSV request. Pass a JSON array of ecosystem, name, and optional version.

NameTypeReqDescription
packagesarrayyes–

No output schema declared.

No examples provided.

Install

How do I install the io.github.mrfentmen/osv-mcp server?

io.github.mrfentmen/osv-mcp runs locally as an npm package, launched with npx -y osv-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · osv-mcp

# add to Claude Code
claude mcp add mrfentmen-osv-mcp -- npx -y osv-mcp
Common questions

What is the io.github.mrfentmen/osv-mcp server?

io.github.mrfentmen/osv-mcp is listed in the public MCP registry as io.github.mrfentmen/osv-mcp. MCP server for OSV open source vulnerability data and package security checks. This page covers its npm package (osv-mcp).

Is the io.github.mrfentmen/osv-mcp server safe to use?

io.github.mrfentmen/osv-mcp scores 79 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. 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 io.github.mrfentmen/osv-mcp server expose?

io.github.mrfentmen/osv-mcp exposes 5 tools: check_package, scan_packages, get_vulnerability, advisory_database, package_releases. Their descriptions and schemas cost roughly 405 tokens of context every time the server is loaded.

Is the io.github.mrfentmen/osv-mcp server still maintained?

io.github.mrfentmen/osv-mcp is still listed as active in the MCP registry. We last reached this channel on 21 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 io.github.mrfentmen/osv-mcp server under?

io.github.mrfentmen/osv-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the io.github.mrfentmen/osv-mcp server?

VerifyMCP ran 16 checks on io.github.mrfentmen/osv-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.