Dependency Drift Mcp

Summarizes drift between local dependency manifests and lockfiles without exposing package names.

What you can do

This local MCP server inspects dependency manifests and lockfiles in a project and reports on drift between them. According to its registry description, it summarizes that drift without returning package names, so the assistant sees counts and status rather than the dependency list itself. No individual tools are listed in the manifest.

When to use it

Useful when you want an assistant to check whether a project's declared dependencies and its lockfile have fallen out of sync, and you would rather not hand over the actual package names. Best suited to local, desktop-based development workflows.

Requirements

Runs as a local process over stdio, installed from the npm package dependency-drift-mcp, so Node.js and npm are needed. It is desktop-only and not web-executable. No authentication, environment variables, or headers are declared.