RepoTrending
REMOTE · MCP.REPOTRENDING.COM
Read-only GitHub trending data: top repos by stars gained today, this week or this month.
Available components
Last scanned (21 hours ago)
Scores higher than 54% of remote servers
Reachable. Last reached 4 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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 415 tokens (~83/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 28 Oct 26 66
First indexed and scored.
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 4 Nov 2026 · Probed https://mcp.repotrending.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=repotrending.com | CN=WE1,O=Google Trust Services,C=US | 28 Oct 2026 | 26 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | c024b000e0038d330e5f4557ddae4dc4 |
| SANs: repotrending.com, mcp.repotrending.com, *.mcp.repotrending.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.repotrending.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| repotrending.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.repotrending.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.repotrending.com/mcp | Inconclusive | 405 |
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 →
get_repo One GitHub repo ~51
Details of one tracked repo by owner/name: stars, forks, language, license, topics, star counts of the last days, gains and ranks per window.
| Name | Type | Req | Description |
|---|---|---|---|
| repo | string | yes | Repo as owner/name. |
| Name | Type | Req | Description |
|---|---|---|---|
| collecting_since | string | yes | First day of collected data, YYYY-MM-DD. |
| created_at | string | yes | – |
| data_date | string | yes | Day of the latest snapshot, YYYY-MM-DD. |
| description | string | yes | – |
| first_seen | – | yes | – |
| forks | integer | yes | – |
| github_url | string | yes | – |
| language | string | yes | – |
| license | string | yes | – |
| method_url | string | yes | Page that explains how the numbers are made. |
| note | string | yes | – |
| rank | object | yes | – |
| repo | string | yes | – |
| source | string | yes | – |
| stars | integer | yes | – |
| stars_by_day | array | yes | Total stars at each daily snapshot, oldest first (up to 31). |
| stars_gained | object | yes | – |
| text_note | string | yes | – |
| topics | array | yes | – |
| url | string | yes | – |
No examples provided.
get_trending Trending GitHub repos ~135
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.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Programming language, for example "Rust". |
| limit | integer | – | How many repos to return (1 to 25). |
| topic | string | – | GitHub topic, for example "mcp". |
| window | string | – | today = last 24 hours, week = 7 days, month = 30 days, all = total stars. |
| Name | Type | Req | Description |
|---|---|---|---|
| collecting_since | string | yes | First day of collected data, YYYY-MM-DD. |
| count | integer | yes | – |
| data_date | string | yes | Day of the latest snapshot, YYYY-MM-DD. |
| language | – | yes | – |
| method_url | string | yes | Page that explains how the numbers are made. |
| note | string | yes | – |
| repos | array | yes | – |
| repos_in_filter | integer | yes | – |
| source | string | yes | – |
| text_note | string | yes | – |
| topic | – | yes | – |
| truncated | boolean | yes | – |
| window | string | yes | – |
| window_status | object | yes | – |
No examples provided.
how_we_rank How the rankings are made ~38
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| collecting_since | string | yes | First day of collected data, YYYY-MM-DD. |
| data_date | string | yes | Day of the latest snapshot, YYYY-MM-DD. |
| limits | array | yes | – |
| method_url | string | yes | Page that explains how the numbers are made. |
| repos_available | integer | yes | – |
| repos_tracked | integer | yes | – |
| source | string | yes | – |
| summary | array | yes | – |
| windows | object | yes | – |
No examples provided.
list_filters Languages and topics ~66
List the languages or the GitHub topics that get_trending and search_repos accept, with how many tracked repos each has. Most repos first.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | Which list to return. |
| limit | integer | – | How many names to return (1 to 100). |
| Name | Type | Req | Description |
|---|---|---|---|
| collecting_since | string | yes | First day of collected data, YYYY-MM-DD. |
| count | integer | yes | – |
| data_date | string | yes | Day of the latest snapshot, YYYY-MM-DD. |
| items | array | yes | – |
| kind | string | yes | – |
| method_url | string | yes | Page that explains how the numbers are made. |
| source | string | yes | – |
| total | integer | yes | – |
| truncated | boolean | yes | – |
No examples provided.
search_repos Search tracked repos ~84
Find tracked repos by words in the name, description, topics or language. Every word must match. Results are ordered by relevance, then stars.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Only repos in this language. |
| limit | integer | – | How many repos to return (1 to 25). |
| query | string | yes | Words to look for, for example "vector database". |
| Name | Type | Req | Description |
|---|---|---|---|
| collecting_since | string | yes | First day of collected data, YYYY-MM-DD. |
| count | integer | yes | – |
| data_date | string | yes | Day of the latest snapshot, YYYY-MM-DD. |
| language | – | yes | – |
| matches | integer | yes | – |
| method_url | string | yes | Page that explains how the numbers are made. |
| repos | array | yes | – |
| source | string | yes | – |
| text_note | string | yes | – |
| truncated | boolean | yes | – |
No examples provided.
How do I install the RepoTrending MCP server?
RepoTrending is a hosted endpoint at https://mcp.repotrending.com/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 · mcp.repotrending.com
claude mcp add --transport http sinhgiang-repotrending 'https://mcp.repotrending.com/mcp'
What is the RepoTrending MCP server?
RepoTrending is an MCP server listed in the public MCP registry as io.github.sinhgiang/repotrending. Read-only GitHub trending data: top repos by stars gained today, this week or this month. This page covers its hosted endpoint (https://mcp.repotrending.com/mcp).
Is the RepoTrending MCP server safe to use?
RepoTrending scores 69 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 RepoTrending MCP server expose?
RepoTrending exposes 5 tools: get_trending, get_repo, search_repos, list_filters, how_we_rank. Their descriptions and schemas cost roughly 374 tokens of context every time the server is loaded.
Does the RepoTrending MCP server require authentication?
No. We connected to RepoTrending without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the RepoTrending MCP server still maintained?
RepoTrending is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.