# io.github.Rakesh1002/reposcout (npm · @rakeshroushan/reposcout)

Discover, enrich, and rank GitHub repos for an objective with weighted, evidence-based scoring.

- Trust score: 58/100 (low)
- Change this week: +40
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `@rakeshroushan/reposcout`: 58/100 (this document), [markdown](https://verifymcp.io/servers/rakesh1002-reposcout/rakeshroushan-reposcout.md), [page](https://verifymcp.io/servers/rakesh1002-reposcout/rakeshroushan-reposcout)

## Channel facts

- Registry: `npm`
- Package: `@rakeshroushan/reposcout`
- Version: `0.1.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-08-03.

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (128 of 132), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (128 of 132), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 19/100
  - Repository check failed: the declared repository URL returned HTTP 404.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 42 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 57/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 309 tokens (~103/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 74/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 22% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add rakesh1002-reposcout -- npx -y @rakeshroushan/reposcout
```

### Codex

```bash
codex mcp add rakesh1002-reposcout -- npx -y @rakeshroushan/reposcout
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "rakesh1002-reposcout": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@rakeshroushan/reposcout"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add rakesh1002-reposcout --command npx --arg -y --arg @rakeshroushan/reposcout
```

### Hermes

```yaml
mcp_servers:
  rakesh1002-reposcout:
    command: "npx"
    args: ["-y", "@rakeshroushan/reposcout"]
```

### Other

```json
{
  "mcpServers": {
    "rakesh1002-reposcout": {
      "command": "npx",
      "args": [
        "-y",
        "@rakeshroushan/reposcout"
      ]
    }
  }
}
```

## 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-08-03 (score 58, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-02 (score 57, +57)

- [security regression] Provenance: unverified → fail
- [security improvement] Install scripts: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Malware scan: unverified → pass
- [functional improvement] License: unverified → pass
- [functional improvement] Schema quality: unverified → fair
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Stability: unverified → 0.23
- [functional improvement] Tool coverage: unverified → 100
- [functional] Licence: MIT

### 2026-07-31 (score 0, −36)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 36, +18)

- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Tool coverage: 22
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: pass
- [functional] First check of Schema quality: unverified

### 2026-07-27 (score 18)

First indexed and scored.

## MCP tools (3)

### `repo_search` (~109 tokens)

Search GitHub repos

Run one or more GitHub repo search queries (use qualifiers like language:, stars:>N, topic:, pushed:>YYYY-MM-DD, archived:false), union and dedupe the results, and return compact records with computed popularity_score and maintenance_score. Craft 3-6 complementary queries from the user's objective.

Input parameters:

- `exclude_archived` (boolean)
- `per_query_limit` (integer)
- `queries` (array, required): GitHub search query strings
- `total_limit` (integer)

### `repo_enrich` (~93 tokens)

Enrich GitHub repos

For a shortlist of repos (owner/name), fetch the README (cleaned, truncated) plus extended metadata and deterministic completeness signals (license, homepage, description, topic count, README size). Results are cached. Use this on the ~10-20 most promising candidates from repo_search before judging relevance and completeness.

Input parameters:

- `full_names` (array, required): Repos as owner/name
- `readme_chars` (integer)

### `repo_rank` (~107 tokens)

Rank repos by weighted score

Combine the four sub-scores into a final ranking. popularity_score and maintenance_score come from repo_search/repo_enrich; relevance_score and completeness_score are your 0-1 judgments. Weights default to relevance 0.4, popularity 0.2, maintenance 0.2, completeness 0.2 and are normalized. Optional hard_filters drop candidates before ranking.

Input parameters:

- `candidates` (array, required)
- `hard_filters` (object)
- `weights` (object)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/rakesh1002-reposcout/rakeshroushan-reposcout#diagnostics

## Score history

- 2026-08-03: 58
- 2026-08-02: 57
- 2026-08-01: 0
- 2026-07-31: 0
- 2026-07-30: 36
- 2026-07-28: 18
- 2026-07-27: 18

## Links

- npm package: https://www.npmjs.com/package/@rakeshroushan/reposcout
- Socket report: https://socket.dev/npm/package/@rakeshroushan/reposcout
- Changelog RSS feed: https://verifymcp.io/servers/rakesh1002-reposcout/rakeshroushan-reposcout/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/rakesh1002-reposcout/rakeshroushan-reposcout/changelog.json
- HTML version of this page: https://verifymcp.io/servers/rakesh1002-reposcout/rakeshroushan-reposcout