MCP NVD 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| nvd_toolC | Fetch CVE data from NVD |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'nvd_tool' has a clear and distinct purpose of fetching CVE data from NVD.
A single tool inherently has perfect naming consistency as there are no other tools to compare against. The name 'nvd_tool' follows a simple noun-based pattern appropriate for its function.
One tool is generally too few for most server purposes, especially for a data source like NVD which typically supports multiple operations (e.g., search by CVE ID, filter by date, get recent vulnerabilities). This feels thin and limited in scope.
The tool surface is severely incomplete for an NVD server. While fetching CVE data is a core function, obvious gaps include searching, filtering, pagination, and accessing specific vulnerability details, which are essential for comprehensive CVE data interaction.