# GitHub Actions trigger checker (mcpb · gha-trigger-check-1.0.0.mcpb)

Will this GitHub Actions workflow run for this push or PR? Which filter line decides, and why

- Trust score: 37/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- mcpb · `gha-trigger-check-1.0.0.mcpb`: 37/100 (this document), [markdown](https://verifymcp.io/servers/lawatch-gha-trigger-check/gha-trigger-check.md), [page](https://verifymcp.io/servers/lawatch-gha-trigger-check/gha-trigger-check)
- oci · `ghcr.io/lawatch/gha-trigger-check`: 39/100, [markdown](https://verifymcp.io/servers/lawatch-gha-trigger-check/ghcr-io-lawatch-gha-trigger-check.md), [page](https://verifymcp.io/servers/lawatch-gha-trigger-check/ghcr-io-lawatch-gha-trigger-check)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/Lawatch/10aday/releases/download/gha-trigger-check-v1.0.0/gha-trigger-check-1.0.0.mcpb`
- Transport: `stdio`
- SHA-256: `ce2a0703f928e601ffe1aaae84f6c9d01db7b63c6cc1639bbc01fe9d3c77ace2`

## 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-11-21.

- **Supply Chain Security**: 0/100
  - 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 could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- **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 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 56/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 2 categories.** Categories scored 0 because we could not verify them: 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.

## Install

### How do I install the GitHub Actions trigger checker MCP server?

GitHub Actions trigger checker ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, ce2a0703f928e601ffe1aaae84f6c9d01db7b63c6cc1639bbc01fe9d3c77ace2; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/Lawatch/10aday/releases/download/gha-trigger-check-v1.0.0/gha-trigger-check-1.0.0.mcpb`
- SHA-256: `ce2a0703f928e601ffe1aaae84f6c9d01db7b63c6cc1639bbc01fe9d3c77ace2`

### Verify on macOS / Linux

```bash
echo "ce2a0703f928e601ffe1aaae84f6c9d01db7b63c6cc1639bbc01fe9d3c77ace2  gha-trigger-check-1.0.0.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\gha-trigger-check-1.0.0.mcpb).Hash -eq "ce2a0703f928e601ffe1aaae84f6c9d01db7b63c6cc1639bbc01fe9d3c77ace2"
```

## 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-11-19 (score 37, +1)

- [functional improvement] Maintenance: unverified → pass

### 2026-11-17 (score 36)

First indexed and scored.

## MCP tools (3)

### `will_workflow_run` (~649 tokens)

Will this GitHub Actions workflow run, and which line decides?

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.

Input parameters:

- `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.

### `which_workflows_run` (~524 tokens)

Which workflows run for this push or pull request?

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.

Input parameters:

- `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>" }.

### `test_filter_patterns` (~184 tokens)

Test GitHub Actions branch / tag / path patterns

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.

Input parameters:

- `list` (string): Which filter the patterns belong to (default "paths"). With -ignore lists, a name matched by the list is ignored.
- `names` (array, required): Branch names, tags or file paths to test.
- `patterns` (array, required): Patterns in order, e.g. ["src/**", "!src/**/*.md"].

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/lawatch-gha-trigger-check/gha-trigger-check#diagnostics

## Score history

- 2026-11-21: 37
- 2026-11-20: 37
- 2026-11-19: 37
- 2026-11-18: 36
- 2026-11-17: 36

## Common questions

### 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 MCPB bundle (https://github.com/Lawatch/10aday/releases/download/gha-trigger-check-v1.0.0/gha-trigger-check-1.0.0.mcpb).

### Is the GitHub Actions trigger checker MCP server safe to use?

GitHub Actions trigger checker scores 37 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.

### 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 11 checks on GitHub Actions trigger checker, covering Source repository, Provenance, License, Maintenance and 7 more. 5 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, Dependency health and 1 more. 2 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Repository: https://github.com/Lawatch/10aday
- Changelog RSS feed: https://verifymcp.io/servers/lawatch-gha-trigger-check/gha-trigger-check.xml
- Changelog JSON feed: https://verifymcp.io/servers/lawatch-gha-trigger-check/gha-trigger-check/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/lawatch-gha-trigger-check/gha-trigger-check.json
- HTML version of this page: https://verifymcp.io/servers/lawatch-gha-trigger-check/gha-trigger-check
