HotRepo
REMOTE · HOTREPO.AI
GitHub Trending boards and AI-written reviews of trending open-source projects.
Available components
Last scanned (13 hours ago)
Scores higher than 25% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Version Control
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. How we score → Why this is hard to score →
Endpoint Security92
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
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. Claim this server and supply a read-only token to verify it and lift the score.
Checks we ran (5)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
Checks we could not complete (6)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Transport in Transport & Reachability (scores 0 for this)Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Tool safety in Tool Safety (scores 0 for this)Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Capabilities in Capabilities (scores 0 for this)Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 11 Nov 26 −44
- Endpoint reachability: reachable → behind authorisation ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.47 → unverified ▼ security
- Transport: pass → unverified ▼ security
- HSTS header: pass → fail ▼ security
- Authorization: fail → pass ▲ security
- First check of Authorization: pass security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 10 Nov 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 9 Nov 26 +1
- Tool coverage: 83% → 75% ▼ functional
- 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 functional
- 8 Nov 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 7 Nov 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Nov 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 4 Nov 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://hotrepo.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=hotrepo.ai | CN=YR1,O=Let's Encrypt,C=US | 24 Oct 2026 | 22 Jan 2027 | RSA 2048 | SHA256-RSA | 5a2c01961f0e25f921ffbc8093d216788e2 |
| SANs: hotrepo.ai, www.hotrepo.ai | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of hotrepo.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814 | 8 | Verified |
| hotrepo.ai. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer resource_metadata="https://hotrepo.ai/.well-known/oauth-protected-resource/mcp"
Bearer resource_metadata="https://hotrepo.ai/.well-known/oauth-protected-resource/mcp" | Header | Value |
|---|---|
| www-authenticate | Bearer resource_metadata="https://hotrepo.ai/.well-known/oauth-protected-resource/mcp" |
Protected resource metadata
| Document | https://hotrepo.ai/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://hotrepo.ai/mcp |
| Authorisation server | https://hotrepo.ai |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://hotrepo.ai/mcp | Auth required | 401 | |
| http (plaintext) | http://hotrepo.ai/mcp | HTTPS enforced | 301 | https://hotrepo.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compare_repos ~217
[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.
| Name | Type | Req | Description |
|---|---|---|---|
| full_names | array | yes | 2 to 5 GitHub repositories as owner/repo |
Structured output declared, but exposes no named fields.
No examples provided.
get_favorite_releases ~169
[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.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_monthly_report ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| month | – | – | YYYY-MM (a finished UTC month); omit for the latest report. Earlier reports need Pro (Free: latest report only) |
Structured output declared, but exposes no named fields.
No examples provided.
get_repo ~137
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.
| Name | Type | Req | Description |
|---|---|---|---|
| full_name | string | yes | GitHub repository as owner/repo (a github.com URL also works) |
Structured output declared, but exposes no named fields.
No examples provided.
get_similar_repos ~127
[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.
| Name | Type | Req | Description |
|---|---|---|---|
| full_name | string | yes | GitHub repository as owner/repo (a github.com URL also works) |
| limit | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_star_history ~206
[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.
| Name | Type | Req | Description |
|---|---|---|---|
| full_name | string | yes | GitHub repository as owner/repo (a github.com URL also works) |
Structured output declared, but exposes no named fields.
No examples provided.
get_topic ~48
List reviewed repositories in one topic, most recently trending first. Free returns at most 10 per call.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| slug | string | yes | Topic slug from list_topics |
Structured output declared, but exposes no named fields.
No examples provided.
get_trending ~440
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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).… |
Structured output declared, but exposes no named fields.
No examples provided.
get_weekly_digest ~307
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
Structured output declared, but exposes no named fields.
No examples provided.
list_favorites ~77
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_topics ~40
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.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
search_repos ~93
Search repositories that HotRepo has reviewed, newest reviews first. Use get_repo for the full review. Free returns at most 10 results per call.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
Structured output declared, but exposes no named fields.
No examples provided.
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.
remote · hotrepo.ai
claude mcp add --transport http ai-hotrepo-hotrepo 'https://hotrepo.ai/mcp'
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.