depquiet
Related Servers
Alternatives to depquiet
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceTranslates a lockfile diff into a human-readable upgrade plan. For every dependency bump (npm or PyPI) returns semver class, breaking changes from GitHub release notes, CVEs fixed in the range, migration guide links, and a clear per-package recommendation. Bulk tool ranks up to 50 package changes in parallel by risk (security > caution > review > likely-safe > safe).2101 npm2MIT
- AlicenseAqualityBmaintenanceEnables an AI agent to parse project lockfiles (npm, pnpm, Yarn, uv, Poetry, requirements.txt, Cargo, go.sum) and query OSV.dev to find known vulnerabilities in locked versions, transitive dependencies included, then produce minimal upgrade plans with breaking-change flags, cleanliness re-checks, and the parent dependency responsible. It also lists outdated packages and explains individual advisories, all read-only with no API key required.5MIT

@4da/mcp-serverofficial
AlicenseAqualityBmaintenanceEnables AI coding agents to learn, from locally read lockfiles, what changes between the dependency version installed and a target version, which of the user's files that upgrade touches, and which vulnerabilities it resolves. It also performs OSV-matched vulnerability scans, ranks upgrade plans, and stores decision memory, running entirely on the user's machine with no account or API keys.11508 npmApache 2.0- AlicenseAqualityBmaintenanceEnables AI coding agents to ground dependency setup, compatibility checks, and major-version migration advice in a project's real runtime, lockfiles, and config files. It parses local project state and npm registry metadata deterministically, then returns tag-pinned install commands, breaking changes, and upgrade steps rather than generic documentation.553 npmMIT
- FlicenseNot gradedqualityDmaintenanceFetches GitHub Code Scanning alerts and applies minimal local patches to fix vulnerabilities, without creating branches, commits, or PRs.-
- FlicenseAqualityAmaintenanceDependency intelligence for AI agents. CVE scanning, health checks, upgrade planning.92-
TDQS
Scored across 2 tools
The two tools divide cleanly along a read-analyze vs. plan-change boundary: triage_alerts classifies existing alerts, plan_fixes computes a concrete dependency change. Descriptions explicitly cross-reference each other ('use it first... then call plan_fixes'), so there is no realistic risk of misselection.
Both names are snake_case verb_noun pairs (triage_alerts, plan_fixes) with the same plural-object convention and parallel verb style. No mixing of casing or verb forms.
Two tools is thin for a dependency-security domain, though each is heavy and multi-stage so the surface is at least functional. The count is borderline by the rubric rather than clearly well-scoped.
The triage-then-plan lifecycle is covered, and re-running triage_alerts serves as verification after applying a diff. Minor gaps remain: no per-alert detail lookup, no report export, and no explicit apply/rollback step (intentional for a read-only server), all of which an agent can work around.