
Freshcheck
io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 3, 2026
Assess dependency staleness: behind level per dependency, grouped by risk from abandoned to current.
Overview
Freshcheck's local MCP server; no sign-in required; STDIO.
No AI overview yet: these facts come from the registry entry and the server itself.
Installation
In SourceWeft
- Open Freshcheck in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
freshcheck
A dependency tree quietly ages. Some packages are a patch behind and can be bumped without a thought, some are a major version behind and need a planned upgrade, and some have not released anything in years — or their repository has been archived outright — and are a risk whatever version they are on. freshcheck takes the tree you have — each dependency's name, installed version, and latest available version, with optional abandonment signals — and sorts it into exactly those risk groups:
- Behind level — for every dependency,
currentandlatestare compared component by component, numerically. The first component that differs decides:major,minor, orpatch. Whenlatestis not ahead ofcurrent— equal, or even behind it — the level isnone. Versions must be strictMAJOR.MINOR.PATCHsemver: three numeric components, no leading zeros, no prerelease or build suffix. - Abandoned — a dependency counts as abandoned when
its repository is archived, or when it has gone at least
abandoned_dayswithout a release (default 730, measured by the optionaldays_since_last_release). Abandonment outranks the version gap: an archived package two majors behind is groupedabandoned, with its behind level still reported alongside so the size of the gap is not lost. - Groups and counts — every dependency lands in one
group —
abandoned,major,minor,patch, orcurrent(behind levelnone, not abandoned) — and the result carries the names in each group plus the group sizes and the overall total.
Every list in the result is sorted ascending, so the same
tree always yields exactly the same assessment. Malformed
input — a missing or empty dependency list, a missing,
empty, or duplicate name, a version that is not strict
semver, a wrongly typed signal — is a validation error
naming the offending path (for example
dependencies[1].latest must be a strict MAJOR.MINOR.PATCH semver version), and no partial assessment is produced.
The computation is pure and local: no network, no
registry lookups, no files read beyond the input you pass
in — freshcheck judges only the versions and signals you
supply.
CLI
args.json contains the full arguments object:
archived defaults to false per dependency, and
abandoned_days defaults to 730 for the whole call.
The assessment is printed as JSON:
Note lib: 1.10.2 is a minor step ahead of 1.9.0 because
components compare numerically, not lexicographically.
Exit codes: 0 on success, 1 on a runtime error
(including an unreadable or invalid input file, or invalid
input), 2 on a usage error.
MCP server
MCP client config:
Tools
-
assess_freshness— Assess how stale a dependency tree is, grouped by risk.dependencies(array, required, at least one) — dependencies as{name, current, latest, archived?, days_since_last_release?}objects;nameis unique across the set, andcurrent/latestare strictMAJOR.MINOR.PATCHsemver versionsabandoned_days(integer, optional, default 730, at least 1) — days without a release at which a dependency counts as abandoned
Returns
{dependencies, groups, counts}.
Docker
Development
License
MIT — Copyright (c) 2026 Rene Turcios
Source: README.md at commit b012cdb
Tools
0Version history
1- v0.1.0LatestNov 3, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts