GitHub Actions trigger checker
MCP server io.github.Lawatch/gha-trigger-check
Sourced
Will this GitHub Actions workflow run for this push or PR? Which filter line decides, and why
The name and description are the publisher's own words, as the registry holds them.
- For
- GitHub
- Version
- 1.0.0
- Registry record changed
- Listed here since
Who publishes it
Sourced. By another publisher, naming a public repository or a package. Anyone can publish one; we have not read its code.
Repository: https://github.com/Lawatch/10aday
How to reach it
- Container image:
ghcr.io/lawatch/gha-trigger-check:1.0.0, runs over stdio - MCP bundle:
https://github.com/Lawatch/10aday/releases/download/gha-trigger-check-v1.0.0/gha-trigger-check-1.0.0.mcpb, runs over stdio
What is known about it
- Downloads
- Not read. Counts come from npm and PyPI; this server lists no package there, or its count has not been read yet.
- Vulnerabilities
- Not checked. OSV is asked about npm and PyPI packages that name a version; this server lists none, or its record changed after the last read.
- Tools
- Not read. A server is asked for its tools at a Streamable HTTP address with nothing to fill in, whose record declares no header. One that is only a package is run, where it can reach nothing, when its record names one version of an npm or PyPI package and no arguments; this one is not that, or has not been run yet.
Changes recorded here
None in the last 30 days. The log began on , and nothing older was recorded.
A change is a difference between two readings of public records, not a review. The whole log · How the log is made
Built from agent catalog version 2026-11-18.1 of , from the MCP Registry as read on . A listing here is not an endorsement: anyone can publish a server, and we have not read its code. Names, descriptions and addresses are the publisher's own. See how this directory is made, and tell us about a wrong entry through the contact page.