Skip to content

RepoTrending MCP server

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

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the RepoTrending MCP server can do

The RepoTrending MCP server is published by the GitHub account sinhgiang. It has 5 tools. It can create or change data (1 tool: how_we_rank), but cannot delete data. 4 tools only read.

4 tools read private data (get_trending, get_repo, search_repos and 1 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 10, 2026, version 0.1.0.

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.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 19, 2026, 17:24 UTC, unchanged since Oct 28, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.repotrending.com/mcp: tools/list returned 5 tools to an anonymous client, including how_we_rank (write)

    What this check looks for

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://radar.anlyon.com/api/v1/servers/io.github.sinhgiang/repotrending/verify?hash=961cca71ef62661a977b6d2526f7b42b09d395dcf51e60d4b803fbf43d8b1b05" | jq -e '.changed == false'

Pinned hash 961cca71ef62, from Nov 10, 2026, 00:18 UTC.

Watch

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

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

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

Badge

Anlyon Radar badge for io.github.sinhgiang/repotrending
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.sinhgiang/repotrending.svg)](https://radar.anlyon.com/servers/io.github.sinhgiang/repotrending)

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

RepoTrending MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the RepoTrending MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the RepoTrending MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the RepoTrending MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the RepoTrending MCP server have?

5 tools: 1 write, 4 read. how_we_rank, get_trending, get_repo, search_repos and list_filters.

Does the RepoTrending MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the RepoTrending MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the RepoTrending MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.