mcp-repo-health
Related Servers
Alternatives to mcp-repo-health
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceScans codebases for TODOs, FIXMEs, code complexity, file stats, and dependencies, generating a health report with a letter grade. Zero configuration required.33 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables maintainers to prioritize maintenance across GitHub repositories by converting repository, branch, CI, security, and release signals into deterministic, evidence-backed scores and ranked actions.MIT
- AlicenseAqualityCmaintenanceSupply chain risk scoring for npm, PyPI, and GitHub repos8107 npm7MIT
- AlicenseAqualityCmaintenanceEnables scoring a local markdown documentation file out of 100 across categories like title, install, usage, license, badges, structure, and relative link resolution, with letter grades and a concrete list of fixes. It works on local files only, providing a heuristic checklist of documentation completeness rather than judging code quality, security, or SEO.3MIT
- AlicenseAqualityAmaintenanceAudits local package folders to generate publish-readiness reports and previews of NPM tarball contents. It helps developers identify and resolve configuration issues like missing types or broken exports before releasing code.361 npmMIT
- AlicenseAqualityCmaintenanceValidates release hygiene in local repositories with network-free, read-only tools for checking repo structure, version alignment, and generating release checklists.3MIT
TDQS
Scored across 2 tools
The two tools are related but distinct: score_repo provides an overall health score, while list_hygiene_gaps returns only the failing checks. An agent could confuse them if it wants a summary versus details, but the descriptions clarify the difference.
Both tools use a verb_noun pattern (score_repo, list_hygiene_gaps), which is consistent. The second tool's noun phrase is more descriptive than the first, but the pattern is still predictable.
Two tools is on the thin side for a repository health server, but the scope is narrow and the two tools cover the core need. It feels slightly minimal but not unreasonable.
The server covers scoring and listing gaps, but lacks operations like getting detailed check results, generating reports, or fixing/ignoring specific hygiene issues. The core workflow is present, but there are notable gaps for a health-check domain.