mcp-dep-tools
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 |
|---|---|
| dep_check_licensesA | Analyze licenses of all dependencies in a package.json. Lists each dependency's license, flags copyleft (GPL) and unknown licenses, and checks compatibility. |
| dep_find_outdatedB | Check which dependencies are outdated. Compares current vs latest version, categorizes as major/minor/patch update, and shows days since last publish. |
| dep_analyze_treeB | Show the dependency tree: direct deps and their transitive deps, total depth, circular dependency detection, and total transitive dependency count. |
| dep_analyze_sizeA | Estimate total node_modules size from package.json without installing. Uses the bundlephobia API to get minified and gzipped size for each production dependency. |
| dep_security_auditA | Check dependencies for known security vulnerabilities. Uses npm audit when available, falls back to the npm registry advisory API. Shows severity, affected versions, and fix recommendations. |
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 clearly targets a distinct aspect of dependency management: size estimation, tree visualization, license checking, outdated detection, and security audit. There is no overlap in functionality.
All tools follow a consistent 'dep_<verb>_<object>' pattern with snake_case. The only slight deviation is 'dep_find_outdated' using 'find' instead of 'check' or 'analyze', but the pattern remains clear and predictable.
With 5 tools, the server covers the main concerns of dependency analysis (size, tree, licenses, outdated, security) without being too sparse or bloated. The count is well-scoped for the domain.
The tools provide comprehensive coverage for inspecting dependencies. Minor gaps exist, such as the absence of a tool to automatically update or fix issues, but the analysis functionality is complete for typical workflows.