audit_nodejs_dependencies
Audit specific dependencies for vulnerabilities
Hand it a list of Node.js dependencies and get back the known vulnerabilities for those exact versions, without giving the server your source tree.
LABSCO SUMMARY
Because dependencies is an argument, this works on a proposed change as easily as on a shipped one: a version bump quoted in a pull request can be audited before anyone pulls the branch. The scope is exactly that one question. There is no project-wide scan, no lockfile parsing and no remediation step, so the answer stops at what is vulnerable.
A one-tool auditor for Node.js dependencies: you pass the dependency set as an argument, it reports what is known against it.
The dependency names and versions you want checked. No account, no key and no environment variables. MIT licensed.
One command — npx -y mcp-security-audit
USE CASES
Take the dependency names and versions out of the proposed change and pass them straight in, without checking the branch out. The report comes back against those exact versions, which is the question a reviewer is actually asking.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
audit_nodejs_dependenciesAudit specific dependencies for vulnerabilities
BEFORE YOU INSTALL
1 tool when we connected.
npx on PATH
CONTEXT COST
Rated by the size of the one tool definition that rides along on every turn
INSTALLATION
Add the block to your client, or run the command directly.
{
"mcpServers": {
"mcp-security-audit": {
"command": "npx",
"args": [
"-y",
"mcp-security-audit"
]
}
}
}npx -y mcp-security-audit