io.github.TweedBeetle/dependency-fitness-mcp
NPM · DEPENDENCY-FITNESS-MCP · SCANNED SEP 22
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 → Why this is hard to score →
Supply Chain Security98
- 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
- 31 of 96 dependencies flagged as unhealthy. 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 105 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
How do I install the io.github.TweedBeetle/dependency-fitness-mcp server?
io.github.TweedBeetle/dependency-fitness-mcp runs locally as an npm package, launched with npx -y dependency-fitness-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · dependency-fitness-mcp
claude mcp add tweedbeetle-dependency-fitness-mcp -- npx -y dependency-fitness-mcp
{
"mcpServers": {
"tweedbeetle-dependency-fitness-mcp": {
"command": "npx",
"args": [
"-y",
"dependency-fitness-mcp"
]
}
}
} {
"servers": {
"tweedbeetle-dependency-fitness-mcp": {
"command": "npx",
"args": [
"-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": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"dependency-fitness-mcp"
]
}
}
} assistant mcp add tweedbeetle-dependency-fitness-mcp -t stdio -c npx -a -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.
- 22 Sept 26 +1
- Stability: 0.97 → pass security
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 16 Sept 26 −3
- Security disclosure: fail → unverified ▼ functional
- Stability: pass → 0.80 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 0
- Security disclosure: fail → unverified ▼ 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 22 Sept 2026 · Analysed npm/dependency-fitness-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| 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 →
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. ['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.
| 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', 'request@2.88.2']. |
| 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 | string|null | yes | – |
| ecosystem | string | yes | – |
| exists | boolean | yes | – |
| last_verified | string | yes | – |
| malicious | boolean | yes | – |
| package | string | yes | – |
| queried_version | string|null | yes | – |
| resolved_version | string|null | yes | – |
| safe_migration_target | – | yes | – |
| signals | object | yes | – |
| sources_consulted | array | yes | – |
| superseded_by | – | yes | – |
| warnings | array | yes | – |
| yanked | boolean | yes | – |
No examples provided.
What is the io.github.TweedBeetle/dependency-fitness-mcp server?
io.github.TweedBeetle/dependency-fitness-mcp is listed in the public MCP registry as io.github.TweedBeetle/dependency-fitness-mcp. npm dependency fitness: deprecated/yanked/superseded + verified safe migration target. This page covers its npm package (dependency-fitness-mcp).
Is the io.github.TweedBeetle/dependency-fitness-mcp server safe to use?
io.github.TweedBeetle/dependency-fitness-mcp scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 2026. It declares no install or post-install scripts. 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 io.github.TweedBeetle/dependency-fitness-mcp server expose?
io.github.TweedBeetle/dependency-fitness-mcp exposes 2 tools: check_package_fitness, audit_dependencies. Their descriptions and schemas cost roughly 288 tokens of context every time the server is loaded.
Is the io.github.TweedBeetle/dependency-fitness-mcp server still maintained?
io.github.TweedBeetle/dependency-fitness-mcp is still listed as active in the MCP registry. We last reached this channel on 22 September 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 io.github.TweedBeetle/dependency-fitness-mcp server under?
io.github.TweedBeetle/dependency-fitness-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.