# io.github.vola-trebla/flakiness-knowledge-graph-mcp (npm · flakiness-knowledge-graph-mcp)

MCP server + Playwright reporter that builds a flakiness knowledge graph from test run history

- Trust score: 69/100 (medium)
- Change this week: +23
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `flakiness-knowledge-graph-mcp`: 69/100 (this document), [markdown](https://verifymcp.io/servers/vola-trebla-flakiness-knowledge-graph-mcp/flakiness-knowledge-graph-mcp.md), [page](https://verifymcp.io/servers/vola-trebla-flakiness-knowledge-graph-mcp/flakiness-knowledge-graph-mcp)

## Channel facts

- Registry: `npm`
- Package: `flakiness-knowledge-graph-mcp`
- Version: `0.2.2`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 76 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 833 tokens (~104/item across 8 items; 8 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add vola-trebla-flakiness-knowledge-graph-mcp -- npx -y flakiness-knowledge-graph-mcp
```

### Codex

```bash
codex mcp add vola-trebla-flakiness-knowledge-graph-mcp -- npx -y flakiness-knowledge-graph-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "vola-trebla-flakiness-knowledge-graph-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "flakiness-knowledge-graph-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add vola-trebla-flakiness-knowledge-graph-mcp --command npx --arg -y --arg flakiness-knowledge-graph-mcp
```

### Hermes

```yaml
mcp_servers:
  vola-trebla-flakiness-knowledge-graph-mcp:
    command: "npx"
    args: ["-y", "flakiness-knowledge-graph-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "vola-trebla-flakiness-knowledge-graph-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "flakiness-knowledge-graph-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 69, +48)

- [security regression] Provenance: unverified → fail
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Install scripts: unverified → pass
- [security improvement] Malware scan: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] License: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Stability: unverified → 0.20
- [functional improvement] Maintenance: unverified → pass
- [functional] Licence: MIT

### 2026-08-01 (score 21, −7)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-31 (score 28, −18)

- [security regression] Malware scan: pass → unverified

### 2026-07-27 (score 46)

First indexed and scored.

## MCP tools (8)

### `get_flaky_tests` (~105 tokens)

Returns tests ranked by flakiness rate (failed+flaky / total runs). Use to answer: which tests are the most unreliable?

Input parameters:

- `db_path` (string, required): Absolute path to the flakiness.db SQLite file
- `limit` (integer): Max tests to return
- `min_runs` (integer): Minimum number of runs to consider a test (filters out one-off failures)
- `since_days` (integer): Only include runs from the last N days

### `get_test_history` (~91 tokens)

Returns the run history for a specific test — status, duration, error, retry count, browser, and OS for each run. Use to answer: is this test getting worse over time?

Input parameters:

- `db_path` (string, required): Absolute path to the flakiness.db SQLite file
- `limit` (integer): Max runs to return
- `test_id` (string, required): Test ID from get_flaky_tests

### `get_failure_patterns` (~70 tokens)

Breaks down failure rates by browser and OS combination. Use to answer: does this test only fail on Firefox? Only on Windows?

Input parameters:

- `db_path` (string, required): Absolute path to the flakiness.db SQLite file
- `since_days` (integer): Only include runs from the last N days

### `get_slow_tests` (~59 tokens)

Returns tests ranked by average duration. Use to answer: which tests are slowing down the CI pipeline?

Input parameters:

- `db_path` (string, required): Absolute path to the flakiness.db SQLite file
- `limit` (integer): Max tests to return

### `get_error_groups` (~106 tokens)

Groups failing tests by similar error messages to surface systemic failures. Use to answer: are 10 tests failing because of the same broken endpoint or shared root cause?

Input parameters:

- `db_path` (string, required): Absolute path to the flakiness.db SQLite file
- `limit` (integer): Max error groups to return
- `min_failures` (integer): Minimum number of failures sharing the same error to include
- `since_days` (integer): Only include failures from the last N days

### `get_flakiness_trend` (~92 tokens)

Returns the daily flakiness rate for a specific test over the last N days. Use to answer: is this test getting worse, better, or staying the same?

Input parameters:

- `days` (integer): Number of days to look back
- `db_path` (string, required): Absolute path to the flakiness.db SQLite file
- `test_id` (string, required): Test ID from get_flaky_tests

### `cluster_semantic_error_trees` (~157 tokens)

Groups test failures by semantic error similarity rather than raw string prefix. Strips dynamic values (UUIDs, numeric IDs, hashes, timestamps, URLs) via regex, then applies Levenshtein fuzzy matching to merge errors that differ only in minor dynamic fragments. Classifies each cluster by taxonomy (TimeoutError, AssertionError, NetworkError, ReferenceError). Use instead of get_error_groups when failure messages contain dynamic IDs or selector attributes that make identical root causes look different.

Input parameters:

- `db_path` (string, required): Absolute path to the flakiness.db SQLite file
- `min_instances` (integer): Minimum number of failure instances to include a cluster
- `since_days` (integer): Only include failures from the last N days

### `correlate_git_commit_flakiness` (~153 tokens)

Finds the exact point where a test transitioned from stable to flaky (or back), and returns the git commit SHA, branch, and author at that transition. Requires the Playwright reporter to be running in a CI environment where GITHUB_SHA / CI_COMMIT_SHA / CIRCLE_SHA1 env vars are set. Use to answer: which commit broke this test, and who authored it?

Input parameters:

- `db_path` (string, required): Absolute path to the flakiness.db SQLite file
- `min_stable_runs` (integer): Consecutive passes required to consider a test 'stable' before a transition (default 3)
- `since_days` (integer): Only look at runs from the last N days

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/vola-trebla-flakiness-knowledge-graph-mcp/flakiness-knowledge-graph-mcp#diagnostics

## Score history

- 2026-08-03: 69
- 2026-08-02: 69
- 2026-08-01: 21
- 2026-07-31: 28
- 2026-07-30: 46
- 2026-07-28: 46
- 2026-07-27: 46

## Links

- npm package: https://www.npmjs.com/package/flakiness-knowledge-graph-mcp
- Socket report: https://socket.dev/npm/package/flakiness-knowledge-graph-mcp
- Repository: https://github.com/vola-trebla/flakiness-knowledge-graph-mcp
- Changelog RSS feed: https://verifymcp.io/servers/vola-trebla-flakiness-knowledge-graph-mcp/flakiness-knowledge-graph-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/vola-trebla-flakiness-knowledge-graph-mcp/flakiness-knowledge-graph-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/vola-trebla-flakiness-knowledge-graph-mcp/flakiness-knowledge-graph-mcp