CVESentry 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., "@CVESentry MCP audit requirements.txt and give me safe upgrade versions for any vulnerable packages"
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.
CVESentry MCP (Lite)
Autonomous Local Vulnerability Scanner, Fast CVE Search Engine & Dependency Audit Plane for AI Coding Agents
CVESentry MCP gives AI coding agents (Claude Desktop, Cursor, Devin, Roo-Code) instant (<5ms) vulnerability intelligence without rate-limits or slow external API keys. It audits dependency manifests (requirements.txt, package.json), identifies vulnerable versions, and provides automated upgrade paths.
π Features (Lite Edition)
Instant Local CVE Search (
search_cve): Query vulnerability records in sub-millisecond local SQLite memory with zero network dependencies.Dependency Manifest Auditor (
audit_manifest): Parsesrequirements.txtandpackage.json, checks versions against vulnerable ranges, and calculates severity breakdowns.CVE Detailed Metadata (
get_cve_details): Detailed CVSS score, vulnerability category, affected package version bounds, and security summaries.Safe Version Recommendation (
get_safe_recommendation): Calculates the minimal patch version that eliminates all matching CVEs.
Related MCP server: Security Intel MCP
π¦ Installation & Setup
git clone https://github.com/johannschiffer/cvesentry-mcp.git
cd cvesentry-mcp
pip install -e .Configuration with Claude Desktop / Cursor
Add to your claude_desktop_config.json:
{
"mcpServers": {
"cvesentry": {
"command": "python3",
"args": ["-m", "cvesentry.server"]
}
}
}β‘ Quick CLI Usage
# Search for a CVE or package
cvesentry search --query "aiohttp"
# Audit a requirements.txt file
cvesentry audit --file requirements.txtπΌ Upgrade to CVESentry Pro
Need enterprise security compliance for automated code generation?
Multi-Ecosystem Engine (SQLite WAL): Full parsing for Python (
pyproject.toml,Pipfile), Node (package-lock.json), Rust (Cargo.lock), and Go (go.mod).EPSS & CISA KEV Exploit Prioritization: Real-world Exploit Prediction Scoring System (EPSS) and CISA Known Exploited Vulnerabilities catalog integration.
Automated Safe Version Upgrader: Automatically patches manifests while preserving semver constraints to minimize breaking changes.
Audit Certificate Exporter: Generates formatted markdown and JSON reports for GitHub PR reviews.
Docker & Compose Ready: Deploy as a microservice sidecar in your CI/CD cluster.
Available at Gumroad.
π License
MIT Β© Johann Schiffer
Available Tools
4 toolsaudit_manifestA
Audits raw contents of requirements.txt or package.json for known vulnerabilities and returns fix recommendations.
Inputs: content (required), manifest_type (required).
get_cve_detailsA
Retrieves complete vulnerability metadata, CVSS score, severity, and affected ranges for a specific CVE ID.
Inputs: cve_id (required).
get_safe_recommendationB
Returns the minimum safe version required to patch vulnerabilities for a given package and version.
Inputs: package (required), ecosystem (required), current_version (required).
search_cveA
Searches local CVE database by ID (e.g., CVE-2024-23334), package name, or keyword with zero latency.
Inputs: query (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogβ¦
TDQS
Scored across 4 tools
Each tool has a distinct primary purpose, but there is minor overlap: search_cve can search by CVE ID while get_cve_details retrieves full details for a CVE ID, and audit_manifest returns fix recommendations that overlap with get_safe_recommendation's single-package fix output. The descriptions still provide enough guidance to select correctly.
All four tool names follow a consistent snake_case verb_noun pattern (search_cve, audit_manifest, get_cve_details, get_safe_recommendation). There is no mixing of conventions or verb styles.
Four tools are well-scoped for a local CVE lookup and remediation server: search, audit, detailed lookup, and safe version recommendation. Each tool earns its place and the set is not bloated or thin.
The set covers the core lifecycle: lookup by ID/package/keyword, audit a manifest, retrieve full CVE metadata, and get a safe patch version. A minor gap is the lack of a direct 'is this version vulnerable?' query, though agents can infer this from search_cve or get_safe_recommendation.
Related MCP Connectors
CVE lookups (NVD) and dependency-manifest audits (OSV) for AI agents. No API keys.
CVE lookups (NVD) and dependency-manifest audits (OSV) for AI agents. No API keys.
Free CVE lookup, dependency vulnerability checks, and CVE updates. No signup or API key.
Queries live Google OSV.dev vulnerability intelligence for any PyPI, npm, Go, or Rust crate and re
Related MCP Servers
- AlicenseAqualityDmaintenanceDependency security & health auditing for AI agents with no account or API key required.22MIT
- AlicenseAqualityBmaintenanceVulnerability intelligence for AI agents that enables CVE lookup, package vulnerability checks, and dependency auditing without API keys.5MIT
- AlicenseNot gradedqualityCmaintenanceProvides security checks for AI agents, including secret scanning, CVE lookup, and dependency vulnerability scanning, all running locally except for CVE lookups.MIT

Fetter MCPofficial
FlicenseNot gradedqualityDmaintenanceProvides real-time Python package vulnerability data, enabling AI agents to check CVEs, CVSS scores, and safe versions for informed dependency decisions.1-