io.github.Rakesh1002/reposcout
NPM · @RAKESHROUSHAN/REPOSCOUT · SCANNED SEP 20
Discover, enrich, and rank GitHub repos for an objective with weighted, evidence-based scoring.
Available components
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 → Why this is hard to score →
Supply Chain Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 32 of 129 dependencies flagged as unhealthy. 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 90 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- 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 Management97
- Stability observed for 29 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.Rakesh1002/reposcout MCP server?
io.github.Rakesh1002/reposcout runs locally as an npm package, launched with npx -y @rakeshroushan/reposcout. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @rakeshroushan/reposcout
claude mcp add rakesh1002-reposcout -- npx -y @rakeshroushan/reposcout
{
"mcpServers": {
"rakesh1002-reposcout": {
"command": "npx",
"args": [
"-y",
"@rakeshroushan/reposcout"
]
}
}
} {
"servers": {
"rakesh1002-reposcout": {
"command": "npx",
"args": [
"-y",
"@rakeshroushan/reposcout"
]
}
}
} codex mcp add rakesh1002-reposcout -- npx -y @rakeshroushan/reposcout
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"rakesh1002-reposcout": {
"type": "local",
"command": [
"npx",
"-y",
"@rakeshroushan/reposcout"
],
"enabled": true
}
}
} openclaw mcp add rakesh1002-reposcout --command npx --arg -y --arg @rakeshroushan/reposcout
mcp_servers:
rakesh1002-reposcout:
command: "npx"
args: ["-y", "@rakeshroushan/reposcout"] {
"McpServers": {
"rakesh1002-reposcout": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@rakeshroushan/reposcout"
]
}
}
} assistant mcp add rakesh1002-reposcout -t stdio -c npx -a -y @rakeshroushan/reposcout
{
"mcpServers": {
"rakesh1002-reposcout": {
"command": "npx",
"args": [
"-y",
"@rakeshroushan/reposcout"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 −3
- Stability: pass → 0.80 functional
- 14 Sept 26 +1
- Stability: 0.97 → pass security
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 −3
- Stability: pass → 0.80 functional
- 7 Sept 26 +1
- Stability: 0.97 → pass security
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 20 Sept 2026 · Analysed npm/@rakeshroushan/reposcout@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 129 packages
| Packages resolved | 129 |
|---|---|
| Stale | 32 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
repo_enrich Enrich GitHub repos ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| full_names | array | yes | Repos as owner/name |
| readme_chars | integer | – | – |
No output schema declared.
No examples provided.
repo_rank Rank repos by weighted score ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| candidates | array | yes | – |
| hard_filters | object | – | – |
| weights | object | – | – |
No output schema declared.
No examples provided.
repo_search Search GitHub repos ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| exclude_archived | boolean | – | – |
| per_query_limit | integer | – | – |
| queries | array | yes | GitHub search query strings |
| total_limit | integer | – | – |
No output schema declared.
No examples provided.
What is the io.github.Rakesh1002/reposcout MCP server?
io.github.Rakesh1002/reposcout is an MCP server listed in the public MCP registry as io.github.Rakesh1002/reposcout. Discover, enrich, and rank GitHub repos for an objective with weighted, evidence-based scoring. This page covers its npm package (@rakeshroushan/reposcout).
Is the io.github.Rakesh1002/reposcout MCP server safe to use?
io.github.Rakesh1002/reposcout scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 io.github.Rakesh1002/reposcout MCP server expose?
io.github.Rakesh1002/reposcout exposes 3 tools: repo_search, repo_enrich, repo_rank. Their descriptions and schemas cost roughly 309 tokens of context every time the server is loaded.
Is the io.github.Rakesh1002/reposcout MCP server still maintained?
io.github.Rakesh1002/reposcout is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.Rakesh1002/reposcout MCP server under?
io.github.Rakesh1002/reposcout declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.