updated 2026-11-11 00:08 UTC

Gitlab MCP

Repository Website

MCP server for GitLab: 277 tools for projects, MRs, issues, pipelines, wikis and more via the GitLab REST/GraphQL API

MCP Servers TypeScript Listed MIT

Is Gitlab MCP safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 8.3 / 10
Provenance Attested
Signed commits 41%
Last push yesterday
Advisories None known
Compare Gitlab MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Gitlab MCP scores 90.9/100 (Grade A), ranked #18 of 1387 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 8.3/10; 41% of recent commits are signed; no published advisory affects its latest release (@zereight/mcp-gitlab); last pushed 2026-11-10. Every point is earned from checkable signals — never paid placement. How scoring works →

How Gitlab MCP could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Gitlab MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/zereight/gitlab-mcp, MIT, last pushed 2026-11-10. 41% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Strong

    OpenSSF Scorecard rates the repository's practices 8.3/10 (scanned Nov 10, 2026). The checks that decide who can get a change released:

    • Code Review10
    • Branch Protectionn/a
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions10
    • Pinned Dependencies9
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection -1
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 10
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 9
    SAST 7
    Security-Policy 10
    Signed-Releases 0
    Token-Permissions 10
    Vulnerabilities 10

  3. Published packages Linked and attested

  4. What you install today No known advisories

    Latest release checked: @zereight/mcp-gitlab 2.3.22. No published advisory affects it (OSV, checked 2026-11-10).

Changes to this chain

  • 2026-09-23 Package provenance attestation detected
  • 2026-09-03 OSSF Scorecard: 5.8/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Gitlab MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Gitlab MCP compares in MCP Servers

  1. #2 Playwright MCP 92.7 +1.8
  2. #3 Mobile MCP 91.9 +1.0
  3. #4 Gitlab MCP 90.9 this agent
  4. #5 Windows MCP 90.8 −0.1
  5. #6 Supabase MCP Server 90.8 −0.1

Bars show each HVTrust score; the tick marks Gitlab MCP’s 90.9.

Where the 90.9 comes from

HVTrust dimensions vs the MCP Servers average

90.9 / 100 · 100.0% confidence

Gitlab MCP MCP Servers average (779 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
19.9 / 25
9.1 above avg 10.8
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.3 above avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
15.6 / 17
3.3 above avg 12.3
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
7.6 above avg 12.3
AdoptionLog-scaled stars · package downloads
15.0 / 20
7.4 above avg 7.6

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-11-10
Rank Moved
Rank rose 43 spots (#61 → #18)
Maintainer Checklist
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with Codebase Memory MCP
View MCP Servers Report missing data
81.8
Activity sub-score · out of 100
#4
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-11-11 00:08 UTC · Repo last pushed yesterday

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
2.1k
Forks
369
Last Push
2026-11-10
yesterday
Commits (4 wk)
532
Downloads (7d)
172,434
npm
HN mentions (30d)
—
Open Issues
6
Rank Change
=
was #18

Analysis

Activity Inputs

81.8 / 100
StarsRepository reach
19.9 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
11.9 / 20

Common questions about Gitlab MCP

Public supply-chain signals for Gitlab MCP are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Gitlab MCP carries less obvious unverified-evidence risk than projects with thin signals.
Does Gitlab MCP publish package provenance?
Yes. Gitlab MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Gitlab MCP have an OpenSSF Scorecard?
Gitlab MCP has an OpenSSF Scorecard score of 8.3/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Gitlab MCP actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Gitlab MCP use?
Gitlab MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Gitlab MCP's commits signed?
41% of the last 100 commits to Gitlab MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

Compare Gitlab MCP head-to-head

Gitlab MCP vs Codebase Memory MCP → Gitlab MCP vs Playwright MCP → Gitlab MCP vs Mobile MCP →

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
Gitlab MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Gitlab MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected

Maintain Gitlab MCP?

For maintainers

HVTrust scores Gitlab MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 16HVTrust 3Grade 3Scorecard 1Delisted 1Listed 1Provenance 1MCP 1
2026-11-10
Rank Moved
Rank rose 43 spots (#61 → #18)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → A
2026-09-23
Rank Moved
Rank rose 532 spots (#587 → #55)
2026-09-23
HVTrust Changed
HVTrust up 52.4pts (34.5 → 86.9)
2026-09-22
Newly Listed
First tracked at rank #587
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-06
Grade Changed
Trust grade C → A
2026-09-06
Rank Moved
Rank rose 619 spots (#659 → #40)
2026-09-06
HVTrust Changed
HVTrust up 31.4pts (55.9 → 87.3)
2026-09-05
Rank Moved
Rank dropped 86 spots (#573 → #659)
2026-09-03
Scorecard Added
OSSF Scorecard: 5.8/10
2026-09-03
Grade Changed
Trust grade D → C
2026-09-03
Rank Moved
Rank rose 185 spots (#763 → #578)
2026-09-03
HVTrust Changed
HVTrust up 7.7pts (48.0 → 55.7)
2026-09-02
Rank Moved
Rank dropped 33 spots (#730 → #763)
2026-09-01
Rank Moved
Rank dropped 32 spots (#698 → #730)
2026-08-31
Rank Moved
Rank dropped 31 spots (#667 → #698)
2026-08-30
Rank Moved
Rank dropped 22 spots (#645 → #667)
2026-08-29
Rank Moved
Rank dropped 39 spots (#606 → #645)
2026-08-28
Rank Moved
Rank dropped 15 spots (#591 → #606)
2026-08-26
Rank Moved
Rank dropped 88 spots (#496 → #584)
2026-08-24
Rank Moved
Rank dropped 12 spots (#481 → #493)
2026-08-22
Rank Moved
Rank rose 15 spots (#499 → #484)
2026-08-19
Rank Moved
Rank dropped 10 spots (#489 → #499)
2026-08-17
Rank Moved
Rank rose 12 spots (#501 → #489)
GitHub → Website → npm: @zereight/mcp-gitlab

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 90.9 Grade A
Markdown:
[![HVTrust](https://hvtracker.net/badge/gitlab-mcp.svg)](https://hvtracker.net/agents/gitlab-mcp)
HTML:
<a href="https://hvtracker.net/agents/gitlab-mcp"><img src="https://hvtracker.net/badge/gitlab-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON