GithubStats_MCP
Related Servers
Alternatives to GithubStats_MCP
No user-submitted related servers found.
Related Servers
- FlicenseAqualityCmaintenanceMCP server for exploring GitHub public data. It provides tools to fetch user profiles, list top repositories, and calculate language usage statistics, which AI agents can invoke dynamically.3-
- FlicenseNot gradedqualityDmaintenanceA read-only MCP server that exposes GitHub user profiles, repository info, and search via tools for AI assistants like Claude.-
- FlicenseNot gradedqualityCmaintenanceMCP server exposing tools to fetch GitHub repository details, issues, and commits, enabling AI agents to query and summarize GitHub data via local LLMs.-
- AlicenseAqualityCmaintenanceA lightweight MCP server that exposes GitHub tools for searching repositories, listing issues, and reading file contents.3346 npmISC
- FlicenseAqualityDmaintenanceMCP server exposing GitHub tools for issues, pull requests, and code browsing via the GitHub REST API. Designed for local LLM clients with flat arguments and streamable HTTP support.15-
- AlicenseBqualityCmaintenanceMCP server that exposes GitHub operations as tools for AI agents, enabling code search, issue management, and PR review.12MIT
TDQS
Scored across 2 tools
The two tools are entirely distinct: 'hello' provides a greeting, while 'github_user_stats' fetches GitHub data. There is no overlap or ambiguity between them.
The tool names lack a consistent pattern. 'hello' is a simple interjection, while 'github_user_stats' is a compound noun; neither follows a verb_noun convention, making the naming style inconsistent.
With only two tools, one of which is a generic greeting, the set feels thin for a GitHub stats server. However, it is not an extreme mismatch given the narrow domain.
The 'github_user_stats' tool covers the primary domain of fetching user profile, activity, and PR insights, but the inclusion of 'hello' adds no domain value, and there is no ability to query specific metrics or historical data, leaving minor gaps.