# io.github.TweedBeetle/dependency-fitness-mcp (npm · dependency-fitness-mcp)

npm dependency fitness: deprecated/yanked/superseded + verified safe migration target.

- Trust score: 68/100 (medium)
- Change this week: +24
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `dependency-fitness-mcp`: 68/100 (this document), [markdown](https://verifymcp.io/servers/tweedbeetle-dependency-fitness-mcp/dependency-fitness-mcp.md), [page](https://verifymcp.io/servers/tweedbeetle-dependency-fitness-mcp/dependency-fitness-mcp)

## Channel facts

- Registry: `npm`
- Package: `dependency-fitness-mcp`
- Version: `0.1.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 55 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add tweedbeetle-dependency-fitness-mcp -- npx -y dependency-fitness-mcp
```

### Codex

```bash
codex mcp add tweedbeetle-dependency-fitness-mcp -- npx -y dependency-fitness-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tweedbeetle-dependency-fitness-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "dependency-fitness-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add tweedbeetle-dependency-fitness-mcp --command npx --arg -y --arg dependency-fitness-mcp
```

### Hermes

```yaml
mcp_servers:
  tweedbeetle-dependency-fitness-mcp:
    command: "npx"
    args: ["-y", "dependency-fitness-mcp"]
```

### Other

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 68, +44)

- [security regression] Provenance: unverified → fail
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Install scripts: unverified → pass
- [security improvement] 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.
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Security disclosure: fail → unverified
- [functional regression] Capabilities: pass → unverified
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Stability: unverified → 0.23
- [functional improvement] License: unverified → pass
- [functional improvement] Schema quality: unverified → excellent
- [functional] Licence: MIT

### 2026-08-01 (score 24, +19)

- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Tool coverage: unverified → 100

### 2026-07-31 (score 5, −21)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 26, −18)

- [security regression] Malware scan: pass → unverified

### 2026-07-27 (score 44)

First indexed and scored.

## MCP tools (2)

### `check_package_fitness` (~149 tokens)

Check npm package fitness

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.

Input parameters:

- `package` (string, required): npm package name, e.g. 'request' or '@babel/core'
- `version` (string): Exact version, semver range, or dist-tag. Omit to check the current 'latest'.

Output parameters:

- `advisories` (array)
- `agreement` (object)
- `confidence` (string)
- `deprecated` (boolean)
- `deprecated_reason`
- `ecosystem` (string)
- `exists` (boolean)
- `last_verified` (string)
- `malicious` (boolean)
- `package` (string)
- `queried_version`
- `resolved_version`
- `safe_migration_target`
- `signals` (object)
- `sources_consulted` (array)
- `superseded_by`
- `warnings` (array)
- `yanked` (boolean)

### `audit_dependencies` (~139 tokens)

Audit npm dependencies

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. ['react@18.2.0', 'request']) and/or the raw contents of a package.json. Ideal for a CI / pre-merge dependency gate. Capped at 50 packages per call.

Input parameters:

- `package_json` (string): Raw package.json contents; all dependency sections are extracted.
- `packages` (array): Package specs, e.g. ['lodash@^4', '@babel/core', 'request@2.88.2'].

Output parameters:

- `results` (array)
- `summary` (object)
- `truncated` (number)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/tweedbeetle-dependency-fitness-mcp/dependency-fitness-mcp#diagnostics

## Score history

- 2026-08-03: 68
- 2026-08-02: 68
- 2026-08-01: 24
- 2026-07-31: 5
- 2026-07-30: 26
- 2026-07-28: 44
- 2026-07-27: 44

## Links

- npm package: https://www.npmjs.com/package/dependency-fitness-mcp
- Socket report: https://socket.dev/npm/package/dependency-fitness-mcp
- Repository: https://github.com/TweedBeetle/dependency-fitness-mcp
- Changelog RSS feed: https://verifymcp.io/servers/tweedbeetle-dependency-fitness-mcp/dependency-fitness-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/tweedbeetle-dependency-fitness-mcp/dependency-fitness-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/tweedbeetle-dependency-fitness-mcp/dependency-fitness-mcp