MCP Dependency Doctor
NPM · MCP-DEPENDENCY-DOCTOR
Read-only npm dependency diagnostics for AI coding agents.
Available components
Last scanned (13 hours ago)
Scores higher than 48% of npm servers
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to petrovicistefan/mcp-dependency-doctor). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 9 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability62
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 143 tokens (~35/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 14 Oct 26 +27
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Tool coverage: 0 functional
- First check of Schema quality: fail functional
- First check of Schema quality: fair functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- 12 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- Security disclosure: unverified → fail ▼ functional
- 11 Oct 26 34
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 18 Oct 2026 · Analysed npm/mcp-dependency-doctor@0.1.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | petrovicistefan/mcp-dependency-doctor |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/petrovicistefan/mcp-dependency-doctor/.github/workflows/release.yml@refs/tags/v0.1.1 |
| Rekor log index | 3151714570 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:a64ee2d050eee21a203b15d79a81572953545eab97f64f81cc0d284358eef1123a94907e28d9bf6a8da040d1dc77cfd74b8b4be02446d128c47432af2 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
dependency_audit ~38
Run read-only npm audit. Sends package versions to the configured npm registry. Never installs or fixes packages.
| Name | Type | Req | Description |
|---|---|---|---|
| projectPath | string | – | – |
No output schema declared.
No examples provided.
dependency_inventory ~35
Read declared dependencies and exact installed versions from npm lockfile v2/v3. No network.
| Name | Type | Req | Description |
|---|---|---|---|
| projectPath | string | – | – |
No output schema declared.
No examples provided.
dependency_outdated ~31
Read available updates using npm outdated. Requires network; never changes dependencies.
| Name | Type | Req | Description |
|---|---|---|---|
| projectPath | string | – | – |
No output schema declared.
No examples provided.
package_health ~39
Inspect public npm package deprecation, release age, Node engine and peer requirements. Requirements are reported, not certified compatible.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
How do I install the MCP Dependency Doctor server?
MCP Dependency Doctor runs locally as an npm package, launched with npx -y mcp-dependency-doctor. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcp-dependency-doctor
claude mcp add petrovicistefan-mcp-dependency-doctor -- npx -y mcp-dependency-doctor
What is the MCP Dependency Doctor server?
MCP Dependency Doctor is listed in the public MCP registry as io.github.petrovicistefan/mcp-dependency-doctor. Read-only npm dependency diagnostics for AI coding agents. This page covers its npm package (mcp-dependency-doctor).
Is the MCP Dependency Doctor server safe to use?
MCP Dependency Doctor scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 18 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the MCP Dependency Doctor server expose?
MCP Dependency Doctor exposes 4 tools: dependency_inventory, dependency_audit, dependency_outdated, package_health. Their descriptions and schemas cost roughly 143 tokens of context every time the server is loaded.
Is the MCP Dependency Doctor server still maintained?
MCP Dependency Doctor is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the MCP Dependency Doctor server under?
MCP Dependency Doctor declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.