Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

RepoAlerts

REMOTE · REPOALERTS.COM

Rising GitHub repos with fake stars filtered out: search, trending, repo pages, alternatives.

Available components

72 Trust /100

Last scanned (10 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 22 Oct 2026.

Category Code Search and Documentation

Trust breakdown (7 categories)

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 Security80
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1349 tokens (~337/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
  • Stability observed for 2 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

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.

  • 21 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 20 Oct 26 71

    First indexed and scored.

Diagnostics

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 22 Oct 2026 · Probed https://repoalerts.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.repoalerts.com CN=YR1,O=Let's Encrypt,C=US 19 Oct 2026 17 Jan 2027 RSA 2048 SHA256-RSA 665286fcea0b1dd8a64d037244905205405
SANs: *.repoalerts.com, repoalerts.com
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 repoalerts.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
repoalerts.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
strict-transport-security max-age=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://repoalerts.com/mcp Verified 200
http (plaintext) http://repoalerts.com/mcp HTTPS enforced 308 https://repoalerts.com/mcp
MCP tools · 4 exposed · ~1,222 tokens

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 →

Tool Tokens
find_alternatives ~318

Open-source alternatives to an app, product or service ("Photoshop", "Notion", "Heroku", "Postman"), from the GitHub repos RepoAlerts tracks, with real star counts and growth. Optionally for a platform or constraint ("Mac", "self-hosted"). Repos whose own page lists that app as something they replace come first.

NameTypeReqDescription
kindstring–Optional: what the repo is. app (end-user application), mcp_server, agent_skill, agent, template, library, cli, model, resource (lists, docs, courses), other.
limitinteger–How many repos to return, 1 to 10. Default 5.
localestring–Language of the summaries: 'en' (default) or 'es' for Spanish. Use 'es' when the user writes in Spanish.
platformstring–Optional platform or constraint in a few words, e.g. 'Mac', 'self-hosted', 'Windows', 'mobile'.
tostringyesThe app, product or tool to replace, e.g. 'Photoshop', 'Notion', 'Heroku', 'Postman', 'Google Analytics'.
topicstring–Optional topic: agents (AI agents, MCP, LLM tooling), models (ML models, training, inference), infra (databases, devops, backend), creative (image, video, audio, design), desktop (desktop and mobile…
NameTypeReqDescription
attributionstringyes–
notesarray––
reposarrayyes–
totalinteger–Matches in the directory before the limit

No examples provided.

get_repo ~163

Everything RepoAlerts knows about one GitHub repository (owner/name or URL): what it is and who it's for, stars and recent growth, a summary of its star curve, licence, last push, the apps it can replace, Hacker News stories and similar repos. Use it to check a repo before recommending or installing it. If the repo isn't in the directory, it says so (it may be unknown or excluded for fake stars).

NameTypeReqDescription
localestring–Language of the summaries: 'en' (default) or 'es' for Spanish. Use 'es' when the user writes in Spanish.
repostringyesThe repository as 'owner/name' (e.g. 'vercel/next.js'), or its GitHub or RepoAlerts URL.
NameTypeReqDescription
attributionstringyes–
foundbooleanyes–
repoobject|nullyes–

No examples provided.

search_repos ~438

Find real, actively growing open-source GitHub repositories for a need described in plain words ("a calendar MCP server", "free Photoshop alternative for Mac", "self-hosted analytics"). Semantic search over the RepoAlerts directory, which leaves out repos with fake (bought or farmed) stars. Use it instead of recalling package or repo names from memory, whenever the user asks for a tool, library, app, framework or MCP server. Returns for each repo: what it is, who it's for, stars and stars gained in 24 hours and 7 days, licence, last push, its RepoAlerts page and GitHub URL.

NameTypeReqDescription
kindstring–Optional: what the repo is. app (end-user application), mcp_server, agent_skill, agent, template, library, cli, model, resource (lists, docs, courses), other.
languagestring–Optional main programming language as GitHub names it, e.g. 'TypeScript', 'Python', 'Rust', 'C++'.
licensestring–Optional SPDX licence id, e.g. 'MIT', 'Apache-2.0', 'GPL-3.0', 'AGPL-3.0'.
limitinteger–How many repos to return, 1 to 10. Default 5.
localestring–Language of the summaries: 'en' (default) or 'es' for Spanish. Use 'es' when the user writes in Spanish.
min_starsinteger–Optional minimum total stars, e.g. 1000 for established projects.
querystringyesWhat the user needs, in plain words. Examples: 'a calendar MCP server', 'free Photoshop alternative for Mac', 'local-first database', 'rust game engine'.
topicstring–Optional topic: agents (AI agents, MCP, LLM tooling), models (ML models, training, inference), infra (databases, devops, backend), creative (image, video, audio, design), desktop (desktop and mobile…
NameTypeReqDescription
attributionstringyes–
notesarray––
reposarrayyes–
totalinteger–Matches in the directory before the limit

No examples provided.

trending_repos ~303

What's rising on GitHub right now: the repos that gained the most stars today, this week or this month, with star farms filtered out. Optionally only one topic (agents, models, infra, creative, desktop, web) or one kind (app, mcp_server, library…). Use it when the user asks what's new, hot, trending or taking off in open source.

NameTypeReqDescription
kindstring–Optional: what the repo is. app (end-user application), mcp_server, agent_skill, agent, template, library, cli, model, resource (lists, docs, courses), other.
limitinteger–How many repos to return, 1 to 20. Default 10.
localestring–Language of the summaries: 'en' (default) or 'es' for Spanish. Use 'es' when the user writes in Spanish.
periodstring–Window for stars gained: 'today' (last 24 hours, default), 'week' (7 days), 'month' (30 days) or 'year' (repos created this year, by total stars).
topicstring–Optional topic: agents (AI agents, MCP, LLM tooling), models (ML models, training, inference), infra (databases, devops, backend), creative (image, video, audio, design), desktop (desktop and mobile…
NameTypeReqDescription
attributionstringyes–
generated_atstring|null––
notesarray––
periodstring––
reposarrayyes–
totalinteger–Matches in the directory before the limit

No examples provided.

Install

How do I install the RepoAlerts MCP server?

RepoAlerts is a hosted endpoint at https://repoalerts.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 · repoalerts.com

# add to Claude Code
claude mcp add --transport http com-repoalerts-radar 'https://repoalerts.com/mcp'
Common questions

What is the RepoAlerts MCP server?

RepoAlerts is an MCP server listed in the public MCP registry as com.repoalerts/radar. Rising GitHub repos with fake stars filtered out: search, trending, repo pages, alternatives. This page covers its hosted endpoint (https://repoalerts.com/mcp).

Is the RepoAlerts MCP server safe to use?

RepoAlerts scores 72 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 RepoAlerts MCP server expose?

RepoAlerts exposes 4 tools: search_repos, trending_repos, get_repo, find_alternatives. Their descriptions and schemas cost roughly 1,222 tokens of context every time the server is loaded.

Does the RepoAlerts MCP server require authentication?

No. We connected to RepoAlerts without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the RepoAlerts MCP server still maintained?

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