What it does
It takes the cache key template as written in a workflow, with the glob patterns from its hashFiles() segments, and the outcome of each run: hit, partial or miss. It reports outcome counts and the hit rate, then gives each non-hit run a cause. A partial run is labelled as an exact key miss with a restore hit. A miss whose changed files match a hashed input is labelled as a changed hashed input, with the matching files listed. Any other miss is labelled unexplained. It also tallies causes, names the most common one, lists the hashed files that changed on misses, and gives an overall diagnosis, which is cache_healthy when every run hit.
It suits CI runs that did not use the cache as expected, for example to check whether a changed lockfile or manifest keeps invalidating the cache, or whether some misses cannot be explained from the recorded inputs. Glob matching supports a leading **/ and single-segment * wildcards, and matching is case-sensitive.
It runs as a CLI that reads an args.json file and prints a JSON report, or as an MCP server exposing an analyze_cache_miss tool that takes key_template, runs and optional restore_keys. All computation is local, with no network access, log scraping or configuration. Exit codes are 0 for success, 1 for runtime errors and 2 for usage errors.
Limitations and requirements
Invalid input is rejected with an error naming the offending path, and no partial report is produced. This covers an empty key template, a run without an outcome, an outcome other than hit, partial or miss, and a changed file that is not a string. changed_files is optional per run, and restore_keys is optional overall. Glob matching is case-sensitive.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
io.github.CloudCorpRecords/cachemiss
CI cache-miss analysis: which hashed key inputs changed and why runs missed or fell back.
v0.1.0As shown on registry.modelcontextprotocol.io when we last read it