MCP servers · cloudcorprecords

flakyguard: per-test flakiness evidence from CI runs

MCP server and CLI that build per-test pass/fail history from CI runs, classify tests as stable or flaky, and list flaky tests for quarantine.

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

flakyguard takes per-test outcomes from a set of CI runs and builds a record for each test: how many runs included it and how many times it passed, failed or was skipped. Skipped results are recorded but never count as evidence. By default a test needs two evidence runs before it receives a verdict of stable pass, stable fail or flaky; until then it is marked insufficient data. Its flakiness rate is the share of the minority outcome among evidence runs, rounded to four decimal places.

It suits teams that want evidence about a suspect test rather than impressions, and that need to decide which flaky tests to quarantine. Flaky tests whose rate meets the quarantine threshold (0.5 by default) appear in a list ordered worst first, with the pass and fail counts behind each rate. The overall verdict is quarantine_recommended when that list is non-empty, and clean otherwise.

Analysis runs locally on the runs you supply, with no network access, no configuration and no history kept between calls. It is available as a CLI that reads an args.json file and prints JSON, and as an MCP server exposing an analyze_test_flakiness tool that takes runs, min_runs and quarantine_threshold.

Limitations and requirements

Each run must contain results, every status must be passed, failed or skipped, and a test may appear only once per run. Invalid input, including an unreadable or invalid input file, is rejected with an error naming the offending path, and no partial analysis is produced.

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

    Flaky-test evidence tracker: per-test pass/fail history, flakiness rates, and a quarantine list.

    v0.1.0
    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
flakyguard: per-test flakiness evidence from CI runs | AI Gate Discover