MCP Dependency Doctor MCP server
Read-only npm dependency diagnostics for AI coding agents.
0 stars
Reviews
Write oneNobody has reviewed MCP Dependency Doctor yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
MCP Dependency Doctor tools (4, 1 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
dependency_auditwrite actionRun read-only npm audit. Sends package versions to the configured npm registry. Never installs or fixes packages.
dependency_inventoryRead declared dependencies and exact installed versions from npm lockfile v2/v3. No network.
dependency_outdatedRead available updates using npm outdated. Requires network; never changes dependencies.
package_healthInspect public npm package deprecation, release age, Node engine and peer requirements. Requirements are reported, not certified compatible.
Public scan report
scanner v0.1.10 · 2026-10-09 · same rubric, same numbers if you re-run it
- Code scan5 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 0 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Install MCP Dependency Doctor in Claude Code, Cursor or VS Code
Runs npx -y mcp-dependency-doctor on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add mcp-dependency-doctor -- npx -y mcp-dependency-doctor
What the publisher says
From the MCP Dependency Doctor repository's README, as published. We do not edit it. Read it on GitHub
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
claude mcp add dependency-doctor -- npx -y mcp-dependency-doctorCodex CLI
codex mcp add dependency-doctor -- npx -y mcp-dependency-doctorClaude Desktop, Cursor, Windsurf, Cline, Gemini CLI — add to the client's MCP config (claudedesktopconfig.json, ~/.cursor/mcp.json, ~/.codeium/windsurf/mcp_config.json, Cline MCP settings, ~/.gemini/settings.json):
{
"mcpServers": {
"dependency-doctor": {
"command": "npx",
"args": [
"-y",
"mcp-dependency-doctor"
]
}
}
}VS Code / GitHub Copilot — .vscode/mcp.json:
{
"servers": {
"dependency-doctor": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"mcp-dependency-doctor"
]
}
}
}Zed — settings.json:
{
"context_servers": {
"dependency-doctor": {
"command": "npx",
"args": [
"-y",
"mcp-dependency-doctor"
]
}
}
}Run from source
git clone https://github.com/petrovicistefan/mcp-dependency-doctor.git
cd mcp-dependency-doctor
npm test
MCP_PROJECT_ROOT=/absolute/path/to/your/project node src/server.jsnpm publication is pending. This implementation has no third-party runtime dependencies.
Claude Desktop / compatible stdio client
{
"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
Project tools accept projectPath, relative to MCPPROJECTROOT. 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.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
MCP Dependency Doctor: common questions
- Is MCP Dependency Doctor MCP server safe?
- Yes, by our scan: it is graded A (92/100). Read the MCP Dependency Doctor safety report
- How do I install MCP Dependency Doctor?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does MCP Dependency Doctor need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is MCP Dependency Doctor maintained?
- The last commit was 4 days ago (2026-10-09). The latest release is v0.1.1.