Odel
MCP server: One MCP server.

Flaky History

@mrfentmenMCP server · External

Local aggregate test-history stability analysis without test names or raw result contents. Tools...

Software testingv1.0.0TypeScript
Freeno charge per call
How to install

Runs on your machine from its package; the steps are below.

What it does

  1. Reads
  2. Writes
  3. High impact

At most: only reads or looks up information.

What it costs

Free

Odel charges nothing per call. The publisher may charge for its own service.

Runs locally over stdio

This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).

npmflaky-history-mcpv1.0.0

Run

npx -y flaky-history-mcp

MCP client config

{
  "mcpServers": {
    "flaky-history": {
      "command": "npx",
      "args": [
        "-y",
        "flaky-history-mcp"
      ]
    }
  }
}
README1 min read

flaky-history-mcp

Flaky History is a local MCP tool for turning small test-history exports into coarse stability signals. It accepts bounded JSON, JSONL, CSV, and simple JUnit-like XML files, then reports aggregate pass, fail, skip, and unknown counts.

Tool

  • analyze_test_history: aggregate local history without returning test names, file names, raw records, exact versions, or values.

Safety

  • Local paths only, bounded by FLAKY_HISTORY_ROOT and realpath checks.
  • Reads only bounded test and result-looking JSON, JSONL, CSV, and XML files.
  • Skips dependencies, build output, Git data, caches, and vendor directories.
  • This is a stability signal, not a CI runner, test retry engine, or statistical proof of flakiness.

Run

bash
npm install
npm run build
node dist/index.js

Similar modules

Browse Software testing