depquiet
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.
depquiet triages dependency vulnerability alerts and plans the change that closes them, verified with the project's own resolver (uv or Poetry) on a temporary copy. Use triage_alerts to see which alerts matter, then plan_fixes for the exact diff and lock command. Neither tool edits the project: show the user the plan, and apply the diff or run the command only when they agree. Raising requires-python drops Python versions; ask before passing raise_python_floor=true.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| triage_alertsA | Scan a project's locked dependencies for known vulnerabilities and sort every alert into action (fix now), review (worth a look, not urgent) or filtered (deprioritized: dev-only, test-only...), with the reasons. Use it first, to see which alerts matter; then call plan_fixes for the change that closes them. Works on Python (uv, Poetry, pip requirements) and JavaScript (npm, pnpm) projects. Read-only: runs pip-audit or the package manager's audit, which query their advisory databases over the network, plus EPSS and CISA KEV lookups unless offline=true. |
| plan_fixesA | Work out the change that closes a project's action alerts and check it with the project's own resolver (uv lock --dry-run, or Poetry) on a temporary copy. Returns the requirement edits as a unified diff, the lock command to run, every version the lock moves (downgrades included), the alerts left out and why, and whether raising requires-python would unblock more fixes. Use it after triage_alerts reports action alerts; only uv and Poetry projects get a plan (for others it explains why there is none). Read-only: never edits or relocks the project; show the user the plan and apply the diff only when they agree. Needs network access, and resolving can build source distributions and take a few minutes on large projects. |
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 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.