Developer · Local MCP server
Reposcout
Discover, enrich, and rank GitHub repos for an objective with weighted, evidence-based scoring.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.Rakesh1002/reposcout- Version
- 0.1.1
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-06-21
- Updated
- 2026-06-21
- Publisher
- Rakesh1002 (GitHub) · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/Rakesh1002) · how
- Listed under
- GitHub MCP servers
- Repository
- github.com/Rakesh1002/reposcout
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @rakeshroushan/reposcout | 0.1.1 | stdio |
How to connect Reposcout
Reposcout runs locally from a Node.js package published to the npm registry: @rakeshroushan/reposcout version 0.1.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @rakeshroushan/reposcout@0.1.1. It reads the environment variable GITHUB_TOKEN (secret); set it in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"reposcout": {
"command": "npx",
"args": [
"-y",
"@rakeshroushan/reposcout@0.1.1"
],
"env": {
"GITHUB_TOKEN": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from Rakesh1002 (GitHub)
| Server | Runs |
|---|---|
| NamemyappBrandable business names with live domain availability + one-click buy URLs. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
More developer servers
| Server | Runs |
|---|---|
| RepoPilotRepository evidence for agents before they adopt dependencies, enter codebases, compare, or merge. | Remote · HTTPLive check: ✓ handshake |
| RepoPilotLocal, deterministic review of Git changes: weakened tests and CI gates, risky flows, blast radius. | Local · stdio |
| RepoRelayBounded local MCP access to one approved repository for AI read/search and structured handoffs. | Local · HTTP |
| RepoRippleDeterministic repository change-impact analysis for engineers and coding agents. | Local · stdio |
| ReposeUptime monitoring that doesn't cry wolf: manage monitors, read incidents, record deploys. | Remote · HTTPLive check: sign-in required |
| RepotectorThe repo guardian AI agents handshake with before they touch your code. | Local · stdio |
| RepovineCheckout-local repository context graph over MCP; `npx repovine setup` wires skills, agents, hooks. | Local · stdio |
| RepowiseCodebase intelligence for AI coding agents - graph, git history, docs, decisions, code health. | Local · stdio |