io.github.niradler/dependency-mcp
NPM · DEPENDENCY-MCP · SCANNED AUG 3
MCP server for checking package versions across multiple package managers
Available components
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 →
Supply Chain Security70
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 0.5.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (19 of 20), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency44
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 277 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 469 tokens (~78/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · dependency-mcp
claude mcp add niradler-dependency-mcp -- npx -y dependency-mcp
codex mcp add niradler-dependency-mcp -- npx -y dependency-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"niradler-dependency-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"dependency-mcp"
],
"enabled": true
}
}
} openclaw mcp add niradler-dependency-mcp --command npx --arg -y --arg dependency-mcp
mcp_servers:
niradler-dependency-mcp:
command: "npx"
args: ["-y", "dependency-mcp"] {
"mcpServers": {
"niradler-dependency-mcp": {
"command": "npx",
"args": [
"-y",
"dependency-mcp"
]
}
}
} 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.
- 3 Aug 26 +4
- Stability: unverified → 0.23 ▲ functional
- 2 Aug 26 +12
- Malware scan: unverified → pass ▲ security
- 1 Aug 26 +12
- Known CVEs: unverified → fail ▼ security
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- License: unverified → pass ▲ functional
- Licence: MIT functional
- 31 Jul 26 −23
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 +47
- CVE-2025-66414 affects this package: high ▼ security
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Security disclosure: unverified → fail ▼ functional
- Maintenance: unverified → pass ▲ functional
- License: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: pass functional
- First check of Schema quality: excellent functional
- First check of Schema quality: fail functional
- Licence: MIT functional
- 26 Jul 26 26
First indexed and scored.
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-w48q-cv73-mx4w | CVE-2025-66414 | high | yes |
Dependencies 19 packages
19 packages in the resolved dependency tree · 19 deprecated · 9 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
check_version_exists ~80
Check if a specific version exists. Use for dependency validation, CI/CD checks, or ensuring version compatibility. Returns whether the version exists with package details and timestamp.
| Name | Type | Req | Description |
|---|---|---|---|
| package_name | string | yes | Name of the package to check |
| registry | string | yes | Package registry/manager to check |
| version | string | yes | Version to check for existence |
No output schema declared.
No examples provided.
check_versions_exist ~77
Check if specific versions exist for multiple packages. Use for bulk dependency validation, CI/CD pipeline checks, or ensuring multiple package version compatibility. Processes up to 100 packages in parallel with individual error handling.
| Name | Type | Req | Description |
|---|---|---|---|
| packages | array | yes | Array of package objects with name and version |
| registry | string | yes | Package registry/manager to check |
No output schema declared.
No examples provided.
get_latest_version ~74
Get the latest version of a package. Use for dependency updates, version checks, or when you need the most recent stable release. Returns package name, latest version, description, and timestamp.
| Name | Type | Req | Description |
|---|---|---|---|
| package_name | string | yes | Name of the package to check |
| registry | string | yes | Package registry/manager to check |
No output schema declared.
No examples provided.
get_latest_versions ~79
Get latest versions for multiple packages simultaneously. Use when checking 3+ dependencies - processes up to 100 packages in parallel. Returns individual results for each package with error isolation. Much faster than individual calls for multiple packages.
| Name | Type | Req | Description |
|---|---|---|---|
| packages | array | yes | Array of package names to check |
| registry | string | yes | Package registry/manager to check |
No output schema declared.
No examples provided.
get_package_info ~75
Get detailed package information including all versions. Use for dependency audits, security reviews, or when you need comprehensive package metadata. Returns versions list, homepage, repository, and full package details.
| Name | Type | Req | Description |
|---|---|---|---|
| package_name | string | yes | Name of the package to get info for |
| registry | string | yes | Package registry/manager to check |
No output schema declared.
No examples provided.
get_packages_info ~84
Get comprehensive package details for multiple packages. Use for dependency audits, security reviews, or bulk package analysis. Processes up to 100 packages in parallel. Returns detailed info for each package with error isolation - failed packages don't break the batch.
| Name | Type | Req | Description |
|---|---|---|---|
| packages | array | yes | Array of package names to get info for |
| registry | string | yes | Package registry/manager to check |
No output schema declared.
No examples provided.