Skip to main content
Glama

Related Servers

Alternatives to taken

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to evaluate real OSS contribution opportunities by scoring issues on availability, competing PRs, staleness, and maintainer sentiment, including live feasibility checks for any repository.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables coding agents to scout, rank, and preflight software work before implementation, returning evidence-backed ACT, VERIFY, or SKIP decisions for issues and pull requests.
      60 npm
      2
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to scan for verified, uncontested GitHub bounty issues and audit specific issue URLs before writing code, filtering out honeypots and competition.
      -
    • -
      license
      B
      quality
      Not graded
      maintenance
      Enables AI-driven orchestration of GitHub development workflows including automated issue analysis, code generation, code review, and PR creation through multiple specialized agents. Integrates with GitHub Actions to automate the complete development process from issue to pull request.
      7
      -
    • A
      license
      A
      quality
      B
      maintenance
      Lets agents read a GitHub repository's live issues through read-only tools for listing, filtering, fetching details with comments and cross-references, searching, and exploring labels and milestones, with transparent pagination and provenance notes.
      5
      MIT

    TDQS

    A4.1/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct scope: check_issue handles a single issue, scan_repo covers a repository's open issues, and discover_candidates searches globally across GitHub. There is no overlap in their primary inputs or outputs, making selection unambiguous.

    Naming Consistency5/5

    All three tool names follow the same verb_noun snake_case pattern: check_issue, scan_repo, discover_candidates. The verbs clearly indicate the action (check, scan, discover) and the nouns the target (issue, repo, candidates), maintaining a predictable convention.

    Tool Count5/5

    With exactly 3 tools, the server is tightly scoped to its purpose of finding and vetting contribution-worthy issues. Each tool occupies a distinct niche (specific, repo-level, and global discovery), and no tool feels redundant or unnecessary for the domain.

    Completeness4/5

    The tool surface covers the full lifecycle of discovery and verification: global search (discover_candidates), repo-wide filtering (scan_repo), and per-issue assessment (check_issue). A minor gap is the lack of a tool to directly mark or claim an issue, but that is outside the stated purpose of evaluating availability, so the coverage is nearly complete.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive