updated 2026-09-26 06:32 UTC

GitLab MCP Server

jmrplens/gitlab-mcp-server

Open source GitLab MCP server for AI assistants: 2-tool dynamic find/execute over 850+ GitLab actions (1,000+ Enterprise), stdio/HTTP/OAuth, safe/read-only modes.

MCP Servers Go Listed MIT

Is GitLab MCP Server safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 7.3 / 10
Provenance None
Signed commits 100%
Last push yesterday
Compare GitLab MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: GitLab MCP Server scores 64.1/100 (Grade C), ranked #503 of 1325 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 7.3/10; 100% of recent commits are signed; last pushed 2026-09-25. Every point is earned from checkable signals — never paid placement. How scoring works →

How GitLab MCP Server compares in MCP Servers

  1. #290 CrowdSentinels AI MCP 64.2 +0.1
  2. #291 Google Maps MCP Server 64.2 +0.1
  3. #292 GitLab MCP Server 64.1 this agent
  4. #293 Domain Search MCP 64.1 ±0
  5. #294 Google Analytics MCP 63.9 −0.2

Bars show each HVTrust score; the tick marks GitLab MCP Server’s 64.1.

Where the 64.1 comes from

HVTrust dimensions vs the MCP Servers average

64.1 / 100 · 100.0% confidence

GitLab MCP Server MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
14.1 / 25
3.8 above avg 10.3
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
14.7 / 17
2.5 above avg 12.2
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
7.8 above avg 12.1
AdoptionLog-scaled stars · package downloads
3.9 / 20
3.3 below avg 7.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-26
Rank Moved
Rank dropped 15 spots (#488 → #503)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
Maintainer Checklist
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Compare with another agent Get email alerts for GitLab MCP Server View MCP Servers Report missing data
63.3
Activity sub-score · out of 100
#292
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 C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-26 06:32 UTC · Repo last pushed yesterday

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
41
Forks
5
Last Push
2026-09-25
yesterday
Commits (4 wk)
385
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
26
Rank Change
▼15
was #488

Analysis

Activity Inputs

63.3 / 100
StarsRepository reach
9.7 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
3.6 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
7.3 / 10
OpenSSF Scorecard · scanned Sep 26, 2026
Signed Commits
100%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 3
CI-Tests 10
CII-Best-Practices 0
Code-Review 0
Contributors 0
Dangerous-Workflow -1
Dependency-Update-Tool 10
Fuzzing 10
License 10
Maintained 10
Packaging -1
Pinned-Dependencies 6
SAST 10
Security-Policy 10
Signed-Releases 8
Token-Permissions -1
Vulnerabilities 9

Common questions about GitLab MCP Server

GitLab MCP Server has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does GitLab MCP Server publish package provenance?
No published build provenance is currently detected for GitLab MCP Server. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does GitLab MCP Server have an OpenSSF Scorecard?
GitLab MCP Server has an OpenSSF Scorecard score of 7.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 Server actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does GitLab MCP Server use?
GitLab MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are GitLab MCP Server's commits signed?
100% of the last 100 commits to GitLab MCP Server 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 Server 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
high confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
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 Server'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
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain GitLab MCP Server?

For maintainers

HVTrust scores GitLab MCP Server 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 21Listed 2HVTrust 2Grade 1Scorecard 1Delisted 1MCP 1Surface 1
2026-09-26
Rank Moved
Rank dropped 15 spots (#488 → #503)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank dropped 138 spots (#350 → #488)
2026-09-23
HVTrust Changed
HVTrust up 14.3pts (50.1 → 64.4)
2026-09-22
Newly Listed
First tracked at rank #350
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-20
Rank Moved
Rank rose 11 spots (#499 → #488)
2026-09-11
Rank Moved
Rank dropped 11 spots (#476 → #487)
2026-09-07
Rank Moved
Rank dropped 26 spots (#436 → #462)
2026-09-06
Rank Moved
Rank rose 11 spots (#447 → #436)
2026-09-05
Rank Moved
Rank dropped 66 spots (#381 → #447)
2026-09-03
Rank Moved
Rank dropped 17 spots (#360 → #377)
2026-09-02
Rank Moved
Rank dropped 14 spots (#346 → #360)
2026-09-01
Scorecard Added
OSSF Scorecard: 7.3/10
2026-09-01
Grade Changed
Trust grade D → C
2026-09-01
Rank Moved
Rank rose 800 spots (#1146 → #346)
2026-09-01
HVTrust Changed
HVTrust up 39.0pts (24.1 → 63.1)
2026-08-31
Rank Moved
Rank dropped 29 spots (#1117 → #1146)
2026-08-30
Rank Moved
Rank dropped 49 spots (#1068 → #1117)
2026-08-29
Rank Moved
Rank dropped 43 spots (#1025 → #1068)
2026-08-28
Rank Moved
Rank dropped 38 spots (#987 → #1025)
2026-08-27
Rank Moved
Rank dropped 15 spots (#972 → #987)
2026-08-26
Rank Moved
Rank dropped 93 spots (#879 → #972)
2026-08-21
Rank Moved
Rank rose 14 spots (#902 → #888)
2026-08-17
Rank Moved
Rank rose 20 spots (#907 → #887)
2026-08-16
Rank Moved
Rank dropped 21 spots (#886 → #907)
2026-08-12
Rank Moved
Rank rose 17 spots (#900 → #883)
2026-08-10
Rank Moved
Rank dropped 49 spots (#840 → #889)
2026-08-08
Newly Listed
First tracked at rank #831
GitHub →

Embed Badge Badge guide for maintainers →

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

Other agents in MCP Servers

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