Depcheck
Known vulnerabilities for exact package versions from OSV, with fixes. Paid per call, x402.
Should I use this
Quality & Safety
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"depcheck": {
"url": "https://depcheck.kaneky.dev/mcp"
}
}
}Remote endpoints
https://depcheck.kaneky.dev/mcpstreamable-httpWhat it can do
Tool inventory
Tools (1)
🟢check_packages(packages)
Look up the known vulnerabilities affecting exact package versions in the public OSV database (npm, PyPI, Go, Maven, crates.io, RubyGems, NuGet, Packagist, Pub, Hex), 1 to 50 packages per call. Per package: every OSV advisory for that version with its id, CVE/GHSA aliases, summary, severity (database label, CVSS vectors, v3 base scores), the versions that fix it or "no fix published", published/modified dates and a link. Plus a summary: packages checked, packages vulnerable, total advisories and the highest severity. Evidence, not advice: absence from OSV does not prove safety.
Input Schema
{
"type": "object",
"properties": {
"packages": {
"items": {
"properties": {
"ecosystem": {
"description": "OSV's ecosystem name, case-sensitive.",
"enum": [
"npm",
"PyPI",
"Go",
"Maven",
"crates.io",
"RubyGems",
"NuGet",
"Packagist",
"Pub",
"Hex"
],
"type": "string"
},
"name": {
"description": "As the ecosystem names it: lodash, requests, github.com/gin-gonic/gin, org.apache.logging.log4j:log4j-core.",
"maxLength": 214,
"minLength": 1,
"type": "string"
},
"version": {
"description": "The exact version, not a range.",
"maxLength": 128,
"minLength": 1,
"type": "string"
}
},
"required": [
"ecosystem",
"name",
"version"
],
"type": "object"
},
"maxItems": 50,
"minItems": 1,
"type": "array"
}
},
"required": [
"packages"
]
}Community
Evidence