Is Gitlab MCP safe to use?

Gitlab MCP has an HVTrust score of 87.4/100 (Grade A), ranked #44 of 1328 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Gitlab MCP?

Gitlab MCP scores 87.4/100 on HVTracker's evidence-weighted HVTrust scale. It has 2.0k GitHub stars and is categorized under MCP Servers.

Gitlab MCP

zereight/gitlab-mcp

First gitlab mcp for you, building together

MCP Servers TypeScript Grade A Listed MIT

87.4/100

Rank #44 of 1328

Compare Gitlab MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-09-08 · 0d ago

Recent change

Grade Changed +9

Is Gitlab MCP safe? Gitlab MCP scores 87.4/100 (Grade A), ranked #44 of 1328 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 6.3/10; 28% of recent commits are signed; last pushed 2026-09-08. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#8 MCP Hangar — 87.4 (A) → #9 ARC-1 — 87.4 (A) → #11 LinkedIn MCP Server — 87.2 (A) → #12 Canvas MCP — 87.1 (A) →

Quick Trust Read

What Would Improve It

Increase the share of verified signed commits for clearer maintainer identity.

Recent Changes

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)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 6.3/10. Tighten the weakest checks to improve public safety evidence.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent Get email alerts for Gitlab MCP View MCP Servers Report missing data

81.7

Activity sub-score · out of 100

#10

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 →

Rank Trend

2026-08-11 2026-09-08

Activity & Reach

Stars

2.0k

Forks

353

Last Push

2026-09-08

today

Commits (4 wk)

176

Downloads (7d)

139,050

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #43

Analysis

HVTrust Dimensions vs MCP Servers

87.4 / 100 · 100.0% confidence

Gitlab MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

16.8 / 25

6.9 above avg 9.9

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

13.9 / 17

1.9 above avg 12.0

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

7.8 above avg 12.2

AdoptionLog-scaled stars · package downloads

14.8 / 20

7.9 above avg 6.9

Activity Inputs

81.7 / 100

StarsRepository reach

19.8 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

11.9 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

6.3 / 10

OpenSSF Scorecard · scanned Sep 7, 2026

Signed Commits

28%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 1

CI-Tests 10

CII-Best-Practices 0

Code-Review 6

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 3

SAST 7

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 8

Is Gitlab MCP safe?

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 6.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?

28% 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.

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

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

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)

2026-08-13

Rank Moved

Rank dropped 15 spots (#483 → #498)

2026-08-10

Rank Moved

Rank dropped 13 spots (#477 → #490)

2026-08-08

Newly Listed

First tracked at rank #471

GitHub → npm: @zereight/mcp-gitlab

Embed Badge Badge guide for maintainers →

For maintainers

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.3 · Raw JSON