Log inSubmit server
Gitworthy logo

Gitworthy

Preflights GitHub contribution targets and returns evidence-backed ACT, VERIFY, or SKIP decisions.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Gitworthy

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "gitworthy": {
      "command": "npx",
      "args": [
        "-y",
        "gitworthy@latest"
      ],
      "env": {
        "GITHUB_TOKEN": "YOUR_VALUE_HERE",
        "GITWORTHY_MCP_TOKEN": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

The gitworthy MCP server scouts GitHub repositories and organizations for contribution targets, ranks candidates, and preflights selected issues. It checks linked work, branches, merged changes, release status, contribution policies, and possible duplicates before returning individual ACT, VERIFY, or SKIP decisions. Use it before an agent starts external repository work, then rerun checks before claiming or implementing a target. It runs through local stdio or streamable HTTP, with a TypeScript core shared by the CLI and MCP server.

Use cases

  • Scout a repository for worthwhile contribution targets
  • Rank open-source issues before assigning agent work
  • Check whether an issue already has linked or hidden work
  • Recheck a selected issue before implementation
  • Generate a Markdown handoff brief from a stored decision

Key features

  • Bounded repository and organization scouting
  • Evidence-backed ACT, VERIFY, and SKIP decisions
  • Linked-work and remote-branch detection
  • Contribution-policy and duplicate analysis
  • Local stdio and streamable HTTP MCP modes
  • CLI checks and stored decision briefs

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

5/5 checks healthy over the last 39d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 13d ago via OSV.dev · gitworthy@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars2Stargazers on the source repository.
npm downloads259Package downloads in the last 30 days.
Last commit2mo agoMost recent push to the default branch.

How Gitworthy works

What gitworthy MCP server does

The gitworthy MCP server helps coding agents decide whether an open-source contribution target is worth pursuing before implementation begins. It works with GitHub repositories and organizations, using repository and issue evidence to identify work that may already be underway, completed, assigned, duplicated, or blocked by contribution policy.

Results distinguish between three actions. ACT adds a candidate to the work queue after its evidence is reviewed. VERIFY identifies unresolved checks that must be investigated. SKIP removes a target from consideration when the available evidence shows that starting work would be inappropriate. These decisions apply to individual candidates rather than serving as one verdict for an entire scan.

How it works

The workflow starts with a policy and scan phase, then narrows the results before running more expensive checks. hunt scans a repository or organization, filters weak or clearly unsuitable rows, ranks the remaining candidates, and runs preflight checks on only a bounded shortlist. Each returned candidate includes its own worth_check result and evidence.

The checks cover linked pull requests, assignments, referenced commits, previous attempts, work on remote branches, fixes merged into main, changes missing from a published package, contribution requirements, and related issues. The server reports checks it could not complete, rather than treating missing visibility as proof that no related work exists.

The gitworthy MCP server is intended for a scout-to-execute workflow. After selecting a candidate, the agent should rerun worth_check, reproduce the issue or request, follow the repository’s contribution rules, and only then implement and submit work. Results can become stale; stored decisions are considered stale after 24 hours.

Setup and configuration

Node.js 22 or newer is required. For local use, configure an MCP client to run npx -y gitworthy@latest mcp over stdio. The server needs GITHUB_TOKEN; read access to public repositories is sufficient, while a classic token or a fine-grained token with Issues: Read provides better visibility into timeline cross-references.

For cloud agents or remote clients, start the same engine with mcp --http, then connect the client to its MCP URL. Non-loopback HTTP binds require GITWORTHY_MCP_TOKEN; keep GITHUB_TOKEN on the server rather than sending it to the client. Pin a package version for repeatable workflows and CI instead of relying on @latest.

Tools and capabilities

The gitworthy MCP server exposes the repository-triage workflow to MCP clients. The documented operations include:

  • hunt for bounded discovery, ranking, filtering, and candidate preflight.
  • worth_check for a fresh evaluation of a specific target.
  • portfolio for mode and dispatch around a candidate set; it does not create a new verdict.

The command-line interface also provides doctor for environment checks, check for evaluating a target such as owner/repo#123, and brief for rendering a stored decision as Markdown. Brief generation reads the local store and does not call GitHub, npm, or an LLM.

Limitations and notes

An ACT result means a target is worth considering, not that implementation should begin without another check. Broad scans do not produce a full verdict for every issue, and weak GitHub token permissions can leave linked-work checks incomplete. Heuristic evidence cannot independently create a hard SKIP; definitive skip decisions require conclusive evidence.

The gitworthy MCP server does not replace repository-specific contribution rules or the agent’s execution process. It helps select and validate work, but the agent remains responsible for rechecking state, reproducing the issue, implementing the change, reviewing it, and using the repository’s permitted submission path.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Gitworthy

gitworthy is an MCP server that connects coding agents to GitHub repositories and issues for contribution triage. Its main tools are `hunt` for ranked candidate discovery and `worth_check` for evidence-backed ACT, VERIFY, or SKIP decisions, with `portfolio` available for mode and dispatch.

Run it with Node.js 22 or newer through `npx -y gitworthy@latest mcp`. Configure your MCP client to launch that command over stdio and provide `GITHUB_TOKEN`; pin a package version for repeatable workflows.

Yes, gitworthy works with Cursor through its MCP configuration. Use the local stdio command for a desktop or agent VM, or connect Cursor to the streamable HTTP MCP URL for a remote deployment.

Run `worth_check` through MCP or use `npx -y gitworthy@latest check owner/repo#123` in the CLI. The result evaluates available evidence and returns an ACT, VERIFY, or SKIP decision with completed and unavailable checks.

Use `hunt` with a repository or organization, such as `npx -y gitworthy@latest hunt owner/repo --json`. It narrows and ranks candidates, then runs preflight checks on only a bounded shortlist.

Related MCP servers

All in Version Control All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewGitworthy AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/gitworthy?style=directory)](https://allmcps.com/mcp/gitworthy)
HTML Embed
<a href="https://allmcps.com/mcp/gitworthy"><img src="https://allmcps.com/api/badge/gitworthy?style=directory" alt="Gitworthy on AllMCPs" /></a>