io.github.vola-trebla/flakiness-knowledge-graph-mcp
NPM · FLAKINESS-KNOWLEDGE-GRAPH-MCP · SCANNED SEP 20
MCP server + Playwright reporter that builds a flakiness knowledge graph from test run history
Available components
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. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 124 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 833 tokens (~104/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.vola-trebla/flakiness-knowledge-graph-mcp server?
io.github.vola-trebla/flakiness-knowledge-graph-mcp runs locally as an npm package, launched with npx -y flakiness-knowledge-graph-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · flakiness-knowledge-graph-mcp
claude mcp add vola-trebla-flakiness-knowledge-graph-mcp -- npx -y flakiness-knowledge-graph-mcp
{
"mcpServers": {
"vola-trebla-flakiness-knowledge-graph-mcp": {
"command": "npx",
"args": [
"-y",
"flakiness-knowledge-graph-mcp"
]
}
}
} {
"servers": {
"vola-trebla-flakiness-knowledge-graph-mcp": {
"command": "npx",
"args": [
"-y",
"flakiness-knowledge-graph-mcp"
]
}
}
} codex mcp add vola-trebla-flakiness-knowledge-graph-mcp -- npx -y flakiness-knowledge-graph-mcp
{
"$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 mcp add vola-trebla-flakiness-knowledge-graph-mcp --command npx --arg -y --arg flakiness-knowledge-graph-mcp
mcp_servers:
vola-trebla-flakiness-knowledge-graph-mcp:
command: "npx"
args: ["-y", "flakiness-knowledge-graph-mcp"] {
"McpServers": {
"vola-trebla-flakiness-knowledge-graph-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"flakiness-knowledge-graph-mcp"
]
}
}
} assistant mcp add vola-trebla-flakiness-knowledge-graph-mcp -t stdio -c npx -a -y flakiness-knowledge-graph-mcp
{
"mcpServers": {
"vola-trebla-flakiness-knowledge-graph-mcp": {
"command": "npx",
"args": [
"-y",
"flakiness-knowledge-graph-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.80 functional
- 8 Sept 26 +1
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/flakiness-knowledge-graph-mcp@0.2.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
cluster_semantic_error_trees ~157
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.
| Name | Type | Req | Description |
|---|---|---|---|
| db_path | string | yes | 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 |
No output schema declared.
No examples provided.
correlate_git_commit_flakiness ~153
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?
| Name | Type | Req | Description |
|---|---|---|---|
| db_path | string | yes | 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 |
No output schema declared.
No examples provided.
get_error_groups ~106
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?
| Name | Type | Req | Description |
|---|---|---|---|
| db_path | string | yes | 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 |
No output schema declared.
No examples provided.
get_failure_patterns ~70
Breaks down failure rates by browser and OS combination. Use to answer: does this test only fail on Firefox? Only on Windows?
| Name | Type | Req | Description |
|---|---|---|---|
| db_path | string | yes | Absolute path to the flakiness.db SQLite file |
| since_days | integer | – | Only include runs from the last N days |
No output schema declared.
No examples provided.
get_flakiness_trend ~92
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?
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Number of days to look back |
| db_path | string | yes | Absolute path to the flakiness.db SQLite file |
| test_id | string | yes | Test ID from get_flaky_tests |
No output schema declared.
No examples provided.
get_flaky_tests ~105
Returns tests ranked by flakiness rate (failed+flaky / total runs). Use to answer: which tests are the most unreliable?
| Name | Type | Req | Description |
|---|---|---|---|
| db_path | string | yes | 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 |
No output schema declared.
No examples provided.
get_slow_tests ~59
Returns tests ranked by average duration. Use to answer: which tests are slowing down the CI pipeline?
| Name | Type | Req | Description |
|---|---|---|---|
| db_path | string | yes | Absolute path to the flakiness.db SQLite file |
| limit | integer | – | Max tests to return |
No output schema declared.
No examples provided.
get_test_history ~91
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?
| Name | Type | Req | Description |
|---|---|---|---|
| db_path | string | yes | Absolute path to the flakiness.db SQLite file |
| limit | integer | – | Max runs to return |
| test_id | string | yes | Test ID from get_flaky_tests |
No output schema declared.
No examples provided.
What is the io.github.vola-trebla/flakiness-knowledge-graph-mcp server?
io.github.vola-trebla/flakiness-knowledge-graph-mcp is listed in the public MCP registry as io.github.vola-trebla/flakiness-knowledge-graph-mcp. MCP server + Playwright reporter that builds a flakiness knowledge graph from test run history. This page covers its npm package (flakiness-knowledge-graph-mcp).
Is the io.github.vola-trebla/flakiness-knowledge-graph-mcp server safe to use?
io.github.vola-trebla/flakiness-knowledge-graph-mcp scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.vola-trebla/flakiness-knowledge-graph-mcp server expose?
io.github.vola-trebla/flakiness-knowledge-graph-mcp exposes 8 tools: get_flaky_tests, get_test_history, get_failure_patterns, get_slow_tests, get_error_groups, and 3 more. Their descriptions and schemas cost roughly 833 tokens of context every time the server is loaded.
Is the io.github.vola-trebla/flakiness-knowledge-graph-mcp server still maintained?
io.github.vola-trebla/flakiness-knowledge-graph-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.vola-trebla/flakiness-knowledge-graph-mcp server under?
io.github.vola-trebla/flakiness-knowledge-graph-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.