Dependency Drift MCP Server

by mrfentmen Your server? Claim it

local only

Dependency Drift MCP runs on your own machine — the client starts it, so there is no endpoint to ping.

Summarize local dependency manifest and lockfile drift without returning package names,...

The linked repository no longer exists on GitHub — it was deleted or made private.

—

Installs / week

npm · dependency-drift-mcp

—

Stars

on GitHub

—

Last commit

0 releases in 90 days

—

License

language unknown

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add dependency-drift-mcp -- npx -y dependency-drift-mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "dependency-drift-mcp": {
      "args": [
        "-y",
        "dependency-drift-mcp"
      ],
      "command": "npx"
    }
  }
}

~/.codex/config.toml

[mcp_servers.dependency-drift-mcp]
command = "npx"
args = ["-y", "dependency-drift-mcp"]

.cursor/mcp.json

{
  "mcpServers": {
    "dependency-drift-mcp": {
      "args": [
        "-y",
        "dependency-drift-mcp"
      ],
      "command": "npx"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "dependency-drift-mcp": {
      "args": [
        "-y",
        "dependency-drift-mcp"
      ],
      "command": "npx"
    }
  }
}

Alternatives to Dependency Drift MCP

same job, measured the same way

License Boundary MCP

by mrfentmen

Summarize local license evidence and uncertainty without returning package names, license text,...

local only

Runtime Support MCP

by mrfentmen

Summarize runtime declarations across local manifests and CI files without returning versions,...

local only

Lockstep MCP

by mrfentmen

Local lockfile and package-manager reproducibility analysis without dependency details. Tools...

local only

Incident Timeline MCP

by mrfentmen

Summarize local log timeline gaps and severity counts without returning messages, IDs, paths, or...

local only

Build Cache MCP

by mrfentmen

Summarize local build and cache footprint using size and age buckets without returning paths or...

local only

Dependency License Change MCP

by mrfentmen

Compare local license evidence across two snapshots without returning package names, text,...

local only

Release Notes Forge MCP

by mrfentmen

Summarize local Git release shape without returning commit messages, paths, hashes, or remotes.

local only

API Deprecation Radar MCP

by mrfentmen

Count local API deprecation markers by broad severity without returning endpoint names, paths,...

local only

Dependency Drift MCP — questions

Answers built from our own checks of this server.

Why is there no uptime for Dependency Drift MCP?

Dependency Drift MCP runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package dependency-drift-mcp.

Is Dependency Drift MCP still maintained?

The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.

How do I connect Dependency Drift MCP?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It runs locally, so the command pulls dependency-drift-mcp straight from npm; nothing to host, nothing to sign up for.