Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.mcparmory/gitlab

OCI · GHCR.IO/MCPARMORY/GITLAB:1.0.3 · 2 COMPONENTS · SCANNED SEP 20

Manage projects, groups, branches, merge requests, and CI/CD pipelines

Available components

oci · ghcr.io/mcparmory/gitlab:1.0.3 50 pypi · mcparmory-gitlab 62
−1 this week 50 Trust /100
Trust breakdown (7 categories)

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 Security0
  • Malware scan not yet available for this package.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency32
Schema Quality & AI Usability82
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 5140 tokens (~96/item across 53 items; 53 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
  • Stability observed for 24 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 Safety98
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 10 of 11 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "execute_manual_job" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Partial
  • An AI judge read all 53 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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

How do I install the com.mcparmory/gitlab MCP server?

com.mcparmory/gitlab runs locally as a container image, launched with docker run --rm -i ghcr.io/mcparmory/gitlab:1.0.3. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

oci · ghcr.io/mcparmory/gitlab:1.0.3

# add to Claude Code
claude mcp add com-mcparmory-gitlab -- docker run --rm -i ghcr.io/mcparmory/gitlab:1.0.3
// .cursor/mcp.json
{
  "mcpServers": {
    "com-mcparmory-gitlab": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/mcparmory/gitlab:1.0.3"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-mcparmory-gitlab": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/mcparmory/gitlab:1.0.3"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add com-mcparmory-gitlab -- docker run --rm -i ghcr.io/mcparmory/gitlab:1.0.3
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-mcparmory-gitlab": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/mcparmory/gitlab:1.0.3"
      ],
      "enabled": true
    }
  }
}
# ~/.hermes/config.yaml
mcp_servers:
  com-mcparmory-gitlab:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/mcparmory/gitlab:1.0.3"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-mcparmory-gitlab": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/mcparmory/gitlab:1.0.3"
      ]
    }
  }
}
// mcp.json
{
  "mcpServers": {
    "com-mcparmory-gitlab": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/mcparmory/gitlab:1.0.3"
      ]
    }
  }
}
Changelog

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.

  • 19 Sept 26 −3
    • Stability: pass → 0.77 functional
  • 18 Sept 26 0
    • Stability: 0.97 → pass security
  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 −2
    • Stability: pass → 0.83 functional
  • 12 Sept 26 0
    • Stability: 0.97 → pass security
  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 20 Sept 2026 · Analysed oci/ghcr.io/mcparmory/gitlab:1.0.3

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem oci
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 53 exposed · ~5,140 tokens

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 →

Tool Tokens
update_group_badge ~119

Updates an existing badge for a group. Allows modification of the badge's name, image URL, and link URL.

NameTypeReqDescription
badge_idstringyesThe unique identifier of the badge to update.
idstringyesThe ID or URL-encoded path of the group owned by the authenticated user.
image_urlstring–The URL of the image to display as the badge.
link_urlstring–The URL where the badge link should direct users.
namestring–A descriptive name for the badge.

No output schema declared.

No examples provided.

update_project_badge ~118

Updates an existing badge for a project. Allows modification of the badge's name, image URL, and link URL.

NameTypeReqDescription
badge_idstringyesThe unique identifier of the badge to update.
idstringyesThe project identifier, either as a numeric ID or URL-encoded path.
image_urlstring–The URL of the image to display as the badge.
link_urlstring–The URL that the badge links to when clicked.
namestring–A descriptive name for the badge.

No output schema declared.

No examples provided.

upload_alert_metric_image ~153

Upload a metric image to an alert for visualization and documentation purposes. Optionally include a URL and description to provide context about the metric data.

NameTypeReqDescription
alert_iidstringyesThe internal ID of the alert to attach the metric image to.
filestringyesBase64-encoded file content for upload. The image file to upload. Supported formats are typically PNG, JPG, and GIF.
idstringyesThe project identifier, either as a numeric ID or URL-encoded path.
urlstring–Optional URL to view additional metric information or the source of the metric data.
url_textstring–Optional descriptive text explaining the metric image content or the linked URL.

No output schema declared.

No examples provided.

Common questions

What is the com.mcparmory/gitlab MCP server?

com.mcparmory/gitlab is an MCP server listed in the public MCP registry as com.mcparmory/gitlab. Manage projects, groups, branches, merge requests, and CI/CD pipelines. This page covers its container image (ghcr.io/mcparmory/gitlab:1.0.3).

Is the com.mcparmory/gitlab MCP server safe to use?

com.mcparmory/gitlab scores 50 out of 100 on VerifyMCP. 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 com.mcparmory/gitlab MCP server expose?

com.mcparmory/gitlab exposes 53 tools: get_group_badge, update_group_badge, remove_group_badge, list_group_badges, add_group_badge, and 48 more. Their descriptions and schemas cost roughly 5,140 tokens of context every time the server is loaded.

Is the com.mcparmory/gitlab MCP server still maintained?

com.mcparmory/gitlab is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.