Provides tools for checking npm packages for known security vulnerabilities and CVEs before installation using the OSV API
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@CVE Checker for Node Modules check express 4.17.1 for vulnerabilities"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
This Model Context Protocol (MCP) server provides tools for checking Common Vulnerabilities and Exposures (CVEs) in npm packages before installation, along with weather information tools.
check_package_cves: Check a single npm package for known vulnerabilities
check_packages_bulk_cves: Check multiple npm packages at once before installation
Related MCP server: pkgproof
The server uses the OSV (Open Source Vulnerabilities) API to check npm packages for known security vulnerabilities. This helps you make informed decisions before installing packages.
{
"tool": "check_package_cves",
"arguments": {
"packageName": "express",
"version": "4.17.1"
}
}{
"tool": "check_packages_bulk_cves",
"arguments": {
"packages": [
{ "name": "express", "version": "4.17.1" },
{ "name": "lodash", "version": "4.17.20" },
{ "name": "axios" }
]
}
}Install dependencies:
npm installBuild the project:
npm run buildRun the MCP server:
node build/index.jsAdd to .vscode/mcp.json to configure the MCP server in your development environment.
{
"servers": {
"cve-checker-mcp": {
"type": "stdio",
"command": "node",
"args": ["./build/index.js"]
}
},
"inputs": []
}This MCP server can be integrated with any MCP-compatible client to provide CVE checking capabilities before installing npm packages.
Check for known CVEs/vulnerabilities in npm packages before installation
Inputs: packageName (required), version.
Check multiple npm packages for CVEs at once (useful before installing dependencies)
Inputs: packages (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 2 tools
The two tools have overlapping purposes—both check npm packages for CVEs—but their descriptions clarify the distinction: one handles single packages and the other handles multiple packages. This overlap could still cause mild confusion for an agent deciding which tool to use, especially if the context involves a single package where either might apply.
The tool names follow a consistent verb_noun pattern with 'check' as the verb and 'cves' as a common element, using snake_case throughout. The minor deviation is the addition of 'bulk' in the second name, which is descriptive and maintains readability without breaking the overall pattern.
With only 2 tools, the server feels thin for its purpose of CVE checking in Node modules, as it might lack operations like updating CVE databases, checking specific CVE details, or handling package versions. However, the core functionality is covered, making it borderline but not severely lacking.
The tool set is significantly incomplete for the domain of CVE checking. It covers basic checking but lacks tools for operations like retrieving CVE details, updating vulnerability databases, checking package versions against CVEs, or handling installation recommendations. This will likely cause agent failures when more comprehensive actions are needed.
Detect malicious or vulnerable npm packages: registry search, OSV.dev and GitHub advisory lookups
Check npm, PyPI, Go and Maven packages or lockfiles against OSV.dev: CVEs, CVSS, fixed versions.
Scan packages and lockfiles (npm, PyPI, Go, Maven, Cargo, NuGet) for vulnerabilities and malware.
Queries live Google OSV.dev vulnerability intelligence for any PyPI, npm, Go, or Rust crate and r.
