PatchProof MCP
Provides tools for inspecting npm supply chain, including scanning repositories, generating SBOMs, auditing dependencies, and creating evidence reports.
Click on "Install 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., "@PatchProof MCPscan the repository at ./my-project for dependency 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.
PatchProof MCP
PatchProof is a focused Model Context Protocol server for local npm supply-chain inspection. The MVP exposes four tools with deterministic, offline-friendly behavior.
Current Status
The complete public tool set is implemented and covered by focused tests:
scan_repository: bounded repository file and byte counting.generate_sbom: deterministic CycloneDX-shaped SBOM generation frompackage-lock.json.audit_dependencies: dependency extraction with a deterministic mock vulnerability table.generate_evidence_report: JSON evidence metadata and a self-contained HTML preview.
Important limitations:
Only npm
package-lock.jsonrepositories are supported.audit_dependenciesdoes not yet query the live OSV API. Selectinglivecurrently uses the same deterministic mock data.scan_repositorycurrently returns repository statistics; vulnerability and secret findings are not yet integrated into its result.Evidence reports currently contain metadata and limitations, not a complete end-to-end audit.
There is no browser demo, Docker image, deployment, CI workflow, or published coverage claim in this revision.
Streamable HTTP is scaffolded and should not yet be treated as a verified production transport when using the local CLI.
The Vercel demo exposes a stateless Streamable HTTP endpoint at /api/mcp.
For safety, every public tool call is locked to the bundled demo fixture; it
does not accept arbitrary server filesystem paths.
Related MCP server: Dependency Checker MCP Server
Requirements
Node.js 20
npm 10
Install And Verify
npm ci
npm run typecheck
npm test
npm run buildThe focused core-tool test suite creates a temporary npm repository and calls the four implemented tools directly.
Run
Build first, then start the stdio MCP server:
npm run build
npm run start:stdioDeploy The Live Demo
Import this GitHub repository into Vercel and deploy with the default settings. The deployment provides:
/- a static project and tool overview;/api/mcp- the stateless MCP Streamable HTTP endpoint;a bundled npm fixture containing deterministic mock vulnerabilities.
Verify the deployment:
curl -X POST https://YOUR-DEPLOYMENT.vercel.app/api/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'Tool Summary
scan_repository
Input:
{
"repoRoot": "/authorized/repository",
"includeHidden": false,
"followSymlinks": false
}Returns the resolved repository root, files scanned, bytes read, duration, ignored directories, and the current findings array.
generate_sbom
Input:
{
"repoRoot": "/authorized/repository",
"format": "cyclonedx"
}Returns a deterministic CycloneDX 1.5-shaped component list derived from
package-lock.json.
audit_dependencies
Input:
{
"repoRoot": "/authorized/repository",
"osvMode": "mock",
"ecosystem": "npm"
}Returns parsed dependencies and matching entries from the local deterministic mock vulnerability table.
generate_evidence_report
Input:
{
"repoRoot": "/authorized/repository",
"format": "both"
}Returns evidence metadata as JSON and, for html or both, a self-contained
HTML preview.
Architecture
src/server MCP registration and CLI
src/tools four public MCP tool definitions
src/scanners bounded repository traversal
src/parsers npm lockfile parsing
src/sbom deterministic SBOM assembly
src/osv deterministic mock dependency audit
src/reporting JSON and HTML evidence metadata
src/security path, resource, error, and redaction utilities
src/transport stdio and HTTP transport scaffolding
tests/unit infrastructure and focused core-tool testsBusiness logic is kept outside the MCP registry so it can be tested directly.
Security Notes
Callers must provide or authorize a repository root.
Repository traversal is bounded by file, byte, depth, and time limits.
Common generated directories such as
.git,node_modules,dist,build, andcoverageare ignored.The implemented dependency audit is local and deterministic.
This is an MVP, not a completed security product. Do not rely on it as the sole source for vulnerability or secret detection.
CyOps Arena
The repository was scaffolded and iterated with CyOps Humanize using MiniMax M3. The Git history and planning documents retain the generated implementation evidence. Manual verification confirmed:
strict TypeScript typecheck passes;
the Vitest suite passes;
the production TypeScript build passes.
License
MIT. See LICENSE.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/eaglebooth/patchproof-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server