Skip to main content
Glama
wenjieding327

RepoRescue MCP

by wenjieding327
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to RepoRescue MCP

No user-submitted related servers found.

    Related Servers

    • Claude MCP Workbench

      fotiosb
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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.
      21 npm
      MIT

    • ProofScope

      YoungblutSchilling
      A
      license
      Not graded
      quality
      A
      maintenance
      An evidence-first integration decision service that assesses GitHub repositories and returns transparent scores, adoption recommendations, and verification gates.
      MIT
    • repo-doctor by Infojitsu

      repo-doctorofficial

      Infojitsu
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP 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

    • Custom Python MCP Server

      razi2004
      A
      license
      Not graded
      quality
      C
      maintenance
      Exposes repository reconnaissance tools — file listing and verbatim reading, regex search, dependency-tree parsing across Python/Node/Rust/Go, and test-coverage ingestion — so agents can gather line-numbered evidence from real source files. This lets an audit pipeline physically re-verify every claim and drop findings that cannot be located in the code.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 4 tools

    Disambiguation4/5

    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.

    Naming Consistency3/5

    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.

    Tool Count5/5

    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.

    Completeness2/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources