mcp-dependency-doctor
Related Servers
Alternatives to mcp-dependency-doctor
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceAudits npm, Yarn, and pnpm lockfiles from local project directories or remote Git repositories (public or private) and returns vulnerability reports in text or JSON. Supports configurable severity thresholds, custom npm registries, dev-dependency skipping, and report language selection.5 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables auditing npm, Yarn, and pnpm lockfiles in local project directories or remote Git repositories to surface dependency vulnerabilities. Exposes a tool that supports severity thresholds, registry overrides, optional dev-dependency skipping, and text or JSON reports.5 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables auditing npm, Yarn, and pnpm lockfiles from local project directories or remote Git repositories, returning vulnerability results in text or JSON with configurable thresholds and dev-dependency skipping.5 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables auditing npm, Yarn, and pnpm lockfiles from local project directories or remote Git repositories, returning vulnerability results in text or JSON with configurable thresholds and dev dependency skipping.5 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables auditing npm, Yarn, and pnpm lockfiles from local project directories or remote Git repositories, returning vulnerability results in text or JSON with configurable severity thresholds and dev dependency handling.5 npmMIT
- AlicenseAqualityAmaintenanceScores npm packages, PyPI packages and GitHub repositories 0-100 with an A-F grade and plain-language risks. Scans package.json, requirements.txt and lock files; no API key needed.373 npm1Apache 2.0
TDQS
Scored across 4 tools
The tools are mostly distinct: inventory reads lockfile data, audit checks vulnerabilities, outdated checks available updates, and package_health inspects package metadata. There is minor potential overlap between dependency_audit and package_health since both assess package quality/risk, but the descriptions make the boundary reasonably clear.
All names use snake_case and are descriptive noun-style tool names. Three use a dependency_ prefix while one uses package_health, which is a minor inconsistency but still readable and predictable.
Four tools is well-scoped for a dependency diagnostics server, with each operation covering a distinct diagnostic angle. There is no obvious bloat or missing basic operation.
The surface covers lockfile inventory, vulnerability audit, outdated packages, and package health metadata, which are core dependency-doctor workflows. Minor gaps exist around license compliance or dependency tree/duplicate analysis, but agents can work around them.