Skip to main content
Glama

Related Servers

Alternatives to taken

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables an agent to check a repository's contribution rules (AI policy, CLA/DCO, assignment and claim windows) and an issue's status (linked open, merged and closed PRs, active claims, merge friendliness) before writing any code. It returns a go, comment & claim first, or don't verdict with the rule or PR evidence behind each reason, reading only and never opening PRs or posting comments.
      354 npm
      MIT
    • 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
      B
      maintenance
      Enables agents to vet a GitHub issue before committing time to it, returning a landability verdict (GO, RISKY, TAKEN, GATED, STALE) plus repo friction scores, gate evidence, and ranked scans of a repository's starter issues. Also exposes contribution automation tools that draft claim comments, prep a fork and branch with a repo-specific checklist, and open a pull request once basics like DCO sign-off pass, with all writes dry-run by default.
      656 npm
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables coding agents to check whether a GitHub issue is ready to hand off before starting work, predicting the files and tests the fix will touch from the live checkout and holding back under-specified issues with a single clarifying question.
      2
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables coding agents to verify whether a GitHub pull request is genuinely ready by checking draft state, conflicts, check results on the head commit, review requirements, merge queue status, and expected commit, returning a verdict with reasons and owners pinned to a commit and timestamp. It reports merged or closed PRs without judging them and never authorizes a merge.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      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.
      222 npm
      2
      MIT

    TDQS

    A3.9/5.0

    Scored across 3 tools

    Disambiguation5/5

    The three tools operate at clearly distinct scopes: check_issue inspects a single issue, scan_repo scans one repository's open issues, and discover_candidates searches GitHub globally. An agent can trivially select the right tool based on whether it has an issue number, a repo, or neither.

    Naming Consistency5/5

    All three names follow a clean verb_noun snake_case pattern (check_issue, scan_repo, discover_candidates). The verbs are also semantically meaningful and distinct, reinforcing the scope separation.

    Tool Count4/5

    Three tools is on the thin side but each maps to a genuinely different granularity (single issue, single repo, global discovery), so none is redundant. The focused domain justifies the small surface.

    Completeness4/5

    The single→repo→global progression covers the core workflow of finding and vetting contribution targets, with consistent error and metadata handling across tools. Minor gaps exist (e.g. no batch check of an explicit issue list or PR-level inspection), but agents can work around them via scan_repo.

    Maintenance

    ActivityActive
    ResponsivenessUsually handled