Performs local vulnerability scans on directories, container images, and SBOMs to provide prioritized remediation plans for AI agents.
Also known as ciloops/vuln-check, @ciloops/vuln-check
- Stars
- 1
- Tools
- —
- Downloads, 30 days
- 938
- Latest version
- 0.1.3
- Last commit
- Oct 23, 2026
- License
- Apache-2.0
What is vuln-check MCP?
vuln-check performs local vulnerability scans on directories, container images, and SBOMs to provide prioritized remediation plans for AI agents.
Summary generated from the project's README
About vuln-check MCP server
Identifying security vulnerabilities in codebases and container images is what vuln-check enables for AI agents. It runs locally on your machine using grype to scan directories, SBOMs, and container images, providing a prioritized remediation plan instead of overwhelming JSON files. The tool calculates a single score for every finding by combining CVSS, EPSS, CISA KEV, and fix availability data.
Developers can integrate this server into clients like Claude Code, Cursor, Windsurf, or VS Code. It requires grype to be installed on the local system. While it primarily runs locally, it can optionally query the OSV API to provide the most recent vulnerability data before it reaches the standard grype database. You can use the scan_dir, scan_image, scan_sbom, vuln_lookup, and db_update tools to manage security posture directly through your AI interface.
What you can do with it
- 1Scan local project directoriesAsk your AI agent to check a local folder for security issues using the scan_dir tool.
- 2Analyze container imagesRequest a vulnerability assessment of a specific container image pulled from a registry.
- 3Get prioritized remediation stepsHave the agent identify the smallest version upgrade required to fix a specific vulnerability.
- 4Lookup specific CVE detailsDirect the AI to find information regarding a particular CVE identifier.
Written from the project's README. Every use case is checked against a quote from it.
How to install vuln-check MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall vuln-check MCP in Claude Code
$ claude mcp add vuln-check -- npx -y @ciloops/vuln-checkInstall vuln-check MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"vuln-check": {
"command": "npx",
"args": [
"-y",
"@ciloops/vuln-check"
]
}
}
}Install vuln-check MCP in VS Code
.vscode/mcp.json
{
"servers": {
"vuln-check": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@ciloops/vuln-check"
]
}
}
}Install vuln-check MCP in VS Code CLI
$ code --add-mcp '{"name":"vuln-check","type":"stdio","command":"npx","args":["-y","@ciloops/vuln-check"]}'Install vuln-check MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"vuln-check": {
"command": "npx",
"args": [
"-y",
"@ciloops/vuln-check"
]
}
}
}Install vuln-check MCP in Codex
$ codex mcp add vuln-check -- npx -y @ciloops/vuln-checkInstall vuln-check MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.vuln-check] command = "npx" args = ["-y", "@ciloops/vuln-check"]
Install vuln-check MCP in Gemini CLI
$ gemini mcp add -s user vuln-check npx -- -y @ciloops/vuln-checkInstall vuln-check MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"vuln-check": {
"command": "npx",
"args": [
"-y",
"@ciloops/vuln-check"
]
}
}
}Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachableciloops/vuln-check is public and reachablegithub.com/ciloops/vuln-check ↗Pass
- Package names this repository as its source@ciloops/vuln-check names ciloops/vuln-check as sourcenpmjs.com/package/@ciloops/vuln-check ↗Pass
- Build provenance (Sigstore attestation)Sigstore attestation for @ciloops/vuln-checknpmjs.com/package/@ciloops/vuln-check/v/0.1.3#provenance ↗Pass
- Open source license (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-10-23github.com/ciloops/vuln-check ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from @ciloops/vuln-checkPass
- No critical advisory in the package or its dependencies1 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubvuln-check
Vulnerability truth for AI agents. Runs grype locally, merges an OSV freshness overlay, and returns a prioritised answer with concrete upgrade targets instead of a 40 KB JSON dump.
- Any language with a lockfile (npm, PyPI, Go, Maven, Cargo, RubyGems, Composer, NuGet, Hex, Pub, Swift, R, Conan…), OS packages, container images, SBOMs.
- One score per finding: CVSS + EPSS + CISA KEV + fix availability.
- Remediation plan per package: smallest version that closes every finding,
breakingflag. CLEANis ~20 tokens. Nothing runs on a server; nothing leaves your machine except the optional OSV query.
Install
# grype is required
brew install grype # or: curl -sSfL https://get.anchore.io/grype | sh -s -- -b /usr/local/bin
go install github.com/ciloops/vuln-check/cmd/vuln-check@latest
# or
brew install ciloops/tap/vuln-check # macOS cask
# or
npx @ciloops/vuln-check scan .
Binaries for Linux/macOS/Windows on the Releases page. Docker: ghcr.io/ciloops/vuln-check (bundles grype).
CLI
vuln-check scan . # agent format, OSV overlay on
vuln-check scan python:3.12-slim # image, pulled from the registry
vuln-check scan sbom:bom.cdx.json
vuln-check scan --format sarif --sarif-out out.sarif .
vuln-check scan --fail-above 69 --no-osv . # CI gate, exit 2 above threshold
vuln-check vuln CVE-2024-3094
vuln-check db update
Output (--format agent):
{"status":"ACTION_REQUIRED","target":"dir:.","packages":412,"findings":17,"shown":5,"sources":["grype","osv"],
"actions":[{"package":"pkg:npm/minimist","current":"1.2.5","target":"1.2.6","breaking":false,"fixes":["CVE-2021-44906"],"score":59}],
"top":[{"id":"CVE-2021-44906","package":"minimist@1.2.5","severity":"CRITICAL","score":59,"epss":0.015,"fixed_in":["1.2.6"]}],
"unfixable":3}
status: CLEAN | REVIEW (all findings < 40) | ACTION_REQUIRED. fresh: true marks advisories that came from OSV before grype-db ingested them. unfixable counts findings with no fix on the current release line.
MCP
Tools: scan_dir, scan_image, scan_sbom, vuln_lookup, db_update.
Claude Code:
claude mcp add vuln-check -- vuln-check mcp
# or the plugin (adds a skill that tells Claude when to scan):
claude plugin marketplace add ciloops/vuln-check && claude plugin install vuln-check
Cursor / Windsurf / VS Code (.cursor/mcp.json, ~/.codeium/windsurf/mcp_config.json, .vscode/mcp.json):
{ "mcpServers": { "vuln-check": { "command": "vuln-check", "args": ["mcp"] } } }
Codex (~/.codex/config.toml):
[mcp_servers.vuln-check]
command = "vuln-check"
args = ["mcp"]
Add --no-osv to the args to keep the dependency list off the network.
GitHub Action
- uses: ciloops/vuln-check@v1
with:
target: . # or an image ref
fail-above: 69
sarif: vuln.sarif
- uses: github/codeql-action/upload-sarif@v3
if: always()
with: { sarif_file: vuln.sarif }
Score
severity = CVSS base × 6 (label fallback) · exploit = EPSS × 30 · KEV: +10, floor 85 · no fix: × 0.85. Clamped to 0–100. See internal/score.
Freshness
grype-db builds daily and grype refreshes it at most every 2 h. The OSV overlay queries api.osv.dev with the purls grype inventoried (language ecosystems only) and adds anything grype-db has not seen yet, usually minutes after a GHSA is published. Disable with --no-osv.
Limits
- No lockfile → transitive dependencies are invisible. Same as every scanner.
- Remediation plans assume a linear release line per package; direct vs transitive is not distinguished yet.
- Version comparison is a generic tokenizer, not per-ecosystem parsers. Good enough for "smallest fix above current"; edge cases exist (PEP 440 post-releases, exotic Maven qualifiers).
Development
go test ./...
go build ./cmd/vuln-check
Tests run against a fake grype (cmd/vuln-check/testdata/fake-grype.sh) and fixtures in internal/grype/testdata. CI runs a real grype e2e.
Release: tag vX.Y.Z → goreleaser publishes binaries, checksums, ghcr image, Homebrew cask for macOS (needs HOMEBREW_TAP_GITHUB_TOKEN and the ciloops/homebrew-tap repo) and the npm package via trusted publishing (OIDC, no token: configure the GitHub Actions trusted publisher for @ciloops/vuln-check on npmjs.com, workflow release.yml).
License
Apache-2.0. grype and syft are Apache-2.0 by Anchore. Vulnerability data: NVD (public domain), GHSA (CC-BY 4.0), OSV (per source), CISA KEV, FIRST EPSS.
vuln-check MCP questions
How do I add vuln-check MCP to Claude Code?
Run claude mcp add vuln-check -- npx -y @ciloops/vuln-check in your terminal. Add --scope user to make it available in every project.
How do I add vuln-check MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What can vuln-check scan?
It can scan any language with a lockfile (such as npm, PyPI, Go, Maven, Cargo, etc.), OS packages, container images, and SBOMs.
Does the data leave my machine?
Nothing runs on a server and nothing leaves your machine except for an optional query to the OSV database.
Can I use this in a CI/CD pipeline?
Yes, it can be used as a GitHub Action to gate CI builds based on a vulnerability threshold.