Skip to main content
Glama
huanglizhuo

octocounts-mcp

by huanglizhuo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

Related Servers

Alternatives to octocounts-mcp

No user-submitted related servers found.

    Related Servers

    • github-insights

      Nishant-Chaudhari-Dev
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides read-only tools to search public GitHub repositories, retrieve repository details, READMEs, contributors, and commit activity, and compare up to 10 repositories side by side.
      MIT

    • github-mcp

      aaryanptl
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides four GitHub superpowers (repo-scorecard, compare-repos, commit-heatmap, trending-mcp) as MCP tools with React widgets for repository health analysis, comparison, commit activity visualization, and trending MCP servers.
      91 npm
      MIT

    • github-assistant

      JokkimDoras
      A
      license
      Not graded
      quality
      B
      maintenance
      Lets MCP-compatible clients answer natural-language questions about your GitHub activity, such as counting today's commits across all your repositories via the GitHub REST API.
      91 npm
      1
      MIT

    • mcp-server-github-trend

      jankoli
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides GitHub open-source intelligence via MCP tools for discovering trends, evaluating repository health, comparing projects, and analyzing users, issues, and releases. It includes a CLI and can be used with AI assistants like Claude or Cursor.
      MIT
    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.5/5.0

    Scored across 2 tools

    Disambiguation5/5

    analyze_repo targets a single repository, while compare_repos targets two repositories or refs. Their boundaries are clear and non-overlapping, so an agent can easily choose the right tool.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern: analyze_repo and compare_repos. Naming is predictable and uses snake_case throughout.

    Tool Count3/5

    Two tools is thin for most MCP servers, though this server has a narrow SLOC-counting purpose. The pair covers single-repo analysis and comparison, but feels minimal.

    Completeness4/5

    The core domain of SLOC totals and comparisons is covered by the two tools. Minor gaps exist around deeper breakdowns or output options, but agents can accomplish the primary workflows.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources