Gitlab
NPM · @PIPEWORX/MCP-GITLAB · 2 COMPONENTS
GitLab MCP — wraps the GitLab REST API v4 (BYO API key)
Available components
Last scanned (17 hours ago)
Scores higher than 77% of npm servers
Category Version Control
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-gitlab). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 735 tokens (~147/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +2
- Stability: unverified → 0.13 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 29 Oct 26 80
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed npm/@pipeworx/mcp-gitlab@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-gitlab |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-gitlab/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3637325068 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:23b6ba8f8ac9e44c2a8c1d48e887ca031f891451e6818447ba2ce35d3c2058634eda8411e066c3d4e7b7fb5dbd339a5f63e40b4a38439d0e6d0acaef2 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
gitlab_get_file ~136
Fetch file content from a GitLab repository by project ID and file path (e.g., "src/main.py"). Returns decoded content, file size, name, and encoding.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | GitLab personal access token |
| file_path | string | yes | Path to the file within the repository |
| project_id | string | yes | Project ID (numeric) or full path "namespace/project" (e.g. "gitlab-org/gitlab") — pass the plain path, do not URL-encode it. |
| ref | string | – | Branch, tag, or commit SHA (default: default branch) |
No output schema declared.
No examples provided.
gitlab_get_project ~116
Get details for a specific GitLab project (e.g., project ID "123" or path "group/project"). Returns name, description, visibility, stars, forks, and default branch.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | GitLab personal access token |
| id | string | yes | Project ID (numeric, e.g. "278964") or full path "namespace/project" (e.g. "gitlab-org/gitlab"). Pass the plain path — do NOT URL-encode it; the pack encodes it. |
No output schema declared.
No examples provided.
gitlab_list_issues ~165
Search issues in a GitLab project by project ID. Returns issue ID, title, state (open/closed), labels, assignee, and URL. Filter by status and labels.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | GitLab personal access token |
| per_page | number | – | Number of issues to return (default 20, max 100) |
| project_id | string | yes | Project ID (numeric) or full path "namespace/project" (e.g. "gitlab-org/gitlab") — pass the plain path, do not URL-encode it. |
| search | string | – | Search issues by title or description |
| state | string | – | Filter by state: "opened", "closed", or "all" (default: "opened") |
No output schema declared.
No examples provided.
gitlab_list_mrs ~155
List merge requests in a GitLab project by project ID. Returns MR ID, title, state, author, source/target branches, and URL. Filter by state and author.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | GitLab personal access token |
| per_page | number | – | Number of merge requests to return (default 20, max 100) |
| project_id | string | yes | Project ID (numeric) or full path "namespace/project" (e.g. "gitlab-org/gitlab") — pass the plain path, do not URL-encode it. |
| state | string | – | Filter by state: "opened", "closed", "merged", or "all" (default: "opened") |
No output schema declared.
No examples provided.
gitlab_list_projects ~110
List all accessible GitLab projects. Returns project ID, name, path, description, star count, and URL. Use gitlab_get_project to fetch detailed info.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | GitLab personal access token |
| owned | boolean | – | If true, only return projects owned by the user (default: false) |
| per_page | number | – | Number of projects to return (default 20, max 100) |
| search | string | – | Search projects by name |
No output schema declared.
No examples provided.
How do I install the Gitlab MCP server?
Gitlab runs locally as an npm package, launched with npx -y @pipeworx/mcp-gitlab. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-gitlab
claude mcp add pipeworx-io-gitlab -- npx -y @pipeworx/mcp-gitlab
What is the Gitlab MCP server?
Gitlab is an MCP server listed in the public MCP registry as io.github.pipeworx-io/gitlab. GitLab MCP, wraps the GitLab REST API v4 (BYO API key). This page covers its npm package (@pipeworx/mcp-gitlab).
Is the Gitlab MCP server safe to use?
Gitlab scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Gitlab MCP server expose?
Gitlab exposes 5 tools: gitlab_list_projects, gitlab_get_project, gitlab_list_issues, gitlab_list_mrs, gitlab_get_file. Their descriptions and schemas cost roughly 682 tokens of context every time the server is loaded.
Is the Gitlab MCP server still maintained?
Gitlab is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Gitlab MCP server under?
Gitlab declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.