GitLab MCP Server
io.github.zereight/gitlab-mcp · v2.3.5
GitLab MCP server for projects, merge requests, issues, pipelines, wiki, releases, and more.
Normalized over 100 points of available evidence.
Score breakdown
Known advisories
source: OSV.dev@zereight/mcp-gitlab: Unauthenticated arbitrary file read via `upload_markdown` enables PAT exfiltration and full account takeover
@zereight/mcp-gitlab Vulnerable to Server-Side Request Forgery
@zereight/mcp-gitlab: DNS rebinding reaches local Streamable HTTP MCP transport
@zereight/mcp-gitlab has multiple safety-control bypasses: execute_graphql read-only + allow-list bypass, unauthenticated transports, session-exhaustion DoS
Metadata change timeline
rug-pull detection- v2.3.2 → v2.3.5Oct 21, 2026
versionchanged version bump"2.3.2" → "2.3.5"
titlechanged title text edit"" → "GitLab MCP Server"
packages.0.versionchanged package version bump"2.3.2" → "2.3.5"
packages.1.identifierchanged image tag 2.3.2 → 2.3.5 (version)"docker.io/zereight050/gitlab-mcp:2.3.2" → "docker.io/zereight050/gitlab-mcp:2.3.5"
- First snapshot (v2.3.2)Oct 17, 2026
Tool lists: not published by the registry — unknown.
FAQ
auto-generated from the data aboveIs GitLab MCP Server safe?
MCPWatch gives GitLab MCP Server a heuristic security score of 92/100 (strong), based on 100 points of available evidence. This is an automated heuristic, not an audit.
Does GitLab MCP Server have known CVEs or vulnerabilities?
OSV.dev lists 4 unique advisories for @zereight/mcp-gitlab (CVE-2026-61560, CVE-2026-61559, CVE-2026-61568). 0 affect the current version 2.3.5.
When was GitLab MCP Server last updated?
The latest registry version is 2.3.5, published Oct 20, 2026. The last push to zereight/gitlab-mcp was on Oct 21, 2026. MCPWatch last checked it on Oct 21, 2026.
What license does GitLab MCP Server use?
GitHub reports the license of zereight/gitlab-mcp as MIT.