Skip to content

RepoTrending

io.github.sinhgiang/repotrendingsinhgiangstreamable-httpv0.1.0Scanned

Read-only GitHub trending data: top repos by stars gained today, this week or this month.

5 tools: 1 change things and 4 only read.

Tools: 0 delete, 0 irreversible, 1 write, 4 read.
  • Reads private data · 4
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Anlyon alternative

1 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

5 tools

Changes things 1Claude Code: ask
  • how_we_rankPlain explanation of how RepoTrending counts stars gained, which repos it tracks, what it leaves out and how much data each window has so far.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: How the rankings are made
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 4Show 4 read-only tools
  • get_repoDetails of one tracked repo by owner/name: stars, forks, language, license, topics, star counts of the last days, gains and ranks per window.Reads private dataNo findings

    Why it is in this group

    • The name "get_repo" says "get": a word for reading.

    What it can reach

    • private-dataThe name "get_repo" says "get" and "repo": it reads repositories.
    • private-dataThe description's first sentence says "repo": it reads repositories.
    • private-dataThe input names a repo (input.repo), and the tool reads: it reads repositories.
    Description, as the server wrote it
    Details of one tracked repo by owner/name: stars, forks, language, license, topics, star counts of the last days, gains and ranks per window.

    Annotations the server declares

    • title: One GitHub repo
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_filtersList the languages or the GitHub topics that get_trending and search_repos accept, with how many tracked repos each has.Reads private dataNo findings

    Why it is in this group

    • The name "list_filters" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "repo": it reads repositories.
    Description, as the server wrote it
    List the languages or the GitHub topics that get_trending and search_repos accept, with how many tracked repos each has. Most repos first.

    Annotations the server declares

    • title: Languages and topics
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_reposFind tracked repos by words in the name, description, topics or language.Reads private dataNo findings

    Why it is in this group

    • The name "search_repos" says "search": a word for reading.

    What it can reach

    • private-dataThe name "search_repos" says "search" and "repo": it reads repositories.
    • private-dataThe description's first sentence says "find" and "repo": it reads repositories.
    Description, as the server wrote it
    Find tracked repos by words in the name, description, topics or language. Every word must match. Results are ordered by relevance, then stars.

    Annotations the server declares

    • title: Search tracked repos
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data4
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http repotrending https://mcp.repotrending.com/mcp
claude mcp add --transport http repotrending https://mcp.repotrending.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__repotrending__get_trending",
      "mcp__repotrending__get_repo",
      "mcp__repotrending__search_repos",
      "mcp__repotrending__list_filters"
    ],
    "ask": [
      "mcp__repotrending__how_we_rank"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as repotrending. Review it before you use it.

Capability tags behind 4 rules
  • mcp__repotrending__get_trending private-data
  • mcp__repotrending__get_repo private-data
  • mcp__repotrending__search_repos private-data
  • mcp__repotrending__list_filters private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://anlyon.dev/api/v1/servers/io.github.sinhgiang/repotrending/verify?hash=961cca71ef62661a977b6d2526f7b42b09d395dcf51e60d4b803fbf43d8b1b05" | jq -e '.changed == false'

Pinned hash 961cca71ef62, from Oct 28, 2026, 16:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/io.github.sinhgiang/repotrending/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

anlyon.dev badge for io.github.sinhgiang/repotrending
[![anlyon.dev](https://anlyon.dev/badge/io.github.sinhgiang/repotrending.svg)](https://anlyon.dev/servers/io.github.sinhgiang/repotrending)

Source: MCP Registry. Synced Oct 28, 2026, 17:17 UTC.