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 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.
      2,061 npm
      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.
      38 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables agents and developers to check, before they comment or write code, which issue claims have gone stale and which finished fork branches never became a pull request. It ranks abandoned claims oldest-first, flags parked branches with compare data, and reports every claimant and linked PR for a single issue.
      72 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Gives AI coding agents a local, mechanical workflow authority: an agent's issue claim is recorded, every subsequent write and irreversible step (push, merge, tag, release) is re-verified against that record, and review verdicts are bound to exact commit bytes so a later push invalidates them. Refusals report what was read and what to do next, keeping an unreadable tracker distinct from a forbidden action.
      1
      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.
      -

    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

    ActivityMaintained
    ResponsivenessResponsive