Skip to main content
Glama
ashwinmridul

mcp-repo-health

by ashwinmridul

Related Servers

Alternatives to mcp-repo-health

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Scans codebases for TODOs, FIXMEs, code complexity, file stats, and dependencies, generating a health report with a letter grade. Zero configuration required.
      33 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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
    • A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      3
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Audits 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.
      3
      61 npm
      MIT

    TDQS

    B3.4/5.0

    Scored across 2 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count3/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues