Dependency Fitness Mcp
Scan npm dependencies for deprecated, yanked, or superseded packages and get verified safe migration targets before release.
Overview
dependency-fitness-mcp is a MCP server for the Ship phase that audits npm dependency health and recommends verified safe migration targets.
What is this MCP server?
- Flags npm packages that are deprecated, yanked, or superseded
- Suggests verified safe migration targets instead of blind major bumps
- stdio npm dependency-fitness-mcp v0.1.1 for agent-driven audits
- Fits pre-ship review loops in Claude Code or Cursor monorepos
- Server version 0.1.1
- npm package identifier dependency-fitness-mcp
- Repository: github.com/TweedBeetle/dependency-fitness-mcp
What problem does it solve?
Indie maintainers miss yanked or superseded npm packages until production breaks or security advisories land.
Who is it for?
Solo Node/TypeScript builders who want agent-assisted dependency hygiene before every release.
Skip if: Teams on non-npm ecosystems (Maven-only, pure Python pip workflows without npm).
What do I get? / Deliverables
After install, agents can list unfit dependencies and migration targets during ship security reviews.
- Fitness report for deprecated, yanked, and superseded dependencies
- Agent-actionable safe migration recommendations per package
Recommended MCP Servers
Journey fit
How it compares
npm supply-chain fitness MCP, not a full SAST or container scanner skill.
Common Questions / FAQ
Who is dependency-fitness-mcp for?
Solo builders and small teams shipping npm-based apps who want MCP-driven checks for deprecated and yanked dependencies.
When should I use dependency-fitness-mcp?
Use it in Ship security before releases or after large dependency updates to confirm safe migration paths.
How do I add dependency-fitness-mcp to my agent?
Add stdio MCP config for npm package dependency-fitness-mcp v0.1.1 in Claude Code or Cursor, run from your project root, and follow tool output for migrations.