MCP servers · cloudcorprecords

claimcheck: tracking stale claims and unshipped fixes in open-source work

A command-line tool, listed as an MCP resource, that finds issues with stale volunteer claims and finished fixes left on fork branches without a pull request.

This text was machine-translated from the publisher's own information and has not been checked by a human editor. The publisher's original text is the reference.

This resource was imported automatically from the sources listed below and has not been reviewed by the AI Gate team yet. The description is the publisher's own, as published. Check the repository before installing.

What it does

claimcheck scans a GitHub repository for two problems in open-source work. The first is stale claims: open, unassigned issues where someone commented that they would take the work and then stopped responding. The tool detects claim comments, checks whether a linked pull request ever appeared, and ranks the results with the oldest claims first. The second is parked fixes: finished commits on fork branches that never became a pull request. Bot comments, maintainer comments and comments from the issue author are excluded from claim detection.

Maintainers and contributors would reach for it to see whether people who said they would take an issue actually delivered, or to find completed work that never reached the main repository. It is described as the follow-up to greenlight, which asks whether an issue is ready to land, while claimcheck asks whether everyone who said yes followed through and whether their work shipped. It is one of four related tools alongside gatefile, greenlight and prwatch.

It runs from the command line. The --days flag changes the stale threshold and --json prints machine-readable output. Responses are cached in a local directory that can be overridden with environment variables. Setting a GitHub token raises the API rate limit.

Limitations and requirements

Requires Node 20 or later. Without a GITHUB_TOKEN or GH_TOKEN, GitHub API requests are limited to 60 per hour; with one, the limit is 5,000 per hour. Claim detection excludes bots, maintainers and the issue author.

Safety

Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.

  • Runs code or changes an assistant's behaviour

Sources

  • Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
    io.github.CloudCorpRecords/claimcheck

    Track stale claims and parked fixes so open-source work does not silently die.

    v0.1.4
    As shown on registry.modelcontextprotocol.io when we last read it
MCP servers
cloudflare

Cloudflare MCP servers

Cloudflare's hosted MCP servers for its products: documentation search, sandbox containers, browser rendering, Radar internet data, logs and analytics, Workers and more.

4.5K GitHub starsCloud & DevOpsSoftware development
Updated 18 Nov 2026
MCP servers
neondatabase

Neon MCP Server (Postgres)

Neon's MCP server for managing Neon Postgres in plain language: create projects and branches, run queries and prepare schema migrations from your editor.

663 GitHub starsData & databasesSoftware development
Updated 18 Nov 2026
MCP servers
microsoft

Playwright MCP (browser automation)

Microsoft's MCP server that lets an AI assistant open web pages, click, type and read them through a real browser, using the page structure instead of screenshots.

39.6K GitHub starsTesting & QAWeb, search & browser
Updated 18 Nov 2026
MCP servers
supabase-community

Supabase MCP Server

Supabase's MCP server that connects an AI assistant to your Supabase project to design tables, run queries, read configuration and look up documentation.

Data & databasesSoftware development
Updated 18 Nov 2026
claimcheck: tracking stale claims and unshipped fixes in open-source work | AI Gate Discover