io.github.TweedBeetle/dependency-fitness-mcp
NPM · DEPENDENCY-FITNESS-MCP · SCANNED AUG 3
npm dependency fitness: deprecated/yanked/superseded + verified safe migration target.
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 Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- 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 55 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 400 tokens (~200/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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-fitness-mcp
claude mcp add tweedbeetle-dependency-fitness-mcp -- npx -y dependency-fitness-mcp
codex mcp add tweedbeetle-dependency-fitness-mcp -- npx -y dependency-fitness-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"tweedbeetle-dependency-fitness-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"dependency-fitness-mcp"
],
"enabled": true
}
}
} openclaw mcp add tweedbeetle-dependency-fitness-mcp --command npx --arg -y --arg dependency-fitness-mcp
mcp_servers:
tweedbeetle-dependency-fitness-mcp:
command: "npx"
args: ["-y", "dependency-fitness-mcp"] {
"mcpServers": {
"tweedbeetle-dependency-fitness-mcp": {
"command": "npx",
"args": [
"-y",
"dependency-fitness-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.
- 2 Aug 26 +44
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Tool coverage: 100 → unverified ▼ functional
- Security disclosure: fail → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Stability: unverified → 0.23 ▲ functional
- License: unverified → pass ▲ functional
- Schema quality: unverified → excellent ▲ functional
- Licence: MIT functional
- 1 Aug 26 +19
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 31 Jul 26 −21
- 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 44
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 95 packages
95 packages in the resolved dependency tree · 95 deprecated · 29 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.
audit_dependencies Audit npm dependencies ~139
Audit many npm dependencies at once and return a per-package fitness verdict plus a summary (how many are deprecated / malicious / vulnerable / behind). Accepts a list of package specs (e.g. ['[email protected]', 'request']) and/or the raw contents of a package.json. Ideal for a CI / pre-merge dependency gate. Capped at 50 packages per call.
| Name | Type | Req | Description |
|---|---|---|---|
| package_json | string | — | Raw package.json contents; all dependency sections are extracted. |
| packages | array | — | Package specs, e.g. ['lodash@^4', '@babel/core', '[email protected]']. |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | — |
| summary | object | yes | — |
| truncated | number | yes | — |
No examples provided.
check_package_fitness Check npm package fitness ~149
Return a cross-validated fitness verdict for an npm package: is it deprecated / yanked / superseded / malicious, and if so what is the safe migration target. Unlike a plain 'is it deprecated' lookup, this reconciles the npm registry, deps.dev, OSV and GitHub into one confidence-scored answer, infers a safe replacement when one exists, and flags disagreement instead of guessing. Also detects non-existent / hallucinated package names.
| Name | Type | Req | Description |
|---|---|---|---|
| package | string | yes | npm package name, e.g. 'request' or '@babel/core' |
| version | string | — | Exact version, semver range, or dist-tag. Omit to check the current 'latest'. |
| Name | Type | Req | Description |
|---|---|---|---|
| advisories | array | yes | — |
| agreement | object | yes | — |
| confidence | string | yes | — |
| deprecated | boolean | yes | — |
| deprecated_reason | — | yes | — |
| ecosystem | string | yes | — |
| exists | boolean | yes | — |
| last_verified | string | yes | — |
| malicious | boolean | yes | — |
| package | string | yes | — |
| queried_version | — | yes | — |
| resolved_version | — | yes | — |
| safe_migration_target | — | yes | — |
| signals | object | yes | — |
| sources_consulted | array | yes | — |
| superseded_by | — | yes | — |
| warnings | array | yes | — |
| yanked | boolean | yes | — |
No examples provided.