
Osv Mcp
io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.0Updated Oct 24, 2026
Use this MCP server to OSV open source vulnerability data and package security checks. Tools...
Overview
Local MCP server that lets a coding assistant check open source packages against OSV.dev vulnerability data and look up CVE, GHSA or OSV records.
- What you can do
- Check a single package by ecosystem, name and optional version
- Scan a list of package references in one request, with lockfiles parsed in the client
- Retrieve a specific CVE, GHSA or OSV vulnerability record
- When to use it
- Useful when an assistant reviews dependencies, audits a lockfile, or needs to confirm whether a package version has known vulnerabilities before suggesting or upgrading it.
- Requirements
- Runs as a local stdio process installed from the npm package osv-mcp (build with npm install and npm run build, then run the built entry point). Needs network access to the public OSV.dev API; no API key or account is required.
Installation
In SourceWeft
- Open Osv Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
OSV MCP
Open source vulnerability checks for coding agents. It uses the public OSV.dev API and needs no API key.
Tools
check_packagechecks an ecosystem, package name, and optional versionscan_packageschecks several package references in one request; parse lockfiles in your client and pass the package listget_vulnerabilityretrieves a CVE, GHSA, or OSV record
Run
The server is read only and uses stdio MCP transport.
Source: README.md at commit f9eaa76
Tools
0Version history
1- v1.0.0LatestSep 22, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.