CVE Checker for Node Modules
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 |
|---|---|
| check_package_cvesB | Check for known CVEs/vulnerabilities in npm packages before installation |
| check_packages_bulk_cvesA | Check multiple npm packages for CVEs at once (useful before installing dependencies) |
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 2 tools
The two tools have overlapping purposes—both check npm packages for CVEs—but their descriptions clarify the distinction: one handles single packages and the other handles multiple packages. This overlap could still cause mild confusion for an agent deciding which tool to use, especially if the context involves a single package where either might apply.
The tool names follow a consistent verb_noun pattern with 'check' as the verb and 'cves' as a common element, using snake_case throughout. The minor deviation is the addition of 'bulk' in the second name, which is descriptive and maintains readability without breaking the overall pattern.
With only 2 tools, the server feels thin for its purpose of CVE checking in Node modules, as it might lack operations like updating CVE databases, checking specific CVE details, or handling package versions. However, the core functionality is covered, making it borderline but not severely lacking.
The tool set is significantly incomplete for the domain of CVE checking. It covers basic checking but lacks tools for operations like retrieving CVE details, updating vulnerability databases, checking package versions against CVEs, or handling installation recommendations. This will likely cause agent failures when more comprehensive actions are needed.