# HotRepo (remote · hotrepo.ai)

GitHub Trending boards and AI-written reviews of trending open-source projects.

- Trust score: 37/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `hotrepo.ai`: 37/100 (this document), [markdown](https://verifymcp.io/servers/ai-hotrepo-hotrepo/hotrepo.md), [page](https://verifymcp.io/servers/ai-hotrepo-hotrepo/hotrepo)

## Channel facts

- Endpoint: `https://hotrepo.ai/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 92/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism.
- **Transport & Reachability**: 0/100
  - Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- **Schema Quality & AI Usability**: 0/100
  - Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Tool Safety**: 0/100
  - Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Capabilities**: 0/100
  - Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

**Unverified: 6 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the HotRepo MCP server?

HotRepo is a hosted endpoint at https://hotrepo.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http ai-hotrepo-hotrepo 'https://hotrepo.ai/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-hotrepo-hotrepo": {
      "type": "remote",
      "url": "https://hotrepo.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-hotrepo-hotrepo --url 'https://hotrepo.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-hotrepo-hotrepo:
    url: "https://hotrepo.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-hotrepo-hotrepo": {
      "Transport": "http",
      "Url": "https://hotrepo.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-hotrepo-hotrepo -t streamable-http -u 'https://hotrepo.ai/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-11 (score 37, −44)

- [security regression] Endpoint reachability: reachable → behind authorisation
- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.47 → unverified
- [security regression] Transport: pass → unverified
- [security regression] HSTS header: pass → fail
- [security improvement] Authorization: fail → pass
- [security] First check of Authorization: pass
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-11-10 (score 81, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-11-09 (score 81, +1)

- [functional regression] Tool coverage: 83% → 75%
- [functional regression] Schema quality: 158 → 185
- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-11-08 (score 80, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-11-07 (score 80, +1)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-11-06 (score 79, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-05 (score 79, +1)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-11-04 (score 78, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

## MCP tools (12)

### `get_trending` (~440 tokens)

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 identifies its UTC timestamp. Other boards compare dates.
    New-board stars_gained is the increment between growth_started_at and growth_observed_at;
    stars_per_hour is that increment divided by the actual window hours (not rounded display hours);
    legacy new-board records without those timestamps return avg_stars_per_day instead.

Input parameters:

- `date`: UTC day YYYY-MM-DD; omit for the latest board. Past days need Pro (Free: latest board only)
- `language` (string): Programming-language board slug such as 'python', 'typescript', 'rust'. Empty string = all languages
- `period` (string): 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).…

### `get_repo` (~137 tokens)

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.

Input parameters:

- `full_name` (string, required): GitHub repository as owner/repo (a github.com URL also works)

### `search_repos` (~93 tokens)

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

Input parameters:

- `limit` (integer)
- `query` (string): Keywords matched against repository name, HotRepo's one-line review and GitHub topics; every word must match. Empty = newest reviews
- `topic`: Topic slug from list_topics to filter by

### `list_topics` (~40 tokens)

List HotRepo's topics (each reviewed project belongs to exactly one, by what it helps people do) with the
    number of reviewed projects in each.

### `get_topic` (~48 tokens)

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

Input parameters:

- `limit` (integer)
- `slug` (string, required): Topic slug from list_topics

### `get_monthly_report` (~80 tokens)

Get a HotRepo monthly report: the repositories that gained the most stars on the daily trending board during
    a month, the most notable new repositories, and leaders per topic, with an editorial introduction.

Input parameters:

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

### `get_weekly_digest` (~307 tokens)

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 removed by HotRepo are dropped and the rest renumbered, and ones without a
    published review link to GitHub (url is null).

Input parameters:

- `week`: ISO week such as 2026-w45 (the week starting that Monday, UTC); omit for the latest issue. Earlier issues need Pro (Free: latest issue only)

### `list_favorites` (~77 tokens)

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.

Input parameters:

- `limit` (integer)

### `get_similar_repos` (~127 tokens)

[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.

Input parameters:

- `full_name` (string, required): GitHub repository as owner/repo (a github.com URL also works)
- `limit` (integer)

### `get_star_history` (~206 tokens)

[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.

Input parameters:

- `full_name` (string, required): GitHub repository as owner/repo (a github.com URL also works)

### `compare_repos` (~217 tokens)

[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.

Input parameters:

- `full_names` (array, required): 2 to 5 GitHub repositories as owner/repo

### `get_favorite_releases` (~169 tokens)

[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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-hotrepo-hotrepo/hotrepo#diagnostics

## Score history

- 2026-11-21: 37
- 2026-11-20: 37
- 2026-11-19: 37
- 2026-11-18: 37
- 2026-11-17: 37
- 2026-11-16: 37
- 2026-11-15: 37
- 2026-11-14: 37
- 2026-11-13: 37
- 2026-11-12: 37
- 2026-11-11: 37
- 2026-11-10: 81
- 2026-11-09: 81
- 2026-11-08: 80
- 2026-11-07: 80
- 2026-11-06: 79
- 2026-11-05: 79
- 2026-11-04: 78
- 2026-11-03: 78
- 2026-11-02: 77
- 2026-11-01: 77
- 2026-10-31: 77
- 2026-10-30: 76
- 2026-10-29: 77
- 2026-10-28: 76
- 2026-10-27: 76
- 2026-10-26: 33
- 2026-10-25: 33

## Common questions

### What is the HotRepo MCP server?

HotRepo is an MCP server listed in the public MCP registry as ai.hotrepo/hotrepo. GitHub Trending boards and AI-written reviews of trending open-source projects. This page covers its hosted endpoint (https://hotrepo.ai/mcp).

### Is the HotRepo MCP server safe to use?

HotRepo scores 37 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the HotRepo MCP server expose?

HotRepo exposes 12 tools: get_trending, get_repo, search_repos, list_topics, get_topic, and 7 more. Their descriptions and schemas cost roughly 1,941 tokens of context every time the server is loaded.

### Does the HotRepo MCP server require authentication?

Yes. HotRepo asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the HotRepo MCP server still maintained?

HotRepo is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the HotRepo MCP server?

VerifyMCP ran 5 checks on HotRepo, covering TLS certificate, Authorization, HTTPS, HSTS header and 1 more. 6 items could not be completed, a gap on our side rather than a finding about HotRepo: Transport, Schema quality, Stability, Tool coverage and 2 more. 6 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://hotrepo.ai/mcp
- Authorisation metadata: https://hotrepo.ai/.well-known/oauth-protected-resource/mcp
- Website: https://hotrepo.ai/mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/ai-hotrepo-hotrepo/hotrepo.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-hotrepo-hotrepo/hotrepo/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ai-hotrepo-hotrepo/hotrepo.json
- HTML version of this page: https://verifymcp.io/servers/ai-hotrepo-hotrepo/hotrepo
