Vulnerability Registry MCP Server
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_vulnerabilityA | Retrieve one vulnerability by its exact CVE identifier. Use for score, status, vendor, affected versions, title, or publication date of a specific CVE. |
| search_vulnerabilitiesA | Search and filter vulnerabilities by text, vendor, severity, status, CVSS score, or publication date. Use this for lists of matching CVEs. |
| search_vendorsA | Find vendors by name, category, or headquarters and return vulnerability counts. |
| get_vendor_overviewA | Return one vendor, aggregate vulnerability statistics, and its five most recent vulnerabilities. Use after identifying a vendor ID. |
| get_vulnerability_statisticsA | Count and summarize vulnerabilities without returning every matching record. Use for questions such as how many critical vulnerabilities are open. |
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 5 tools
Each tool targets a distinct operation: get_vulnerability for a specific CVE, search_vulnerabilities for filtered lists, search_vendors for vendor lookup, get_vendor_overview for aggregate vendor data, and get_vulnerability_statistics for counts. There is no meaningful overlap between any pair of tools.
All tool names follow a consistent verb_noun pattern using lowercase and underscores, with verbs limited to 'get' and 'search'. The naming clearly indicates whether a tool returns a single entity, a list, or statistics.
With 5 tools, the server is well-scoped for a vulnerability registry query interface. Each tool covers a distinct need without redundancy or bloat, fitting comfortably in the ideal 3-15 range.
The tool set provides complete read-only coverage for a vulnerability registry: individual CVE lookup, flexible searching, vendor discovery, vendor-specific aggregation, and vulnerability statistics. No obvious gaps exist for the apparent domain.