fresh-deps-mcp
# claude-mcp-build
MCP servers that make Claude better at finishing real projects.
| Package | What it does |
|---|---|
| [**finishline-mcp**](packages/finishline) | A project manager that gets projects shipped: kickoff interview, one next action, scope-creep guard, stall detection, ship check, live visual dashboard. |
| [**fresh-deps-mcp**](packages/fresh-deps) | Live package versions, deprecations and vulnerabilities (npm, PyPI, crates.io, Go) so Claude stops installing outdated or vulnerable packages. Also powers finishline's dependency check. |
Install finishline as a Claude Code plugin (MCP server + session-start hook):
```
/plugin marketplace add hyunaeee/claude-mcp-build
/plugin install finishline@hyunaeee-mcp
```
Development:
```bash
npm install
npm run build
npm run smoke
```
Behind a corporate proxy, set `NODE_USE_ENV_PROXY=1` so Node's `fetch` uses `HTTPS_PROXY`.
TDQS
Scored across 2 tools
latest_version targets a single package's current version and advisories, while check_deps audits an entire manifest for outdated, deprecated, and vulnerable dependencies. The input scopes and intended workflows are clearly distinct, so an agent should not confuse them.
Both names use snake_case and are concise, but latest_version is a noun phrase while check_deps follows a verb_noun pattern. This is a minor deviation in an otherwise readable set.
Only two tools are provided, which is below the typical 3-15 range, but they map cleanly to the server's two core workflows: single-package lookup and manifest auditing. The count is slightly thin but reasonable for this narrow purpose.
The surface covers the core dependency-freshness needs: checking a package's latest stable version plus advisories, and auditing a manifest for outdated, deprecated, and vulnerable dependencies with upgrade targets. Minor gaps exist, such as no direct scan of an installed environment or arbitrary bulk package list, but agents can work around these via manifests and repeated lookups.