Dependency MCP Server

npm dependency fitness: deprecated/yanked/superseded + verified safe migration target.

Local serverstdio

What is the Dependency MCP server?

npm dependency fitness: deprecated/yanked/superseded + verified safe migration target. That is what the dependency mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

An MCP server that gives a coding agent a cross-validated fitness verdict for an npm package before it writes or upgrades a dependency:

  • Migration-target inference. — When a package is deprecated, it parses the
  • Cross-validation, not a guess. — It reconciles deprecation across the npm
  • It refuses to guess. — If a package is deprecated but no successor can be
  • Anti-slopsquatting. — A non-existent / hallucinated package name returns a

The tools it exposes

The server publishes 2 tools. What each one is for:

  • check_package_fitness — Single-package verdict. Input: package (e.g. request, @babel/core), optional version (exact, semver range, or dist-tag — omit for latest). Output
  • audit_dependencies — Batch verdict for a CI / pre-merge gate. Input: packages (e.g. ["react@18.2.0", "request"]) and/or the raw contents of a package.json. Output: a

Getting it running

Installation goes through your MCP client rather than a global install: point it at dependency-fitness-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

What it needs from you

Configuration is passed through the environment: GITHUB_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

How it compares

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Dependency's toolset — check_package_fitness, audit_dependencies — is a fair guide to whether it matches your workflow. It is maintained by TweedBeetle; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
check_package_fitnessSingle-package verdict. Input: package (e.g. request, @babel/core), optional version (exact, semver range, or dist-tag — omit for latest). Output: the full Verdict (structured) plus a human-readable summary.
audit_dependenciesBatch verdict for a CI / pre-merge gate. Input: packages (e.g. ["react@18.2.0", "request"]) and/or the raw contents of a package.json. Output: a per-package verdict array plus a summary (how many deprecated / malicious /

How to install the Dependency MCP server

{
  "mcpServers": {
    "dependency-fitness": {
      "command": "npx",
      "args": ["-y", "dependency-fitness-mcp"],
      "env": {
        "GITHUB_TOKEN": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
GITHUB_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use Dependency to check package fitness.
  • Use Dependency to audit dependencies.

Frequently asked questions

It connects Dependency to MCP-compatible AI assistants such as Claude and Cursor, exposing 2 tools (check_package_fitness, audit_dependencies) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Dependency directly.