What it does
freshcheck assesses how stale a dependency tree is. For each dependency it compares the installed version with the latest available version, component by component, and reports a behind level of major, minor, patch or none. A dependency counts as abandoned when its repository is archived or when it has gone a set number of days without a release. Abandonment takes precedence over the version gap, but the behind level is still reported.
Someone maintaining a project could use it to sort outdated packages into the groups abandoned, major, minor, patch and current. The result lists the names in each group, the group sizes and the total, sorted so that the same input always gives the same output. It can be run as a CLI that reads an arguments file and prints JSON, or used as an MCP server exposing an assess_freshness tool.
The caller supplies the dependency list: each entry has a name, a current version and a latest version, with optional archived and days_since_last_release fields. abandoned_days defaults to 730 and defaults to archived as false. The CLI exits with 0 on success, 1 on a runtime error and 2 on a usage error.
Limitations and requirements
Versions must be strict MAJOR.MINOR.PATCH semver: three numeric components, no leading zeros, and no prerelease or build suffix. Malformed input, including a missing or empty dependency list, a missing, empty or duplicate name, a non-strict version or a wrongly typed signal, is rejected with a validation error and no partial assessment is produced. The tool performs no network or registry lookups and judges only the versions and signals supplied.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
io.github.CloudCorpRecords/freshcheck
Assess dependency staleness: behind level per dependency, grouped by risk from abandoned to current.
v0.1.0As shown on registry.modelcontextprotocol.io when we last read it