mcp-github-trending
Related Servers
Alternatives to mcp-github-trending
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceAn MCP server that provides access to the OSS Insight Public API for GitHub repository analytics. It enables querying trending repositories, contributor statistics, and collection rankings through various tools.187 npm3MIT
- FlicenseNot gradedqualityDmaintenanceA simple MCP server that provides repository information (list repos, get repo details) using GitHub's public REST API, without needing any API keys or tokens.-
- FlicenseNot gradedqualityDmaintenanceMCP server for GitHub operations, providing tools for repository management, issues, pull requests, and code search.-
- -licenseNot gradedqualityAmaintenanceMCP Server for the GitHub API, enabling file operations, repository management, search functionality, and more.88,163 npm90,629MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for the GitHub API, enabling file operations, repository management, search functionality, issues, pull requests, and more.64 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides tools for interacting with the GitHub API, enabling AI assistants to query repositories, pull requests, issues, commits, users, and more.379 npmISC
TDQS
Scored across 2 tools
The two tools have perfectly distinct purposes: one targets trending developers, the other trending repositories. There is no overlap in functionality, and an agent can easily differentiate between them based on the clear resource distinction.
Both tools follow an identical verb_noun pattern with 'get_github_trending_' prefix, ensuring complete predictability. The naming is highly consistent and readable, with no deviations in style or structure.
With only 2 tools, the server feels thin for its apparent scope of 'github-trending'. While it covers two key resources, the lack of filtering, sorting, or time-range options limits utility, making the count borderline insufficient for robust trending analysis.
The server provides basic access to trending developers and repositories, but there are notable gaps. Missing operations include filtering by language, location, or time period, and there is no way to get historical trending data or detailed analytics, which are common needs in this domain.