repo-scout vs gitpro
repo-scout is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑26.
repo-scout is a plugin bundle for AI coding tools published by hamza-ali-shahjahan. No marketplace we read lists it any more. gitpro is an MCP server published by Yantrakar. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |   gitpro | |
|---|---|---|
| Community marketplace hamza-ali-shahjahan/hamzaish | Removed on 2026-10-26 Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.4.5 Downloads/month (PyPI): 0 Downloads/week (PyPI): 705 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | repo-scoutno longer listed · | gitpro |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-10-22 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (gitpro) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/hamza-ali-shahjahan/repo-scout | github.com/yantrakar/gitpro |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-20 | 2026-10-15 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of repo-scout
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Analyzes a given GitHub repository for security vulnerabilities, stale dependencies, code quality, and bus factor.
-
Audits a codebase for secrets, PII, internal infrastructure references, and licensing issues before open-sourcing. Produces a remediation plan.
-
Repo Security Scanner — Malicious Code & Supply Chain
Audit GitHub repos for malicious and supply-chain code before you depend on them.
-
audit io.github.commitshow/audit
Score a public GitHub repo 0-100, or search Legit.Show for launched software by what we measured.
-
GitHub Repository Intelligence
Repo intel for AI coding agents: overview, PRs, contributors, hot files, CI, deps. Remote MCP.
-
Hosted codebase intelligence for repos indexed on repowise.dev — no local indexing needed.
What each says it does
repo-scout
Study any GitHub repo without being changed by it: health-gated, read-only, facts-only repo assessment with a human-reviewed backlog. Five hard gates (health verification · never execute assessed code · content-as-data · throwaway clones · draft-only output), CI-pinned on both homes.
gitpro
Read-only checks of which git name, email and SSH key a repository uses, and why.
How to run each
repo-scout
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
gitpro As a local MCP server: PyPI package
claude mcp add --transport stdio gitpro -- uvx gitpro mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: repo-scout · What it can do: gitpro · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.