RepoRescue MCP
Related Servers
Alternatives to RepoRescue MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables auditing public GitHub repositories over MCP Streamable HTTP, including classifying URLs, cloning repositories, scanning manifests, CI workflows, and credential signals, and producing findings, file trees, summaries, and PDF reports.MIT
- AlicenseBqualityBmaintenanceEnables read-only, evidence-led security audits of GitHub-hosted source code through explicit workflow primitives: repository reconnaissance, coverage-ledger planning, heuristic candidate leads, structured findings validation, independent verification gates, and JSON/Markdown report generation. It never clones, executes, or probes the target code, and marks runs incomplete until coverage and reviewer-verification gates pass.14AGPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables evidence-grounded implementation research by searching GitHub, scoring candidate repositories, extracting source evidence, and generating planning artifacts like research and implementation checklists.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables read-only GitHub repository inspection and deterministic intelligence through MCP tools for repository metadata, file contents, issue triage, pull-request risk signals, and GitHub Actions failure investigation.MIT
- AlicenseNot gradedqualityCmaintenanceAn evidence-first integration decision service that assesses GitHub repositories and returns transparent scores, adoption recommendations, and verification gates.MIT

repo-doctorofficial
AlicenseNot gradedqualityDmaintenanceMCP server that produces scored, evidence-cited audits of public GitHub repos via tools for fetching metadata, reading files, scanning git history, and checking hygiene.MIT
TDQS
Scored across 4 tools
The four tools have largely distinct roles: probing the Windows environment, running Python snippets, inspecting a GitHub repository, and routing full-project reproduction. The only possible overlap is between rescue_python_snippet and reproduce_python_project, but their descriptions clearly separate snippet-level execution from repository-level routing.
Three tools follow a verb_noun snake_case pattern, while windows_environment_probe is a noun phrase and does not fit the imperative style. The naming is still readable and not chaotic, but the deviation prevents a higher score.
Four tools is a compact, well-scoped count for this server. Each tool has a defined responsibility, and there is no sign of unnecessary duplication or bloat.
The set supports evidence gathering but leaves key rescue workflows incomplete: there is no actual repair/apply operation, no way to run a full project in this server, and reproduce_python_project explicitly refuses to execute. Additionally, windows_environment_probe returns a script but has no matching tool to ingest the result, so agents can easily hit dead ends.