get_github_trendingLABSCO SUMMARY
Pulling the READMEs is what saves the tokens.
The listing alone is nearly useless for writing anything — you end up fetching each README anyway, one call and one round trip at a time. Returning them together means a digest is one tool call, which is the explicit reason the author gives for building it. The proxy support is not incidental either: it exists because reaching GitHub is not uniform everywhere, and the status tool tells you which way the request is going before you debug a timeout.
What it is
A fetcher for the GitHub trending page that returns more than the listing. For each repository it collects the name, link, description and the full README, so a summary or a blog post can be written from one response rather than from a chain of follow-up fetches.
What you get
get_github_trendingreturns the day's trending repositories as Markdown, with the README content included for each onerepo_limitsets how many repositories to fetch, defaulting to 5save_to_filewrites the result to a dated Markdown file and defaults to true, adding a numeric suffix rather than overwriting an existing fileuse_proxyroutes the fetch through a configured proxy, defaulting to falseget_proxy_statusreports the current proxy configuration
Requirements
Python. Install straight from the repository with pip, or clone and install in editable mode, then have the client run python -m github_trending_mcp. Proxy settings come from three environment variables — PROXY_HOST defaulting to 127.0.0.1, PROXY_PORT defaulting to 10808 and PROXY_PROTOCOL defaulting to socks5 — which can also be set inline in the client's server entry. Because it parses the trending page, a change to that page's structure will require the parsing logic to be updated.
Setup effort
One command — pip install git+https://github.com/RusianHu/GitHubDailyTrendingFetcher-mcp.git
USE CASES
01
Writing a daily digest of what is trending
Get the repositories and their READMEs in one response and summarise from there.
02
Keeping an archive of what was hot each day
Let it save a dated Markdown file, with a suffix rather than an overwrite if one already exists.
03
Fetching from a network that needs a proxy
Route the request through your proxy and confirm the settings before blaming the network.
04
Scanning more than the front few
Raise the repository limit when a quick look at the top five is not enough.
2 tools
Listed in project docs. Your client may show a different list.
get_proxy_statusBEFORE YOU INSTALL
What to know first
Tools you get
2 tools named in the project's documentation.
Requires
python on PATH
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
pip install git+https://github.com/RusianHu/GitHubDailyTrendingFetcher-mcp.gitMCP Clients
Roo Code
ROO CODE · JSON
{
"mcpServers": {
"github-trending-mcp": {
"command": "python",
"args": [
"-m",
"github_trending_mcp"
],
"env": {
"PROXY_HOST": "127.0.0.1",
"PROXY_PORT": "10808",
"PROXY_PROTOCOL": "socks5"
},
"alwaysAllow": [
"get_github_trending",
"get_proxy_status"
],
"disabled": false
}
}
}
