Dependency Checker 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
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scan_fileB | Parses a manifest file and checks for vulnerabilities. |
| check_vulnerabilitiesC | Checks a list of dependencies. |
| get_vulnerability_detailsC | Get details for a list of vulnerability IDs. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| audit_dependencies | Instructs the agent to perform a comprehensive security audit of the project's dependencies. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool targets a distinct action: checking dependencies by list, retrieving vulnerability details by ID, and scanning a manifest file. No overlap in purpose.
All tool names follow a clear verb_noun pattern in snake_case (check_vulnerabilities, get_vulnerability_details, scan_file), with descriptive verbs that match the operation.
Three tools cover the core workflow of checking dependencies and retrieving details, which is appropriate for a focused dependency checker without unnecessary bloat.
The set covers the main use cases (checking via list or file, getting details), but might benefit from a tool to list all known vulnerabilities or update databases, though not essential.