RepoTrending
Server Details
Read-only GitHub trending data: top repos by stars gained today, this week or this month.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 5 tools
Each tool has a clearly distinct role: fetching one repo, listing trending repos, explaining ranking methodology, listing filter values, and searching tracked repos. The potential overlap between get_trending and search_repos is resolved by their descriptions: one browses rankings, the other matches keywords.
Four tools follow a clear verb_noun pattern (get_repo, get_trending, list_filters, search_repos). The exception is how_we_rank, which is readable but breaks the convention.
Five tools are well-scoped for a read-only GitHub trending explorer. Each tool covers a distinct need without padding or obvious missing essentials.
The surface covers repo details, trending lists, filters, search, and ranking explanation, which handles the core domain. A way to list all tracked repos or compare repos could be useful, but agents can work around this via search and trending.
Available Tools
5 toolsget_repoOne GitHub repoARead-onlyIdempotentInspect
Details of one tracked repo by owner/name: stars, forks, language, license, topics, star counts of the last days, gains and ranks per window.
Inputs: repo (required). Returns: url, note, rank, repo, +16 more
get_trendingTrending GitHub reposARead-onlyIdempotentInspect
Top GitHub repos by stars gained today (last 24 hours), this week (7 days) or this month (30 days), or by total stars (window "all"). Optional language or topic filter. Use list_filters for valid names.
Inputs: limit, topic, window, language. Returns: note, count, repos, topic, +10 more
how_we_rankHow the rankings are madeARead-onlyIdempotentInspect
Plain explanation of how RepoTrending counts stars gained, which repos it tracks, what it leaves out and how much data each window has so far.
Inputs: no named parameters. Returns: limits, source, summary, windows, +5 more
list_filtersLanguages and topicsARead-onlyIdempotentInspect
List the languages or the GitHub topics that get_trending and search_repos accept, with how many tracked repos each has. Most repos first.
Inputs: kind (required), limit. Returns: kind, count, items, total, +5 more
search_reposSearch tracked reposARead-onlyIdempotentInspect
Find tracked repos by words in the name, description, topics or language. Every word must match. Results are ordered by relevance, then stars.
Inputs: query (required), limit, language. Returns: count, repos, source, matches, +6 more
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
GitHub hot-repo leaderboards: snapshots, movers, rank history. Read-only JSON, hourly batches.
Rising GitHub repos per topic, ranked by star velocity, plus repos spotted early. Free, read-only.
Trend data from Google, TikTok, Amazon, Reddit, YouTube, Steam, npm and more as JSON
Search GitHub repos, find alternatives, browse topics and rank top developers and orgs. No auth.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to query GitHub trending projects, analyze language and technology trends, and generate visual trend reports.MIT
- FlicenseNot gradedqualityDmaintenanceProvides access to GitHub trending projects through MCP, allowing AI assistants to query popular repositories filtered by language and time range (daily/weekly/monthly).-
- AlicenseNot gradedqualityDmaintenanceFetches and filters GitHub trending repositories by keywords, language, and time period.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP-capable clients to query recent and active GitHub trending repositories, search projects with filters, read repository details and README excerpts, and compare multiple repositories for technology selection.308 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.