CI pipeline monitoring for GitLab and GitHub - no API key.
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
project_pipelinesList the most recent GitLab CI pipelines for a project, newest first, with status, branch, trigger, age and duration. No API key needed.List the most recent GitLab CI pipelines for a project, newest first, with status, branch, trigger, age and duration. No API key needed.
No input schema was published for this tool.
pipeline_detailFetch one CI pipeline by id: status, branch, commit, trigger source, timings and URL.Fetch one CI pipeline by id: status, branch, commit, trigger source, timings and URL.
No input schema was published for this tool.
pipeline_jobsShow every job in a pipeline grouped by stage, with status, duration and the failure reason, plus the first job you should look at when a build is red.Show every job in a pipeline grouped by stage, with status, duration and the failure reason, plus the first job you should look at when a build is red.
No input schema was published for this tool.
ci_statsMeasure a project's pipeline health over its recent runs: success rate, average duration, the flakiest branches and a plain verdict.Measure a project's pipeline health over its recent runs: success rate, average duration, the flakiest branches and a plain verdict.
No input schema was published for this tool.
latest_ci_statusCheck the newest pipeline of up to 10 projects at once and report a compact green or red build board with age and duration.Check the newest pipeline of up to 10 projects at once and report a compact green or red build board with age and duration.
No input schema was published for this tool.
github_workflow_runsList recent GitHub Actions workflow runs for a public repository with conclusion, branch, trigger event and attempt number.List recent GitHub Actions workflow runs for a public repository with conclusion, branch, trigger event and attempt number.
No input schema was published for this tool.
github_jobsShow the jobs of a GitHub Actions run and name the exact step that failed, so you can go straight to the cause.Show the jobs of a GitHub Actions run and name the exact step that failed, so you can go straight to the cause.
No input schema was published for this tool.
project_releasesList a GitLab project's published releases newest first, with tag, release date, author, commit, the headline of the changelog and how many source archives and binary links ship with it.List a GitLab project's published releases newest first, with tag, release date, author, commit, the headline of the changelog and how many source archives and binary links ship with it.
No input schema was published for this tool.
repo_languagesShow which languages a public GitHub repository is written in, with the size and share of each, so you can see the stack a project is built on before reading any of its code.Show which languages a public GitHub repository is written in, with the size and share of each, so you can see the stack a project is built on before reading any of its code.
No input schema was published for this tool.
9 of 9 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
CI pipeline monitoring for GitLab and GitHub - no API key.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
The crawl stopped at the depth-4 limit. Anything below that level was never resolved.
The crawl stopped at the 60-package limit. The rest of the tree was never resolved.
36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)
54 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.
+42 more not listed. The counts by reason above cover all of them.
Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.