Gitlab (vish288) MCP Server

mcp-gitlab PyPI v0.9.3

Published by vish288 — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for GitLab API — projects, MRs, pipelines, CI/CD variables, approvals, and more

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 83

Each tool and what it can reach — statically extracted from the published source.

  • gitlab_create_issuenetwork egress
  • gitlab_add_issue_commentno sensitive capability
  • gitlab_add_mr_noteno sensitive capability
  • gitlab_approve_mrno sensitive capability
  • gitlab_award_emojino sensitive capability
  • gitlab_cancel_jobno sensitive capability
  • gitlab_cancel_pipelineno sensitive capability
  • gitlab_compareno sensitive capability
  • gitlab_create_branchno sensitive capability
  • gitlab_create_commitno sensitive capability
Show 73 more tools ↓
  • gitlab_create_group_variableno sensitive capability
  • gitlab_create_mrno sensitive capability
  • gitlab_create_mr_approval_ruleno sensitive capability
  • gitlab_create_mr_discussionno sensitive capability
  • gitlab_create_pipelineno sensitive capability
  • gitlab_create_projectno sensitive capability
  • gitlab_create_project_approval_ruleno sensitive capability
  • gitlab_create_releaseno sensitive capability
  • gitlab_create_tagno sensitive capability
  • gitlab_create_variableno sensitive capability
  • gitlab_delete_branchno sensitive capability
  • gitlab_delete_group_variableno sensitive capability
  • gitlab_delete_mr_approval_ruleno sensitive capability
  • gitlab_delete_mr_noteno sensitive capability
  • gitlab_delete_projectno sensitive capability
  • gitlab_delete_project_approval_ruleno sensitive capability
  • gitlab_delete_releaseno sensitive capability
  • gitlab_delete_tagno sensitive capability
  • gitlab_delete_variableno sensitive capability
  • gitlab_get_commitno sensitive capability
  • gitlab_get_groupno sensitive capability
  • gitlab_get_issueno sensitive capability
  • gitlab_get_job_logno sensitive capability
  • gitlab_get_mrno sensitive capability
  • gitlab_get_mr_approvalsno sensitive capability
  • gitlab_get_pipelineno sensitive capability
  • gitlab_get_projectno sensitive capability
  • gitlab_get_project_approvalsno sensitive capability
  • gitlab_get_releaseno sensitive capability
  • gitlab_get_tagno sensitive capability
  • gitlab_list_branchesno sensitive capability
  • gitlab_list_commitsno sensitive capability
  • gitlab_list_group_variablesno sensitive capability
  • gitlab_list_groupsno sensitive capability
  • gitlab_list_issuesno sensitive capability
  • gitlab_list_mr_approval_rulesno sensitive capability
  • gitlab_list_mr_commitsno sensitive capability
  • gitlab_list_mr_discussionsno sensitive capability
  • gitlab_list_mr_notesno sensitive capability
  • gitlab_list_mr_pipelinesno sensitive capability
  • gitlab_list_mrsno sensitive capability
  • gitlab_list_pipelinesno sensitive capability
  • gitlab_list_project_approval_rulesno sensitive capability
  • gitlab_list_releasesno sensitive capability
  • gitlab_list_tagsno sensitive capability
  • gitlab_list_variablesno sensitive capability
  • gitlab_merge_mrno sensitive capability
  • gitlab_merge_mr_sequenceno sensitive capability
  • gitlab_mr_changesno sensitive capability
  • gitlab_play_jobno sensitive capability
  • gitlab_rebase_mrno sensitive capability
  • gitlab_remove_emojino sensitive capability
  • gitlab_reply_to_discussionno sensitive capability
  • gitlab_resolve_discussionno sensitive capability
  • gitlab_retry_jobno sensitive capability
  • gitlab_retry_pipelineno sensitive capability
  • gitlab_share_group_with_groupno sensitive capability
  • gitlab_share_project_with_groupno sensitive capability
  • gitlab_subscribe_mrno sensitive capability
  • gitlab_unapprove_mrno sensitive capability
  • gitlab_unshare_group_with_groupno sensitive capability
  • gitlab_unshare_project_with_groupno sensitive capability
  • gitlab_unsubscribe_mrno sensitive capability
  • gitlab_update_group_variableno sensitive capability
  • gitlab_update_issueno sensitive capability
  • gitlab_update_mrno sensitive capability
  • gitlab_update_mr_approval_ruleno sensitive capability
  • gitlab_update_mr_noteno sensitive capability
  • gitlab_update_project_approval_ruleno sensitive capability
  • gitlab_update_project_approvalsno sensitive capability
  • gitlab_update_project_merge_settingsno sensitive capability
  • gitlab_update_releaseno sensitive capability
  • gitlab_update_variableno sensitive capability

What this scan could not see

Versions 2

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.9.3 latest A 96/100 0 1.13.0 2026-08-25
v0.9.2 A 96/100 0 1.12.1 2026-07-27

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mcp-gitlab-2/badge.svg)](https://mcptrustchecker.com/registry/mcp-gitlab-2)
HTML
<a href="https://mcptrustchecker.com/registry/mcp-gitlab-2"><img src="https://mcptrustchecker.com/registry/mcp-gitlab-2/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mcp-gitlab-2/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan mcp-gitlab --online --registry pypi

Use the free API → How scoring works

Other implementations of Gitlab 25

Independent packages implementing the same tool, scanned with the same engine. Compare all 26 side by side →

More in Developer Tools