com.mcparmory/gitlab
PYPI · MCPARMORY-GITLAB · 2 COMPONENTS · SCANNED SEP 20
Manage projects, groups, branches, merge requests, and CI/CD pipelines
Available components
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 Security37
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Install-script risk not yet assessed.Unverified
- 2 of 46 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (MIT License) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 131 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
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 Management83
- Stability observed for 25 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 current MCP spec version (2026-07-28).Pass
How do I install the com.mcparmory/gitlab MCP server?
com.mcparmory/gitlab runs locally as a PyPI package, launched with uvx mcparmory-gitlab. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcparmory-gitlab
claude mcp add com-mcparmory-gitlab -- uvx mcparmory-gitlab
{
"mcpServers": {
"com-mcparmory-gitlab": {
"command": "uvx",
"args": [
"mcparmory-gitlab"
]
}
}
} {
"servers": {
"com-mcparmory-gitlab": {
"command": "uvx",
"args": [
"mcparmory-gitlab"
]
}
}
} codex mcp add com-mcparmory-gitlab -- uvx mcparmory-gitlab
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mcparmory-gitlab": {
"type": "local",
"command": [
"uvx",
"mcparmory-gitlab"
],
"enabled": true
}
}
} openclaw mcp add com-mcparmory-gitlab --command uvx --arg mcparmory-gitlab
mcp_servers:
com-mcparmory-gitlab:
command: "uvx"
args: ["mcparmory-gitlab"] {
"McpServers": {
"com-mcparmory-gitlab": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"mcparmory-gitlab"
]
}
}
} assistant mcp add com-mcparmory-gitlab -t stdio -c uvx -a mcparmory-gitlab
{
"mcpServers": {
"com-mcparmory-gitlab": {
"command": "uvx",
"args": [
"mcparmory-gitlab"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 −3
- Stability: pass → 0.77 functional
- 17 Sept 26 0
- Stability: 0.97 → pass security
- 16 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.
- 14 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 12 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 11 Sept 26 −18
- Malware scan: pass → unverified ▼ security
- Stability: pass → 0.80 functional
- 10 Sept 26 0
- Stability: 0.97 → pass security
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 pypi/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 | pypi |
Background: How many MCP packages publish verified provenance →
Dependencies 46 packages
| Packages resolved | 46 |
|---|---|
| Stale | 1 |
| No linked repository | 1 |
| 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 →
update_group_badge Update Group Badge ~119
Updates an existing badge for a group. Allows modification of the badge's name, image URL, and link URL.
| Name | Type | Req | Description |
|---|---|---|---|
| badge_id | string | yes | The unique identifier of the badge to update. |
| id | string | yes | The ID or URL-encoded path of the group owned by the authenticated user. |
| image_url | string | – | The URL of the image to display as the badge. |
| link_url | string | – | The URL where the badge link should direct users. |
| name | string | – | A descriptive name for the badge. |
No output schema declared.
No examples provided.
update_project_badge Update Project Badge ~118
Updates an existing badge for a project. Allows modification of the badge's name, image URL, and link URL.
| Name | Type | Req | Description |
|---|---|---|---|
| badge_id | string | yes | The unique identifier of the badge to update. |
| id | string | yes | The project identifier, either as a numeric ID or URL-encoded path. |
| image_url | string | – | The URL of the image to display as the badge. |
| link_url | string | – | The URL that the badge links to when clicked. |
| name | string | – | A descriptive name for the badge. |
No output schema declared.
No examples provided.
upload_alert_metric_image 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.
| Name | Type | Req | Description |
|---|---|---|---|
| alert_iid | string | yes | The internal ID of the alert to attach the metric image to. |
| file | string | yes | Base64-encoded file content for upload. The image file to upload. Supported formats are typically PNG, JPG, and GIF. |
| id | string | yes | The project identifier, either as a numeric ID or URL-encoded path. |
| url | string | – | Optional URL to view additional metric information or the source of the metric data. |
| url_text | string | – | Optional descriptive text explaining the metric image content or the linked URL. |
No output schema declared.
No examples provided.
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 PyPI package (mcparmory-gitlab).
Is the com.mcparmory/gitlab MCP server safe to use?
com.mcparmory/gitlab scores 62 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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.