Gitlab Ci Break Lint MCP server

by jmshinhwa·io.github.jmshinhwa/gitlab-ci-break-lint·v1.0.1

Names the .gitlab-ci.yml lines your runner will reject after the next GitLab major upgrade

A89/100grade A

What users say

No reviews yet

Safety scan

A89/100

Adoption

Growing

0 stars73 downloads/wk

Reviews

Nobody has reviewed Gitlab Ci Break Lint yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

No tool declarations could be read from the package source. They show once the server is installed.

scanner v0.1.9 · 2026-09-23 · same rubric, same numbers if you re-run it

no findings

Code scan6 source files scanned25/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancelast push 0 days ago15/15
Maintainer identityregistry namespace matches repository owner6/10

Overall 89/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 89/100; higher than 80% of 1,119 Developer tools servers
Downloads a week: 73; more than 51% of 430 Developer tools servers with a package

Runs npx -y @readystack/gitlab-ci-break-lint on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add gitlab-ci-break-lint -- npx -y @readystack/gitlab-ci-break-lint

From the Gitlab Ci Break Lint repository's README, as published. We do not edit it. Read it on GitHub

VS Code themes by ReadyStack

Nothing above is checked by us. What we check is on the safety report.

Is Gitlab Ci Break Lint MCP server safe?: Yes, by our scan: it is graded A (89/100). Read the Gitlab Ci Break Lint safety report
How do I install Gitlab Ci Break Lint?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Gitlab Ci Break Lint need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Gitlab Ci Break Lint maintained?: The last commit was 40 days ago (2026-09-23). The latest release is v1.0.1.
What can I use instead of Gitlab Ci Break Lint?: Servers from other publishers that do the same job: GitLab MCP Server, Gk CLI MCP server and Advanced GitLab MCP server.
How does Gitlab Ci Break Lint compare with other Developer tools MCP servers?: safety score 89/100 (higher than 80% of 1,119 Developer tools servers); downloads a week 73 (more than 51% of 430 Developer tools servers with a package). Full comparison.

Same job from other publishers: the closest match first, then the best rated.

GitLab MCP Server
GitLab MCP server for projects, merge requests, issues, pipelines, wiki, releases, and more.
not reviewed
Widely used
B
Gk CLI
The GitKraken MCP Server for managing repos, PRs, issues across GitHub, GitLab, Bitbucket and more.
not reviewed
Established
B
Advanced GitLab MCP server
64 CQRS tools exposing 236 GitLab operations across 26 entity types
not reviewed
Growing
A
Gitlab
GitLab MCP server (MCP 2026-07-28): projects, MRs, pipelines, CI/CD, issues; writes or read-only
not reviewed
Growing
B
Grasp — Code Architecture & Dependency Analysis
Codebase analysis: dependency graphs, security scanning, and refactor plans for GitHub and GitLab.
not reviewed
Growing
C