Back to Browse

Flaky History MCP Server

Developer ToolsModerate7.2MCP RegistryLocal
Free

Server data from the Official MCP Registry

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

About

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

Security Report

7.2
Moderate7.2Low Risk

Flaky History is a well-designed local test-history analysis tool with strong security controls. Path traversal is effectively mitigated through realpath checks and bounded directory walking. Input validation uses regex allow-lists for file types, and output is privacy-preserving by design—never emitting test names, file paths, or raw values. Minor quality issues around exception handling and regex complexity do not materially affect security. Supply chain analysis found 1 known vulnerability in dependencies (0 critical, 1 high severity). Package verification found 1 issue.

6 files analyzed · 5 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

File System Read

Reads files on your machine. Normal for tools that analyze or process local data.

env_vars

Check that this permission is expected for this type of plugin.

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-mrfentmen-flaky-history-mcp": {
      "args": [
        "-y",
        "flaky-history-mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

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

npm install
npm run build
node dist/index.js

Reviews

No reviews yet

Be the first to review this server!