CVESentry MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_cveA | Searches local CVE database by ID (e.g., CVE-2024-23334), package name, or keyword with zero latency. |
| audit_manifestA | Audits raw contents of requirements.txt or package.json for known vulnerabilities and returns fix recommendations. |
| get_cve_detailsA | Retrieves complete vulnerability metadata, CVSS score, severity, and affected ranges for a specific CVE ID. |
| get_safe_recommendationB | Returns the minimum safe version required to patch vulnerabilities for a given package and version. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.