Skip to main content
Glama
chetangpande-ai

GitHub Repository Health MCP

by chetangpande-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to GitHub Repository Health MCP

No user-submitted related servers found.

    Related Servers

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of repository health: metadata, issues, commits, and workflow runs. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    All four tools follow a consistent get_<resource>_<detail> pattern with snake_case naming. The naming is predictable and easy to extend.

    Tool Count5/5

    Four tools is well-scoped for a read-only repository health MCP. Each tool covers a meaningful health signal without unnecessary redundancy.

    Completeness4/5

    The core health indicators—repo stats, issues, commits, and CI status—are covered. Pull request activity and contributor trends are notable omissions, but the current surface is sufficient for basic health assessments.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources