CONTRI
Related Servers
Alternatives to CONTRI
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables 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
- AlicenseAqualityAmaintenanceEnables coding agents to check whether a GitHub issue is already taken before volunteering, by analyzing linked PRs, assignees, claimant comments, AI contribution policies, and repo health to return GO, TAKEN, or CAUTION verdicts.376 PyPI2MIT
- AlicenseAqualityBmaintenanceZero-dependency open-source contribution companion: repo rules and AI policy radar, evidence-backed issue briefs, pre-submit checks, and review coaching.9156 PyPI1MIT
- AlicenseNot gradedqualityBmaintenanceEnables 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 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables developers to discover and evaluate contribution opportunities in public GitHub repositories through structured analysis of issues, code, and repository metadata.MIT
- AlicenseAqualityDmaintenanceGuides AI agents through open-source contribution workflows, from finding issues to submitting PRs, while keeping decision-making and coding with the human contributor.2MIT
TDQS
Scored across 9 tools
Each tool targets a distinct step in the contribution workflow: auth, project discovery, issue listing, issue vetting, project health, maintainer responsiveness, and briefing. The only closely overlapping pair is check_issue/check_issues, but the batch-vs-single relationship is explicit and clearly signposted. contribution_brief also sits near check_issue, though the descriptions establish that one is a verdict and the other a source-linked writeup.
All names are snake_case and readable, with a dominant verb_noun pattern (sign_in, check_issue, find_issues, discover_projects). The deviations are the noun-phrase names repo_health, team_responsiveness, and contribution_brief, which break the verb-first convention but remain unambiguous. Singular/plural pairing on check_issue(s) with no find_issue counterpart is a small inconsistency.
Nine tools is well within the ideal range and each earns its place across a coherent workflow (auth → discover → find → verify → brief). No tool looks like filler or a redundant wrapper beyond the intentional batch variant.
The surface covers the full arc of the stated purpose: authentication, project discovery, issue discovery, claim verification, project vitality, maintainer responsiveness, and a contribution brief. Minor gaps exist around outcomes—no way to save/track a shortlisted issue, mark intent, or check PR-side contribution opportunities—but core workflows reach a usable endpoint.