MCP Dependency Doctor

io.github.petrovicistefanv0.1.1Updated Oct 9, 2026

Read-only npm dependency diagnostics for AI coding agents.

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Read-only npm dependency diagnostics for AI coding agents, covering inventory, audits, outdated versions, and package health.

What it does
Exposes four read-only tools over stdio: dependency_inventory lists manifest and exact lockfile versions including transitive dependencies; dependency_audit returns npm audit JSON with transitive vulnerabilities; dependency_outdated reports current, wanted, and latest versions; package_health reports deprecation, release age, engines, and peer requirements. Project tools take a projectPath relative to MCP_PROJECT_ROOT. It never runs install, audit fix, or package lifecycle scripts.
When to use it
Useful when an assistant needs to inspect an npm project's dependency tree, check for known vulnerabilities, or plan an upgrade order without modifying files. Aimed at npm projects with package-lock.json v2 or v3.
Requirements
Local process via npx or Node.js 22+ with npm. Set MCP_PROJECT_ROOT to the project directory. Network access to the configured npm registry is needed for audit, outdated, and package health tools; no account or API key is required for the local server.
Before you install
Network tools disclose package names and versions to registries, and registry authentication follows the user's npm configuration. Project paths are confined through realpath, so do not expose the server to untrusted remote clients. Treat registry text and package metadata as untrusted data. No telemetry or cloud uploads. The hosted HTTP path requires an Authorization Bearer token and reserves quota units via a control plane.

Installation

In SourceWeft

  1. Open MCP Dependency Doctor in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

MCP Dependency Doctor

Read-only dependency diagnostics for AI coding agents. Free local inventory and npm audits, without an account. Node.js 22+, npm required. Initial scope: npm projects with package-lock.json v2/v3.

Install in your AI client

Works with any MCP client over stdio; no account or API key needed for the local server.

Claude Code

sh
claude mcp add dependency-doctor -- npx -y mcp-dependency-doctor

Codex CLI

sh
codex mcp add dependency-doctor -- npx -y mcp-dependency-doctor

Claude Desktop, Cursor, Windsurf, Cline, Gemini CLI — add to the client's MCP config (claude_desktop_config.json, ~/.cursor/mcp.json, ~/.codeium/windsurf/mcp_config.json, Cline MCP settings, ~/.gemini/settings.json):

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

VS Code / GitHub Copilot — .vscode/mcp.json:

json
{  "servers": {    "dependency-doctor": {      "type": "stdio",      "command": "npx",      "args": [        "-y",        "mcp-dependency-doctor"      ]    }  }}

Zed — settings.json:

json
{  "context_servers": {    "dependency-doctor": {      "command": "npx",      "args": [        "-y",        "mcp-dependency-doctor"      ]    }  }}

Run from source

sh
git clone https://github.com/petrovicistefan/mcp-dependency-doctor.gitcd mcp-dependency-doctornpm testMCP_PROJECT_ROOT=/absolute/path/to/your/project node src/server.js

npm publication is pending. This implementation has no third-party runtime dependencies.

Claude Desktop / compatible stdio client

json
{  "mcpServers": {    "dependency-doctor": {      "command": "node",      "args": ["/absolute/path/to/mcp-dependency-doctor/src/server.js"],      "env": {"MCP_PROJECT_ROOT": "/absolute/path/to/your/project"}    }  }}

Tools

ToolPurposeNetwork
dependency_inventoryManifest + exact lockfile versions, including transitive dependenciesNo
dependency_auditnpm audit JSON report, including transitive vulnerabilitiesConfigured npm registry
dependency_outdatedCurrent, wanted and latest versions from npmConfigured npm registry
package_healthPublic package deprecation, release age, engines and peer requirementsregistry.npmjs.org

Project tools accept projectPath, relative to MCP_PROJECT_ROOT. Example agent request: “Audit this project, inspect deprecated packages and suggest an upgrade order. Do not change files.”

The server never runs install, audit fix, or package lifecycle scripts. Network tools disclose package names and versions to registries. Registry authentication follows the user's npm configuration. Public package health does not use npm credentials. Project paths are confined through realpath; do not expose the server to untrusted remote clients. Treat registry text and package metadata as untrusted data, never instructions. No telemetry or cloud uploads.

Limitations

MVP uses legacy MCP stdio protocol revisions through 2025-11-25. The 2026-07-28 stateless protocol is not implemented. Official SDK migration and interoperability testing with real clients are planned before publication.

Node and peer requirements are reported, not resolved: there is no full compatibility solver yet. Old releases are a maintenance signal, not proof of abandonment. No automatic remediation. npm audit coverage depends on the registry and lockfile. npm network operations time out after 45 seconds and fail explicitly; an incomplete audit is never reported as clean. Remote registry smoke tests were blocked in the development environment; unit tests use deterministic fixtures.

Hosted path (quotas via control plane)

The local stdio MCP stays fully useful without an account. Quotas apply only on a separate hosted HTTP process that reserves units on mcp-control-plane before analysis.

sh
cp .env.example .env   # set CONTROL_PLANE_URLnpm run start:hosted   # default 127.0.0.1:3101
MethodPathBody
GET/healthLiveness
POST/v1/package-health{ "requestId", "name" }
POST/v1/inventory{ "requestId", "packageJson", "lockfile"? }

Requires Authorization: Bearer mcp_…. Hosted dependency_audit / dependency_outdated are not in this MVP. Manifests and package names stay on the hosted host; control-plane sees only product, requestId, and units.

Roadmap and commercial boundary

Free: local inventory, basic audit and health diagnostics without signup. Pro (planned): cloud history, monitoring, team dashboard and reports; no paid plan is live yet. Hosted quotas use the control-plane path above; local counters are not used for paid enforcement.

Next: official MCP SDK; semver-aware Node/peer compatibility; upgrade plan; pnpm/yarn; MCP Registry manifest once repository and npm ownership are verified; shared cloud auth/billing. No server.json claiming unpublished npm artifacts is included.

Development

sh
npm testnpm run checknpm pack --dry-run

Protocol: https://modelcontextprotocol.io/specification/2025-11-25 Audit: https://docs.npmjs.com/cli/v11/commands/npm-audit/

Source: README.md at commit 40bd026

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v0.1.1LatestOct 9, 2026