Flaky History MCP server

by mrfentmen·io.github.mrfentmen/flaky-history-mcp·v1.0.0

No reviews yet

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

A85/100grade A

Write a review Install

What users say

No reviews yet

Be the first

Safety scan

A85/100

full report

Adoption

New

0 stars

Reviews

Write one

Nobody has reviewed Flaky History yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Flaky History tools (1)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

analyze_test_history
Aggregate local test history into stability signals without returning test names, file names, raw records, or exact versions.

Public scan report

scanner v0.1.10 · 2026-11-01 · same rubric, same numbers if you re-run it

no findings

Code scan8 source files scanned25/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancelast push 85 days ago12/15
Maintainer identityregistry namespace matches repository owner6/10

Overall 85/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

How Flaky History compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 85/100; higher than 70% of 48,255 servers
Tools: 1; the typical server has 7
Tools that change things: 0%; typical: 0%. Fewer write tools means less an agent can break

What its tools let an agent do: 1 read

Install Flaky History in Claude Code, Cursor or VS Code

Runs npx -y flaky-history-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add flaky-history-mcp -- npx -y flaky-history-mcp

Add to Cursor

What the publisher says

From the Flaky History repository's README, as published. We do not edit it. Read it on GitHub

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

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

Safety

Local paths only, bounded by FLAKYHISTORYROOT 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

Nothing above is checked by us. What we check is on the safety report.

Flaky History: common questions

Is Flaky History MCP server safe?: Yes, by our scan: it is graded A (85/100). Read the Flaky History safety report
How do I install Flaky History?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Flaky History need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Flaky History maintained?: The last commit was 87 days ago (2026-08-09). The latest release is v1.0.0.
How does Flaky History compare with other MCP servers?: safety score 85/100 (higher than 70% of 48,255 servers); tools 1 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.