GitHub Actions trigger checker
OCI · GHCR.IO/LAWATCH/GHA-TRIGGER-CHECK · 2 COMPONENTS
Will this GitHub Actions workflow run for this push or PR? Which filter line decides, and why
Available components
Last scanned (23 hours ago)
Scores higher than 35% of OCI servers
Category CI/CD and DevOps
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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
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 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability56
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1487 tokens (~495/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (12)
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (4)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain Security (scores 0 for this)No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
- Known CVEs in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
- Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 37
First indexed and scored.
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 21 Nov 2026 · Analysed oci/ghcr.io/lawatch/gha-trigger-check@1.0.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
test_filter_patterns Test GitHub Actions branch / tag / path patterns ~184
Tests a list of GitHub Actions filter patterns (as written under branches, tags or paths, "!" exceptions included) against branch names, tags or file paths, and says for each one whether it is selected and which pattern decides (the last matching one). Also returns the exact regular expression of each pattern and the error GitHub gives for an invalid one ("[]", ranges outside a-z/A-Z/0-9, trailing "\", "?" or "+" after "**"). Use it to write or fix a filter before pushing.
| Name | Type | Req | Description |
|---|---|---|---|
| list | string | – | Which filter the patterns belong to (default "paths"). With -ignore lists, a name matched by the list is ignored. |
| names | array | yes | Branch names, tags or file paths to test. |
| patterns | array | yes | Patterns in order, e.g. ["src/**", "!src/**/*.md"]. |
No output schema declared.
No examples provided.
which_workflows_run Which workflows run for this push or pull request? ~524
Checks every workflow of a repository at once for one push or pull request and lists which ones run, which do not, and why (the deciding line of each). Give the workflows as { "<file name>": "<YAML>" }, or let the server read .github/workflows/ in "dir" (default: current directory). Same rules and inputs as will_workflow_run. Use it to predict the CI of a PR, or to find why a check never appears.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | pull_request(_target) activity type: opened (default), synchronize (new commits pushed), reopened, labeled, closed, ready_for_review, edited... |
| branch | string | – | push: the pushed branch (e.g. "main", "feature/login"; "refs/heads/..." accepted). pull_request / pull_request_target: the BASE branch the PR targets (branch filters compare with the base, not the PR… |
| changed_files | array | – | Files changed, relative to the repo root ("src/app.ts"). push: files changed by the pushed commits (e.g. `git diff --name-only <before>..<after>`); pull request: `git diff --name-only origin/<base>..… |
| commit_message | string | – | Head commit message, to detect [skip ci], [ci skip], [no ci], [skip actions], [actions skip] and the "skip-checks: true" trailer. |
| dir | string | – | Repository root to read .github/workflows/ from, when "workflows" is not given. Default: current directory. |
| event | string | – | push (default), pull_request or pull_request_target. Other events are only checked for presence under on:. |
| has_merge_conflict | boolean | – | pull_request: true if the PR currently has a merge conflict (pull_request workflows then do not run). |
| ref | string | – | Alternative to branch/tag: a full ref, "refs/heads/main" or "refs/tags/v1.0". |
| tag | string | – | push only: the pushed tag (e.g. "v1.2.0"). Give a branch or a tag, not both. |
| tags_pushed_count | integer | – | push of tags: how many tags were pushed at once (GitHub creates no event above 3). |
| workflows | object | – | The workflow files, as { ".github/workflows/ci.yml": "<content>" }. |
No output schema declared.
No examples provided.
will_workflow_run Will this GitHub Actions workflow run, and which line decides? ~649
Answers "why didn't my GitHub Actions workflow run?" or "will this push / PR trigger it?" exactly as GitHub filters events. Give the workflow YAML (or its path) and the push or pull request: branch or tag, changed files, activity type, commit message. Returns runs = true / false (null if a needed input is missing), the step-by-step reasoning, and the workflow line and pattern that decide. Covers: branches / branches-ignore / tags / tags-ignore / paths / paths-ignore with the exact glob rules ("*" stops at "/", "**", "?" and "+" repeat the previous character, [a-z], "!" exceptions where the last matching pattern wins), branch filters of pull_request compared with the BASE branch, tag pushes ignored when only branch filters exist (and the reverse), paths not evaluated for tags, paths-ignore needing ALL files ignored, default pull_request types (opened, synchronize, reopened), [skip ci] markers, more than 3 tags pushed at once, merge conflicts, more than 300 changed files, and invalid filters that make GitHub reject the whole file (branches with branches-ignore, bad patterns). Offline, read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | pull_request(_target) activity type: opened (default), synchronize (new commits pushed), reopened, labeled, closed, ready_for_review, edited... |
| branch | string | – | push: the pushed branch (e.g. "main", "feature/login"; "refs/heads/..." accepted). pull_request / pull_request_target: the BASE branch the PR targets (branch filters compare with the base, not the PR… |
| changed_files | array | – | Files changed, relative to the repo root ("src/app.ts"). push: files changed by the pushed commits (e.g. `git diff --name-only <before>..<after>`); pull request: `git diff --name-only origin/<base>..… |
| commit_message | string | – | Head commit message, to detect [skip ci], [ci skip], [no ci], [skip actions], [actions skip] and the "skip-checks: true" trailer. |
| event | string | – | push (default), pull_request or pull_request_target. Other events are only checked for presence under on:. |
| has_merge_conflict | boolean | – | pull_request: true if the PR currently has a merge conflict (pull_request workflows then do not run). |
| ref | string | – | Alternative to branch/tag: a full ref, "refs/heads/main" or "refs/tags/v1.0". |
| tag | string | – | push only: the pushed tag (e.g. "v1.2.0"). Give a branch or a tag, not both. |
| tags_pushed_count | integer | – | push of tags: how many tags were pushed at once (GitHub creates no event above 3). |
| workflow | string | – | Content of the workflow file (.github/workflows/*.yml). |
| workflow_path | string | – | Or a path to the workflow file, if the server can read the project. |
No output schema declared.
No examples provided.
How do I install the GitHub Actions trigger checker MCP server?
GitHub Actions trigger checker runs locally as a container image, launched with docker run --rm -i ghcr.io/lawatch/gha-trigger-check:1.0.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/lawatch/gha-trigger-check
claude mcp add lawatch-gha-trigger-check -- docker run --rm -i ghcr.io/lawatch/gha-trigger-check:1.0.0
What is the GitHub Actions trigger checker MCP server?
GitHub Actions trigger checker is an MCP server listed in the public MCP registry as io.github.Lawatch/gha-trigger-check. Will this GitHub Actions workflow run for this push or PR? Which filter line decides, and why. This page covers its container image (ghcr.io/lawatch/gha-trigger-check).
Is the GitHub Actions trigger checker MCP server safe to use?
GitHub Actions trigger checker scores 39 out of 100 on VerifyMCP. 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 GitHub Actions trigger checker MCP server expose?
GitHub Actions trigger checker exposes 3 tools: will_workflow_run, which_workflows_run, test_filter_patterns. Their descriptions and schemas cost roughly 1,357 tokens of context every time the server is loaded.
Is the GitHub Actions trigger checker MCP server still maintained?
GitHub Actions trigger checker is still listed as active in the MCP registry. We last reached this channel on 21 November 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 GitHub Actions trigger checker MCP server under?
GitHub Actions trigger checker declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the GitHub Actions trigger checker MCP server?
VerifyMCP ran 12 checks on GitHub Actions trigger checker, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about GitHub Actions trigger checker: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.