GithubStats_MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | Optional GitHub personal access token for higher rate limits |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| helloA | Return a friendly greeting for the provided name. |
| github_user_statsB | Fetch public GitHub profile, activity stats, and pull request insights. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.