Skip to main content
Glama
mcp-repo-health

mcp-repo-health

by ashwinmridul

Related Servers

Alternatives to mcp-repo-health

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Scores npm packages, PyPI packages and GitHub repositories 0-100 with an A-F grade and plain-language risks. Scans package.json, requirements.txt and lock files; no API key needed.
      3
      67 npm
      1
      Apache 2.0
    • 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.
      5 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 AI agents and developers to score npm packages, PyPI packages, and GitHub repositories for maintenance health, producing A–F grades, per-signal details, and plain-language risk lists before adoption. It supports checking individual packages, scanning manifests or lock files for transitive dependencies, and comparing alternatives.
      3
      67 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Local repository health diagnosis and fix planning for AI-written JavaScript, TypeScript, Python and mixed projects. Its stdio MCP server exposes scans, finding explanations, repair plans, verification, privacy review and DPDP technical readiness checks.
      7 npm
      35
      GPL 3.0

    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

    ActivityStale
    ResponsivenessNo recent community issues