PatchPilot MCP
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., "@PatchPilot MCP Check if lodash@4.17.0 is safe"
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.
PatchPilot MCP
Security scanner for vibe coders. Checks npm packages for known vulnerabilities before you install them.
What it does
PatchPilot is an MCP server that integrates with Claude Code, Cursor, and other AI coding tools. When you're about to install a package, you can ask Claude to check if it's safe first.
Example:
You: "Check if lodash@4.17.0 is safe to use"
Claude: 🚨 lodash@4.17.0 has 4 known vulnerabilities!
...
💡 Recommendation: Update to lodash@4.17.21 or laterRelated MCP server: CodeInspectus
Installation
Prerequisites
Node.js 18+
Claude Code or another MCP-compatible client
Setup
Clone this repository:
git clone https://github.com/YOUR_USERNAME/patchpilot-mcp.git
cd patchpilot-mcpInstall dependencies:
npm installBuild:
npm run buildAdd to Claude Code
Add to your Claude Code config (~/.claude/settings.json):
{
"mcpServers": {
"patchpilot": {
"command": "node",
"args": ["/path/to/patchpilot-mcp/dist/index.js"]
}
}
}Or for development (without building):
{
"mcpServers": {
"patchpilot": {
"command": "npx",
"args": ["tsx", "/path/to/patchpilot-mcp/src/index.ts"]
}
}
}Restart Claude Code after adding the config.
Usage
Once installed, ask Claude to check packages:
"Check if express@4.17.0 is safe"
"Is next@14.1.0 secure?"
"Check lodash 4.17.0 for vulnerabilities"
How it works
PatchPilot uses the OSV API (Google's Open Source Vulnerabilities database) to check packages. The API is:
Free (no API key needed)
Fast
Comprehensive (aggregates data from npm, GitHub, NVD, and more)
Available Tools
check_package
Check a single npm package for known vulnerabilities.
Input:
name: Package name (e.g., "lodash")version: Package version (e.g., "4.17.0")
Output:
Vulnerability count and severity breakdown
Details of each vulnerability
Recommended fix version
License
MIT
Available Tools
1 toolcheck_packageCheck Package SecurityA
Check if an npm package has known security vulnerabilities. Use this before installing any package to ensure it is safe.
Inputs: name (required), version (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusing it with other tools. The tool's purpose is clearly and unambiguously defined.
With a single tool, naming consistency is trivially satisfied. The name 'check_package' follows a clear verb_noun style that would be consistent if extended.
The server has only one tool, which feels too thin for the implied scope of 'PatchPilot'—a name suggesting broader patching and management workflows. One tool is insufficient to provide a meaningful set of operations.
The tool only checks for the presence of known vulnerabilities but provides no ability to list details, assess multiple packages at once, or suggest remediation. This creates significant gaps for agents needing comprehensive security information.
Maintenance
Related MCP Connectors
Pre-install security scans for npm packages, MCP servers, and AI agents with cited verdict evidence.
Package verdicts for AI coding agents: check npm, PyPI, Go and NuGet installs before they run.
Provide AI-powered real-time analysis and intelligence on NPM packages, including security, depend…
Checks AI-written code for leaked keys and made-up packages, on your machine. Never uploads code.
Related MCP Servers
- AlicenseAqualityDmaintenanceDependency security & health auditing for AI agents with no account or API key required.22MIT
- AlicenseAqualityBmaintenanceLocal-first, zero-egress security scanner for AI-generated / "vibe-coded" JS/TS. Bundles Opengrep, Gitleaks & Trivy behind one CWE-keyed schema and adds AI-code-specific checks (client-side secret exposure, Supabase RLS, prompt-injection & LLM-output XSS sinks). No account, no telemetry.10183 npm51Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to automatically verify npm packages against the live registry before installation, flagging hallucinated, slopsquatted, or otherwise suspicious packages with risk verdicts.5 npmMIT
- AlicenseAqualityBmaintenanceEnables AI coding agents and CI to vet npm dependencies before they reach the lockfile, flagging hallucinated, slopsquatted, or otherwise risky packages with evidence-backed verdicts.367 npm4MIT