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

io.github.Rakesh1002/reposcout

NPM · @RAKESHROUSHAN/REPOSCOUT · SCANNED AUG 3

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

+40 this week 58 Trust /100
Trust breakdown (6 categories)

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. How we score →

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

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @rakeshroushan/reposcout

# add to Claude Code
claude mcp add rakesh1002-reposcout -- npx -y @rakeshroushan/reposcout
# add to Codex CLI
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
    }
  }
}
# add to OpenClaw
openclaw mcp add rakesh1002-reposcout --command npx --arg -y --arg @rakeshroushan/reposcout
# ~/.hermes/config.yaml
mcp_servers:
  rakesh1002-reposcout:
    command: "npx"
    args: ["-y", "@rakeshroushan/reposcout"]
// mcp.json
{
  "mcpServers": {
    "rakesh1002-reposcout": {
      "command": "npx",
      "args": [
        "-y",
        "@rakeshroushan/reposcout"
      ]
    }
  }
}
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.

  • 3 Aug 26 +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.

  • 2 Aug 26 +57
    • Provenance: unverified → fail security
    • Install scripts: unverified → pass security
    • Known CVEs: unverified → partial security
    • Malware scan: unverified → pass security
    • License: unverified → pass functional
    • Schema quality: unverified → fair functional
    • Dependency health: unverified → partial functional
    • Maintenance: unverified → pass functional
    • MCP protocol: unverified → pass functional
    • Stability: unverified → 0.23 functional
    • Tool coverage: unverified → 100 functional
    • Licence: MIT functional
  • 31 Jul 26 −36
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 +18
    • 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 functional
  • 27 Jul 26 18

    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 3 Aug 2026 · Analysed npm/@rakeshroushan/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 128 packages

128 packages in the resolved dependency tree · 128 deprecated · 30 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 3 exposed · ~309 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.

Tool Tokens
repo_enrich ~93

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.

NameTypeReqDescription
full_namesarrayyesRepos as owner/name
readme_charsinteger

No output schema declared.

No examples provided.

repo_rank ~107

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.

NameTypeReqDescription
candidatesarrayyes
hard_filtersobject
weightsobject

No output schema declared.

No examples provided.

repo_search ~109

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.

NameTypeReqDescription
exclude_archivedboolean
per_query_limitinteger
queriesarrayyesGitHub search query strings
total_limitinteger

No output schema declared.

No examples provided.