# RepoAlerts (remote · repoalerts.com)

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

- Trust score: 72/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-22

## Components

- remote · `repoalerts.com`: 72/100 (this document), [markdown](https://verifymcp.io/servers/com-repoalerts-radar/repoalerts.md), [page](https://verifymcp.io/servers/com-repoalerts-radar/repoalerts)

## Channel facts

- Endpoint: `https://repoalerts.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-22.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## 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.

### Claude

```bash
claude mcp add --transport http com-repoalerts-radar 'https://repoalerts.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-repoalerts-radar": {
      "url": "https://repoalerts.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-repoalerts-radar": {
      "type": "http",
      "url": "https://repoalerts.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-repoalerts-radar]
url = "https://repoalerts.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-repoalerts-radar": {
      "type": "remote",
      "url": "https://repoalerts.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-repoalerts-radar --url 'https://repoalerts.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-repoalerts-radar:
    url: "https://repoalerts.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-repoalerts-radar": {
      "Transport": "http",
      "Url": "https://repoalerts.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-repoalerts-radar -t streamable-http -u 'https://repoalerts.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-repoalerts-radar": {
      "type": "http",
      "url": "https://repoalerts.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-21 (score 72, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-20 (score 71)

First indexed and scored.

## MCP tools (4)

### `search_repos` (~438 tokens)

Search GitHub repos

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.

Input parameters:

- `kind` (string): Optional: what the repo is. app (end-user application), mcp_server, agent_skill, agent, template, library, cli, model, resource (lists, docs, courses), other.
- `language` (string): Optional main programming language as GitHub names it, e.g. 'TypeScript', 'Python', 'Rust', 'C++'.
- `license` (string): Optional SPDX licence id, e.g. 'MIT', 'Apache-2.0', 'GPL-3.0', 'AGPL-3.0'.
- `limit` (integer): How many repos to return, 1 to 10. Default 5.
- `locale` (string): Language of the summaries: 'en' (default) or 'es' for Spanish. Use 'es' when the user writes in Spanish.
- `min_stars` (integer): Optional minimum total stars, e.g. 1000 for established projects.
- `query` (string, required): What the user needs, in plain words. Examples: 'a calendar MCP server', 'free Photoshop alternative for Mac', 'local-first database', 'rust game engine'.
- `topic` (string): 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…

Output parameters:

- `attribution` (string)
- `notes` (array)
- `repos` (array)
- `total` (integer): Matches in the directory before the limit

### `trending_repos` (~303 tokens)

Trending GitHub repos

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.

Input parameters:

- `kind` (string): Optional: what the repo is. app (end-user application), mcp_server, agent_skill, agent, template, library, cli, model, resource (lists, docs, courses), other.
- `limit` (integer): How many repos to return, 1 to 20. Default 10.
- `locale` (string): Language of the summaries: 'en' (default) or 'es' for Spanish. Use 'es' when the user writes in Spanish.
- `period` (string): Window for stars gained: 'today' (last 24 hours, default), 'week' (7 days), 'month' (30 days) or 'year' (repos created this year, by total stars).
- `topic` (string): 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…

Output parameters:

- `attribution` (string)
- `generated_at` (string|null)
- `notes` (array)
- `period` (string)
- `repos` (array)
- `total` (integer): Matches in the directory before the limit

### `get_repo` (~163 tokens)

Get a repo's RepoAlerts page

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).

Input parameters:

- `locale` (string): Language of the summaries: 'en' (default) or 'es' for Spanish. Use 'es' when the user writes in Spanish.
- `repo` (string, required): The repository as 'owner/name' (e.g. 'vercel/next.js'), or its GitHub or RepoAlerts URL.

Output parameters:

- `attribution` (string)
- `found` (boolean)
- `repo` (object|null)

### `find_alternatives` (~318 tokens)

Find open-source alternatives

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.

Input parameters:

- `kind` (string): Optional: what the repo is. app (end-user application), mcp_server, agent_skill, agent, template, library, cli, model, resource (lists, docs, courses), other.
- `limit` (integer): How many repos to return, 1 to 10. Default 5.
- `locale` (string): Language of the summaries: 'en' (default) or 'es' for Spanish. Use 'es' when the user writes in Spanish.
- `platform` (string): Optional platform or constraint in a few words, e.g. 'Mac', 'self-hosted', 'Windows', 'mobile'.
- `to` (string, required): The app, product or tool to replace, e.g. 'Photoshop', 'Notion', 'Heroku', 'Postman', 'Google Analytics'.
- `topic` (string): 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…

Output parameters:

- `attribution` (string)
- `notes` (array)
- `repos` (array)
- `total` (integer): Matches in the directory before the limit

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-repoalerts-radar/repoalerts#diagnostics

## Score history

- 2026-10-22: 72
- 2026-10-21: 72
- 2026-10-20: 71

## 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.

## Links

- Remote endpoint: https://repoalerts.com/mcp
- Website: https://repoalerts.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-repoalerts-radar/repoalerts.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-repoalerts-radar/repoalerts.json
- HTML version of this page: https://verifymcp.io/servers/com-repoalerts-radar/repoalerts