MCP servers · cloudcorprecords

cidiff: sorts PR CI failures into introduced, pre-existing and external

A CLI and MCP server that compares CI checks on a pull request's head and base commits and classifies each one.

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

It compares check runs and commit statuses on a pull request's head commit with those on its base commit, and labels each check as introduced, pre-existing, external, fixed, passing, indeterminate or pending. Hosted deploy checks, such as Vercel, Netlify and Cloudflare, and checks waiting for maintainer approval are classed as external before any base comparison. A failure with no base evidence is marked indeterminate, and a check whose completed runs disagree on the same commit is flagged as flaky.

It suits cases where a pull request shows many failing checks and the author needs to see which failures the change caused. The CLI exits with code 1 when introduced failures exist and 0 otherwise, so it can serve as a CI gate or a triage script. The MCP server offers diff_pr_ci, which takes a repository and PR number, and diff_ci_runs, which takes a repository and head and base SHAs.

Running it needs no credentials for public repositories. The GITHUB_TOKEN environment variable is optional and raises the GitHub API rate limit. If the head commit has no check runs, for example because workflow approval is pending, the tool warns that CI has not run and does not classify those failures.

Limitations and requirements

Checks are matched by exact name, so a renamed check appears as a removal plus an addition. The base comparison uses the check evidence recorded for the PR's base commit, taken from the PR object. Failures with no usable base evidence remain unclassified (indeterminate). If CI has not run on the head commit, failures cannot be classified. Setting GITHUB_TOKEN is optional and only raises the API rate limit; no other credentials are needed for public repositories.

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/cidiff

    Base-vs-head CI differ: which PR failures are introduced, pre-existing, external, or fixed.

    v0.1.2
    As shown on registry.modelcontextprotocol.io when we last read it
MCP servers
docker

Docker Hub MCP Server

Docker's MCP server that helps an AI assistant find and compare container images on Docker Hub and, with your token, manage your own repositories and tags.

171 GitHub starsCloud & DevOpsSoftware development
Updated 13 Nov 2026
MCP servers
awslabs

MCP servers for AWS (AWS Labs)

A large open-source collection of MCP servers from AWS Labs for building and operating on AWS: documentation, infrastructure, databases, AI services, cost and more.

9.9K GitHub starsCloud & DevOpsData & databases
Updated 17 Nov 2026
MCP servers
firecrawl

Firecrawl MCP Server (web search and scraping)

Firecrawl's MCP server that lets an AI assistant search the web, turn pages and PDFs into clean Markdown, crawl sites and interact with dynamic pages.

7.8K GitHub starsWeb, search & browserProductivity & automation
Updated 17 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 17 Nov 2026