We and selected third parties use cookies or similar technologies for technical purposes and, with your consent, to analyze how the site is used.

You can freely give, refuse or withdraw your consent at any time.

HotRepo

MCP server by HotRepo

Browse GitHub Trending boards, AI-written project reviews, topics and monthly reports for open-source repositories.

Needs an API key (Needs an API key from the vendor)Streamable HTTP

Connect to HotRepo

HotRepo needs an API key. Connect with its own URL and your key:

https://hotrepo.ai/mcp

Send your key. mcp.tc never sees or stores keys. Where to get a key

Share this server

Opens this page, with the URL and setup steps.

mcp.tc/i/hotrepo

About

HotRepo tracks GitHub Trending (daily, weekly, monthly) and its own board of fast-growing new repositories. Each trending project gets an AI-written review covering the problem it solves, what is different, who should try it, requirements, limitations and a verdict. The tools are read-only and let you fetch boards, read reviews, search by query or topic, and get monthly reports.

It runs as a hosted Streamable HTTP endpoint at https://hotrepo.ai/mcp. Access needs a HotRepo API key, sent in the Authorization header. Free sign-up is available on the HotRepo account page.

What you can do

  • Get GitHub Trending boards by period, language and date
  • Read full AI reviews of trending repositories
  • Search reviewed repositories by query or topic
  • List topics and the repositories in each
  • Read monthly trending reports
  • View a repository's daily trending history and Hacker News threads

Tools 12

  • get_trendingRead-only

    Get a trending board for one UTC day, ranked by stars gained, with one-line reviews.

  • get_repoRead-only

    Read the full review of a repository with stats, topic, trending history and HN threads.

  • search_reposRead-only

    Search reviewed repositories, newest reviews first.

  • list_topicsRead-only

    List topics with the number of reviewed projects in each.

  • get_topicRead-only

    List reviewed repositories in one topic, most recently trending first.

  • get_monthly_reportRead-only

    Get a monthly report of top star gainers, notable new repos and topic leaders.

  • get_weekly_digestRead-only

    Get a HotRepo weekly digest, the weekly email also published on hotrepo.ai/weekly: an editorial introduction (a headline and a few themes), the week's 10 biggest gainers, notable new repositories…

  • list_favoritesRead-only

    List the repositories the API key's owner has favorited on hotrepo.ai, most recently favorited first, with HotRepo's one-line review when one is published.

  • get_similar_reposRead-only

    [Pro] Find reviewed repositories similar to a given one: alternatives and related projects, ranked by how closely HotRepo's one-line review, the GitHub description, name and GitHub topics match…

  • get_star_historyRead-only

    [Pro] A repository's star growth over its whole life: stars at the end of each month, stars added on each of the last 30 days, stars gained over the last 7 / 30 / 90 / 365 days, and the days it was…

  • compare_reposRead-only

    [Pro] Compare 2 to 5 repositories side by side: stars, forks, age, language, license, HotRepo topic and one-line review, days on GitHub's all-languages daily Trending (HotRepo's records start…

  • get_favorite_releasesRead-only

    [Pro] New releases of the repositories the API key's owner has favorited on hotrepo.ai that HotRepo found in the last 30 days (by when HotRepo picked them up, up to the 50 most recent; a release…

Read from the live server on 18 Nov 2026. Read-only, Writes and Can delete are hints the server declares; your client decides whether to ask before running a tool.

Example prompts

  • What is trending on GitHub today in Rust?

  • Show me HotRepo's review of debpalash/VoiceStudio.

  • Search reviewed repositories about coding agents.

  • Give me the HotRepo monthly report for last month.

Set up

Every client connects to hotrepo.ai. Pick yours; the page remembers your choice.

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport http hotrepo https://hotrepo.ai/mcp
  1. Start Claude Code and type /mcp. hotrepo should show as connected.

HotRepo needs an API key. HotRepo’s docs say which header carries it; most servers use Authorization: Bearer <YOUR_API_KEY>.

Claude Desktop

  1. Use the mcp-remote bridge, which keeps the key on this computer (a connector added on claude.ai with the key under Request headers also shows up here). Open Settings → Developer → Edit Config and add:
claude_desktop_config.json
{
  "mcpServers": {
    "hotrepo": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://hotrepo.ai/mcp"
      ]
    }
  }
}
  1. Replace the placeholder with your key and restart Claude Desktop.

The bridge needs Node.js on your computer.

Cursor

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

mcp.json
{
  "mcpServers": {
    "hotrepo": {
      "url": "https://hotrepo.ai/mcp"
    }
  }
}

HotRepo needs an API key. HotRepo’s docs say which header carries it; most servers use Authorization: Bearer <YOUR_API_KEY>.

VS Code

Or from a terminal:

code --add-mcp '{"name":"hotrepo","type":"http","url":"https://hotrepo.ai/mcp"}'

Or commit it to the repo in .vscode/mcp.json:

.vscode/mcp.json
{
  "servers": {
    "hotrepo": {
      "type": "http",
      "url": "https://hotrepo.ai/mcp"
    }
  }
}

HotRepo needs an API key. HotRepo’s docs say which header carries it; most servers use Authorization: Bearer <YOUR_API_KEY>.

Devin Desktop

  1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):
mcp_config.json
{
  "mcpServers": {
    "hotrepo": {
      "serverUrl": "https://hotrepo.ai/mcp"
    }
  }
}
  1. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads serverUrl (or url) for remote servers.

Codex

codex mcp add hotrepo --url https://hotrepo.ai/mcp

Or edit ~/.codex/config.toml directly:

config.toml
[mcp_servers.hotrepo]
url = "https://hotrepo.ai/mcp"

HotRepo needs an API key. HotRepo’s docs say which header carries it; most servers use Authorization: Bearer <YOUR_API_KEY>.

Gemini CLI

gemini mcp add --transport http hotrepo https://hotrepo.ai/mcp

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients accept this shape. Some name the URL field differently: serverUrl in Devin Desktop, httpUrl in Gemini CLI’s settings file.

{
  "mcpServers": {
    "hotrepo": {
      "type": "http",
      "url": "https://hotrepo.ai/mcp"
    }
  }
}

Zed puts servers under context_servers in its settings. Cline needs "type": "streamableHttp", or it assumes SSE.

Client only starts local servers? Bridge it with npx -y mcp-remote https://hotrepo.ai/mcp.

HotRepo needs an API key. HotRepo’s docs say which header carries it; most servers use Authorization: Bearer <YOUR_API_KEY>.

Embed

Show HotRepo in a README or on your site. Each embed links to this page, uses the server’s own URL, and sets no cookies. How embeds work

The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.

README badge

Badge preview, lightBadge preview, dark
Markdown
[![HotRepo on mcp.tc](https://mcp.tc/i/hotrepo/badge.svg)](https://mcp.tc/i/hotrepo)
HTML
<a href="https://mcp.tc/i/hotrepo"><img src="https://mcp.tc/i/hotrepo/badge.svg" alt="HotRepo on mcp.tc" height="20"></a>

It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.

Website card

HTML
<script src="https://mcp.tc/w/hotrepo.js" async></script>

The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.

iframe

HTML
<iframe src="https://mcp.tc/embed/hotrepo" title="HotRepo on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.

JSON

The listing as data for your own pages and tools: name, tagline, the server’s own URL, tools and the “Add to” links. Any site can read it (CORS is open).

https://mcp.tc/i/hotrepo.json

What each field means

AI prompt

Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the HotRepo card to your site.

Markdown
Add the mcp.tc card for HotRepo, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.

Put this tag where the card should appear. The card renders right before it:

```html
<script src="https://mcp.tc/w/hotrepo.js" async></script>
```

To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.

```html
<div data-mcptc="hotrepo"><a href="https://mcp.tc/i/hotrepo">HotRepo on mcp.tc</a></div>
```

Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.

If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).

For a README or other Markdown docs, use the badge instead:

```markdown
[![HotRepo on mcp.tc](https://mcp.tc/i/hotrepo/badge.svg)](https://mcp.tc/i/hotrepo)
```

Reference: https://mcp.tc/embed

Change history

Its tools are behind a sign-in, so we can’t read them. New versions it reports and edits by its owner show up here.

Follow HotRepo and we’ll email you when something changes.

  1. , Automatic check

    New version 1.2.0 (was 1.1.0). Reported by the server.

  2. , Automatic check

    5 tools added and 7 tools changed. Server instructions changed.

    New server instructions

    Details, 9 Nov 2026, 14:50 UTC

    Added 5

    • compare_reposRead-only

      [Pro] Compare 2 to 5 repositories side by side: stars, forks, age, language, license, HotRepo topic and one-line review, days on GitHub's all-languages daily Trending (HotRepo's records start 2026-05-10) and best position there (real positions from 2026-10-24), recent star growth (when HotRepo has generated its star history; null otherwise) and Hacker News attention. stars_gained_last_7_days and stars_gained_last_30_days count back from star_growth_until, which can differ between repositories; mention it when the dates differ instead of comparing the numbers as if they covered the same days. For the full reviews call get_repo on the ones that matter. Repositories without a HotRepo page (no review and no star history) are returned with available=false.

    • get_favorite_releasesRead-only

      [Pro] New releases of the repositories the API key's owner has favorited on hotrepo.ai that HotRepo found in the last 30 days (by when HotRepo picked them up, up to the 50 most recent; a release published earlier but found late is included), sorted by release date, newest first. Each comes with HotRepo's AI summary of what the release added or changed (written from the release notes; pre-releases and nightly builds are skipped). summary_status: ok = changes listed; pending = summary still being written; empty = the release notes did not say what changed; failed = no summary, only versions and links. Releases are checked hourly. Reading them here does not mark them as read on the website.

    • get_similar_reposRead-only

      [Pro] Find reviewed repositories similar to a given one: alternatives and related projects, ranked by how closely HotRepo's one-line review, the GitHub description, name and GitHub topics match (projects in the same HotRepo topic score a little higher). Only repositories HotRepo has reviewed are compared, whether or not they are still trending. Fewer than limit results means nothing else was similar enough.

    • get_star_historyRead-only

      [Pro] A repository's star growth over its whole life: stars at the end of each month, stars added on each of the last 30 days, stars gained over the last 7 / 30 / 90 / 365 days, and the days it was on GitHub's all-languages daily Trending page with its best position that day (HotRepo's board records start 2026-05-10; real positions from 2026-10-24, earlier ones are null). Counts are from GitHub's star history and only include stars that still exist. If HotRepo has not fetched this repository yet, the call fetches it from GitHub now (usually a few seconds), which uses one of the plan's new star histories for the day; repositories already on HotRepo do not count.

    • get_weekly_digestRead-only

      Get a HotRepo weekly digest, the weekly email also published on hotrepo.ai/weekly: an editorial introduction (a headline and a few themes), the week's 10 biggest gainers, notable new repositories, and each day's top gainer. stars_that_week is the highest star count seen that week, not today's count. daily_top_gainers lists, for each day, the repository that gained the most stars that day among those on GitHub's all-languages daily Trending with a published HotRepo review; it is not necessarily the one GitHub showed at #1. The top list comes from GitHub's weekly Trending; when fewer than 10 usable repositories were on it, it is topped up with the biggest gainers summed over that week's daily Trending boards. Each top item's ranked_from says which ("weekly_trending" or "daily_trending_sum"; null on older issues where the issue-level top_source is "mixed"). Do not call a daily_trending_sum item part of the weekly Trending. Lists were fixed when the issue went out; repositories later remo…

    Changed 7

    • get_monthly_reportinput schema
      • Removed parameters: lang
      • Description of month
        Before

        YYYY-MM (a finished UTC month); omit for the latest report

        After

        YYYY-MM (a finished UTC month); omit for the latest report. Earlier reports need Pro (Free: latest report only)

    • get_repoinput schema
      • Removed parameters: lang
    • get_topicdescription and input schema
      Before

      List reviewed repositories in one topic, most recently trending first.

      After

      List reviewed repositories in one topic, most recently trending first. Free returns at most 10 per call.

      • Removed parameters: lang
    • get_trendinginput schema
      • Removed parameters: lang
      • Description of date
        Before

        UTC day YYYY-MM-DD; omit for the latest board

        After

        UTC day YYYY-MM-DD; omit for the latest board. Past days need Pro (Free: latest board only)

    • list_favoritesinput schema
      • Removed parameters: lang
    • list_topicsinput schema
      • Removed parameters: lang
    • search_reposdescription and input schema
      Before

      Search repositories that HotRepo has reviewed, newest reviews first. Use get_repo for the full review.

      After

      Search repositories that HotRepo has reviewed, newest reviews first. Use get_repo for the full review. Free returns at most 10 results per call.

      • Removed parameters: lang

    Server instructions

    Before

    HotRepo (https://hotrepo.ai) tracks GitHub Trending (daily, weekly, monthly) plus its own board of fast-growing new repositories, and publishes an AI-written review for trending projects: what problem it solves, what is different, who should try it, requirements and limitations, and a verdict. Use these tools to discover notable open-source projects, check what is trending in a language, read HotRepo's review of a specific repository, or list the projects the user has favorited on hotrepo.ai. Board dates are UTC days. Reviews are based on each project's own docs and may miss nuance; link users to the HotRepo page (url) or the GitHub repository for details.

    After

    HotRepo (https://hotrepo.ai) tracks GitHub Trending (daily, weekly, monthly) plus its own board of fast-growing new repositories, and publishes an AI-written review for trending projects: what problem it solves, what is different, who should try it, requirements and limitations, and a verdict. Use these tools to discover notable open-source projects, check what is trending in a language, read HotRepo's review of a specific repository, or list the projects the user has favorited on hotrepo.ai. Board dates are UTC days. Reviews are based on each project's own docs and may miss nuance; link users to the HotRepo page (url) or the GitHub repository for details. Tools marked [Pro] need a HotRepo Pro plan: past boards, monthly reports and weekly digests, similar projects / alternatives, star growth history, side-by-side comparison, and release summaries for the user's favorites. On the Free plan they return an error with the upgrade link; tell the user what Pro would add instead of retrying. Reviews, topic names, report and digest introductions, release notes and hotrepo.ai links come in the language set for the API key (English or Chinese; the user changes it on hotrepo.ai/account). Tools have no language parameter: if the user writes in another language, translate when you answer. Field names and error messages are always English.

  3. , Automatic check

    1 tool changed.

    Details, 7 Nov 2026, 14:47 UTC

    Changed 1

    • get_trendingdescription
      Before

      Get a HotRepo trending board: the repositories on GitHub Trending (or HotRepo's new-repository board) for one UTC day, ranked by stars gained (new boards use measured Stars/hour), each with HotRepo's one-line review. From 2026-11-01 boards list only repositories with a published review; earlier archived days may include items without one. GitHub does not order strictly by stars gained, so GitHub's own position can differ from rank. On weekly, monthly and language boards each item has best_github_rank_that_day: the best position it reached on GitHub's page for this board across that day's scrapes. On the all-languages daily board and the new-repository board it has best_github_daily_rank instead: the best position it has ever reached on GitHub's all-languages daily Trending page up to this board's date. Both are null when unknown (no real positions before 2026-10-24). Live new-board previous_rank compares the preceding successful hourly run (including retained projects); previous_board…

      After

      Get a HotRepo trending board: the repositories on GitHub Trending (or HotRepo's new-repository board) for one UTC day, ranked by stars gained (new boards use measured Stars/hour), each with HotRepo's one-line review. From 2026-11-01 boards list only repositories with a published review; earlier archived days may include items without one. GitHub does not order strictly by stars gained, so GitHub's own position can differ from rank. On weekly, monthly and language boards each item has best_github_rank_that_day: the best position it reached on GitHub's page for this board across that day's scrapes. On the all-languages daily board and the new-repository board it has best_github_daily_rank instead: the best position it has ever reached on GitHub's all-languages daily Trending page up to this board's date. Both are null when unknown (no real positions before 2026-10-24). Live new-board previous_rank compares the preceding successful run (including retained projects); previous_board_at ide…

  4. , Automatic check

    1 tool changed.

    Details, 5 Nov 2026, 17:48 UTC

    Changed 1

    • get_repodescription
      Before

      Read HotRepo's full review of a repository (Markdown), with its stats, topic, daily trending history (the all-languages board; each day's best_github_rank_that_day is the best position it reached on GitHub's page that day, null before 2026-10-24) and Hacker News threads that link to it. Only repositories that have trended and been reviewed are available.

      After

      Read HotRepo's full review of a repository (Markdown), with its stats, topic, daily trending history (the all-languages board; each day's best_github_rank_that_day is the best position it reached on GitHub's page that day, null before 2026-10-24) and Hacker News threads that link to it. forked_from / fork_root name the upstream repository when it is a GitHub fork (null otherwise). Only repositories that have trended and been reviewed are available.

  5. , Automatic check

    1 tool changed.

    Details, 4 Nov 2026, 02:43 UTC

    Changed 1

    • get_trendingdescription

      The text shown here is the same before and after: the change is past the first 1,000 characters or in characters that don’t show.

  6. , Automatic check

    1 tool changed.

    Details, 1 Nov 2026, 14:47 UTC

    Changed 1

    • get_trendingdescription
      Before

      Get a HotRepo trending board: the repositories on GitHub Trending (or HotRepo's new-repository board) for one UTC day, ranked by stars gained (new boards use measured Stars/hour), each with HotRepo's one-line review when available. GitHub does not order strictly by stars gained, so GitHub's own position can differ from rank. On weekly, monthly and language boards each item has best_github_rank_that_day: the best position it reached on GitHub's page for this board across that day's scrapes. On the all-languages daily board and the new-repository board it has best_github_daily_rank instead: the best position it has ever reached on GitHub's all-languages daily Trending page up to this board's date. Both are null when unknown (no real positions before 2026-10-24). Live new-board previous_rank compares the preceding successful hourly run (including retained projects); previous_board_at identifies its UTC timestamp. Other boards compare dates. New-board stars_gained is the increment between…

      After

      Get a HotRepo trending board: the repositories on GitHub Trending (or HotRepo's new-repository board) for one UTC day, ranked by stars gained (new boards use measured Stars/hour), each with HotRepo's one-line review. From 2026-11-01 boards list only repositories with a published review; earlier archived days may include items without one. GitHub does not order strictly by stars gained, so GitHub's own position can differ from rank. On weekly, monthly and language boards each item has best_github_rank_that_day: the best position it reached on GitHub's page for this board across that day's scrapes. On the all-languages daily board and the new-repository board it has best_github_daily_rank instead: the best position it has ever reached on GitHub's all-languages daily Trending page up to this board's date. Both are null when unknown (no real positions before 2026-10-24). Live new-board previous_rank compares the preceding successful hourly run (including retained projects); previous_board…

  7. , Automatic check

    1 tool changed.

    Details, 1 Nov 2026, 11:49 UTC

    Changed 1

    • get_trendingdescription and input schema
      Before

      Get a HotRepo trending board: the repositories on GitHub Trending (or HotRepo's new-repository board) for one UTC day, ranked by stars gained in the period, each with HotRepo's one-line review when available. GitHub does not order strictly by stars gained, so GitHub's own position can differ from rank. On weekly, monthly and language boards each item has best_github_rank_that_day: the best position it reached on GitHub's page for this board across that day's scrapes. On the all-languages daily board and the new-repository board it has best_github_daily_rank instead: the best position it has ever reached on GitHub's all-languages daily Trending page up to this board's date. Both are null when unknown (no real positions before 2026-10-24).

      After

      Get a HotRepo trending board: the repositories on GitHub Trending (or HotRepo's new-repository board) for one UTC day, ranked by stars gained (new boards use measured Stars/hour), each with HotRepo's one-line review when available. GitHub does not order strictly by stars gained, so GitHub's own position can differ from rank. On weekly, monthly and language boards each item has best_github_rank_that_day: the best position it reached on GitHub's page for this board across that day's scrapes. On the all-languages daily board and the new-repository board it has best_github_daily_rank instead: the best position it has ever reached on GitHub's all-languages daily Trending page up to this board's date. Both are null when unknown (no real positions before 2026-10-24). Live new-board previous_rank compares the preceding successful hourly run (including retained projects); previous_board_at identifies its UTC timestamp. Other boards compare dates. New-board stars_gained is the increment between…

      • Description of period
        Before

        daily/weekly/monthly = GitHub Trending for that window; new = HotRepo's board of repositories created in the last 14 days, ranked by average stars per day (every repository found by searches in the l…

        After

        daily/weekly/monthly = GitHub Trending for that window; new = HotRepo's board of repositories created in the last 7 days, ranked by measured Stars/hour over up to 24 hours (at least 1 hour observed).…

  8. , Automatic check

    New version 1.1.0 (was 1.0.0). Reported by the server.

  9. , Automatic check

    1 tool added and 1 tool changed. Server instructions changed.

    New server instructions

    Details, 29 Oct 2026, 17:47 UTC

    Added 1

    • list_favoritesRead-only

      List the repositories the API key's owner has favorited on hotrepo.ai, most recently favorited first, with HotRepo's one-line review when one is published. Use get_repo for the full review. Favorites are added on the website's project pages, not through this server.

    Changed 1

    • get_trendingdescription
      Before

      Get a HotRepo trending board: the repositories on GitHub Trending (or HotRepo's new-repository board) for one UTC day, ranked by stars gained in the period, each with HotRepo's one-line review when available. best_github_rank_that_day is the best position the repository reached on GitHub's own page for this board across that day's scrapes (GitHub does not order strictly by stars gained, so it can differ from rank); null before 2026-10-24.

      After

      Get a HotRepo trending board: the repositories on GitHub Trending (or HotRepo's new-repository board) for one UTC day, ranked by stars gained in the period, each with HotRepo's one-line review when available. GitHub does not order strictly by stars gained, so GitHub's own position can differ from rank. On weekly, monthly and language boards each item has best_github_rank_that_day: the best position it reached on GitHub's page for this board across that day's scrapes. On the all-languages daily board and the new-repository board it has best_github_daily_rank instead: the best position it has ever reached on GitHub's all-languages daily Trending page up to this board's date. Both are null when unknown (no real positions before 2026-10-24).

    Server instructions

    Before

    HotRepo (https://hotrepo.ai) tracks GitHub Trending (daily, weekly, monthly) plus its own board of fast-growing new repositories, and publishes an AI-written review for trending projects: what problem it solves, what is different, who should try it, requirements and limitations, and a verdict. Use these tools to discover notable open-source projects, check what is trending in a language, or read HotRepo's review of a specific repository. Board dates are UTC days. Reviews are based on each project's own docs and may miss nuance; link users to the HotRepo page (url) or the GitHub repository for details.

    After

    HotRepo (https://hotrepo.ai) tracks GitHub Trending (daily, weekly, monthly) plus its own board of fast-growing new repositories, and publishes an AI-written review for trending projects: what problem it solves, what is different, who should try it, requirements and limitations, and a verdict. Use these tools to discover notable open-source projects, check what is trending in a language, read HotRepo's review of a specific repository, or list the projects the user has favorited on hotrepo.ai. Board dates are UTC days. Reviews are based on each project's own docs and may miss nuance; link users to the HotRepo page (url) or the GitHub repository for details.

  10. , Automatic check

    2 tools changed.

    Details, 29 Oct 2026, 02:44 UTC

    Changed 2

    • get_repodescription
      Before

      Read HotRepo's full review of a repository (Markdown), with its stats, topic, daily trending history and Hacker News threads that link to it. Only repositories that have trended and been reviewed are available.

      After

      Read HotRepo's full review of a repository (Markdown), with its stats, topic, daily trending history (the all-languages board; each day's best_github_rank_that_day is the best position it reached on GitHub's page that day, null before 2026-10-24) and Hacker News threads that link to it. Only repositories that have trended and been reviewed are available.

    • get_trendingdescription and input schema
      Before

      Get a HotRepo trending board: the repositories on GitHub Trending (or HotRepo's new-repository board) for one UTC day, ranked by stars gained in the period, each with HotRepo's one-line review when available.

      After

      Get a HotRepo trending board: the repositories on GitHub Trending (or HotRepo's new-repository board) for one UTC day, ranked by stars gained in the period, each with HotRepo's one-line review when available. best_github_rank_that_day is the best position the repository reached on GitHub's own page for this board across that day's scrapes (GitHub does not order strictly by stars gained, so it can differ from rank); null before 2026-10-24.

      • Description of period
        Before

        daily/weekly/monthly = GitHub Trending for that window; new = HotRepo's board of repositories created in the last 14 days, ranked by average stars per day

        After

        daily/weekly/monthly = GitHub Trending for that window; new = HotRepo's board of repositories created in the last 14 days, ranked by average stars per day (every repository found by searches in the l…

  11. , Automatic check

    Tracking started: 6 tools.

FAQ

Can I paste mcp.tc/i/hotrepo into my MCP client?

No. mcp.tc links are pages, not server addresses. Connect with https://hotrepo.ai/mcp, so your client talks to HotRepo directly. Your key goes there too, never to mcp.tc. The quick link is for sharing: it opens this page, with setup steps for every client.

Does HotRepo need an API key or a sign-in?

Yes. HotRepo needs an API key. Get one from HotRepo and keep it in your client’s config, never in a shared file.

Is HotRepo a remote or a local server?

Remote. HotRepo hosts it at https://hotrepo.ai/mcp, and it speaks Streamable HTTP. There’s nothing to install.

What can HotRepo do?

It has 12 tools, including get_trending, get_repo and search_repos. You can get GitHub Trending boards by period, language and date, read full AI reviews of trending repositories and search reviewed repositories by query or topic.

Which clients can use it?

Any client that supports remote MCP servers and can send your key: Claude Code, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. On claude.ai and Claude Desktop, add the key as a request header when you create the custom connector. ChatGPT can’t send a key, so it can’t use it.

Does mcp.tc track changes to HotRepo?

Partly. HotRepo’s tools are behind a sign-in, so we can’t read them. Its History tab shows the new versions it reports and edits by its owner. Follow the listing to get an email when it changes.

Who wrote this page?

mcp.tc’s robot read HotRepo’s own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

mcp.tc isn’t affiliated with HotRepo. This page was built from HotRepo’s public metadata, last checked on 18 Nov 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.