No user-submitted related servers found.
Scored across 4 tools
The issue-focused tools are confusingly similar: search_issues actually lists issues, while search_repository_issues searches them, making it hard for an agent to know which to select. get_repository and list_pull_requests are distinct, but the two issue tools create real ambiguity.
All tool names use snake_case and a verb_noun pattern, but search_issues is a misleading name for a listing operation and search_repository_issues redundantly adds 'repository' while search_issues does not. This creates a somewhat consistent yet semantically muddled naming scheme.
Four tools is not excessive, but for a server called 'GitHub MCP Server' the count feels thin and narrowly scoped. It is above the 1-2 tool borderline but still underrepresents the expected breadth of a GitHub integration.
The surface only covers repository information, issue listing/searching, and pull request listing. Core GitHub operations like creating or updating issues, creating or merging pull requests, and fetching individual items are missing, which will likely cause agent failures for common workflows.