What it does
abandoncheck takes caller-supplied facts about a dependency: whether its repository is archived, days since the last release and last commit, commits in the last 90 days, active maintainers, and open issues. It returns a verdict, a score, the bands the signals fall into, and the reasons behind the score. An archived repository gives a score of 0 and the verdict abandoned. Otherwise the score starts at 100 and loses points for missing or stale release information, missing or stale commit information, a silent last 90 days, and a thin maintainer bench, never dropping below 0. Open issues are reported but never scored.
It suits checking whether the dependencies in a project still have people looking after them. Release age falls into fresh (180 days or less), aging (365), stale (730), or dormant beyond that, and is unknown when no release information is given. Commit age falls into active (90 days), slowing (180), quiet (365), or silent beyond that. Scores of 80 and above read as maintained, 50 and above as at_risk, above 0 as likely_abandoned, and 0 as abandoned.
It runs as an MCP server exposing a check_dep_maintenance tool, or as a CLI that reads an args.json file and prints JSON. Absent optional signals appear as null with an unknown band. The CLI exits with 0 on success, 1 on a runtime error, and 2 on a usage error. The computation is local and pure: it makes no network calls, needs no configuration, and reads or touches no repository.
Limitations and requirements
The tool judges only the signals provided and inspects no code or repository, so results depend on the values supplied. Malformed input (a missing, empty, or non-string name; a missing or non-boolean archived; or any optional count that is not an integer of at least 0) returns a validation error naming the path, with no partial result. Open issue counts never affect the score.
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/abandoncheck
Judge whether a dependency is maintained, from factual signals: releases, commits, archival.
v0.1.0As shown on registry.modelcontextprotocol.io when we last read it