Gitlab (yoda.digital) MCP Server
@yoda.digital/gitlab-mcp-server
npm
v0.9.1
Source verified
Published by yoda-digital — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
GitLab MCP Server - A Model Context Protocol server for GitLab integration
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 − 6 = 94. 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:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
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 1
critical Completed toxic-flow trifecta across toolsMTC-FLOW-002
This server (without client built-ins) exposes a complete data-exfiltration chain: list_issue_discussions → get_environment → create_issue. Untrusted input is ingested, private data is read, and it can be sent to an external sink via the agent composing the tools (→). Static analysis proves the primitive exists, not that a specific run will occur.
Fix: Remove one leg of the trifecta: isolate untrusted-input tools from secret-reading tools and from egress tools, or require human approval between them.
Location: flow list_issue_discussions → get_environment → create_issue
Tools 88
Each tool and what it can reach — statically extracted from the published source.
create_issuenetwork egresscreate_issue_notenetwork egressget_environmentreads sensitive dataget_file_contentsreads sensitive datalist_issue_discussionsingests untrusted inputlist_issue_notesingests untrusted inputapprove_merge_requestno sensitive capabilitycancel_auto_mergeno sensitive capabilitycancel_jobno sensitive capabilitycancel_pipelineno sensitive capability
Show 78 more tools ↓
compare_branchesno sensitive capabilitycreate_branchno sensitive capabilitycreate_groupno sensitive capabilitycreate_group_wiki_pageno sensitive capabilitycreate_labelno sensitive capabilitycreate_merge_requestno sensitive capabilitycreate_merge_request_discussionno sensitive capabilitycreate_merge_request_noteno sensitive capabilitycreate_milestoneno sensitive capabilitycreate_or_update_fileno sensitive capabilitycreate_project_wiki_pageno sensitive capabilitycreate_releaseno sensitive capabilitycreate_repositoryno sensitive capabilitycreate_tagno sensitive capabilitydelete_branchno sensitive capabilitydelete_groupno sensitive capabilitydelete_group_wiki_pageno sensitive capabilitydelete_project_wiki_pageno sensitive capabilityedit_group_wiki_pageno sensitive capabilityedit_project_wiki_pageno sensitive capabilityfork_repositoryno sensitive capabilityget_current_userno sensitive capabilityget_groupno sensitive capabilityget_group_wiki_pageno sensitive capabilityget_jobno sensitive capabilityget_job_logno sensitive capabilityget_job_log_smartno sensitive capabilityget_merge_request_changesno sensitive capabilityget_merge_request_commitsno sensitive capabilityget_pipelineno sensitive capabilityget_pipeline_summaryno sensitive capabilityget_projectno sensitive capabilityget_project_eventsno sensitive capabilityget_project_wiki_pageno sensitive capabilityget_repository_treeno sensitive capabilityget_userno sensitive capabilitylist_branchesno sensitive capabilitylist_commitsno sensitive capabilitylist_environmentsno sensitive capabilitylist_group_membersno sensitive capabilitylist_group_projectsno sensitive capabilitylist_group_subgroupsno sensitive capabilitylist_group_wiki_pagesno sensitive capabilitylist_groupsno sensitive capabilitylist_issuesno sensitive capabilitylist_labelsno sensitive capabilitylist_merge_request_discussionsno sensitive capabilitylist_merge_request_notesno sensitive capabilitylist_merge_requestsno sensitive capabilitylist_milestonesno sensitive capabilitylist_pipeline_jobsno sensitive capabilitylist_pipelinesno sensitive capabilitylist_project_membersno sensitive capabilitylist_project_wiki_pagesno sensitive capabilitylist_protected_branchesno sensitive capabilitylist_releasesno sensitive capabilitylist_tagsno sensitive capabilitylist_usersno sensitive capabilitymerge_merge_requestno sensitive capabilityprotect_branchno sensitive capabilitypush_filesno sensitive capabilityrebase_merge_requestno sensitive capabilityretry_jobno sensitive capabilityretry_pipelineno sensitive capabilitysearch_repositoriesno sensitive capabilityset_auto_mergeno sensitive capabilitytrigger_pipelineno sensitive capabilityunapprove_merge_requestno sensitive capabilityunprotect_branchno sensitive capabilityupdate_groupno sensitive capabilityupdate_issueno sensitive capabilityupdate_labelno sensitive capabilityupdate_merge_requestno sensitive capabilityupdate_merge_request_noteno sensitive capabilityupdate_milestoneno sensitive capabilityupdate_projectno sensitive capabilityupload_group_wiki_attachmentno sensitive capabilityupload_project_wiki_attachmentno sensitive capability
Toxic flows 1
Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).
What this scan could not see
- Tools were statically extracted from the published source (88 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.9.1 latest |
A 94/100 | 1 | 1.13.0 | 2026-09-07 |
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.
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 @yoda.digital/gitlab-mcp-server --onlineOther implementations of Gitlab 25
Independent packages implementing the same tool, scanned with the same engine. Compare all 26 side by side →
MCP Server for GitLab API - repository management and DevOps automation
GitLab MCP Server with GraphQL discovery
MCP server for GitLab API integration with comprehensive project, issue, merge request, pipeline, and job management capabilities
GitLab MCP server for projects, merge requests, issues, pipelines, wiki, releases, and more
基于 Model Context Protocol (MCP) 框架构建的 GitLab 集成服务器，提供与 GitLab 实例的强大集成能力
Works with the GitLab REST API v4 using a personal access token to browse projects, read repository files, and manage issues and merge requests; supports GitLab.com and self-hosted instances.
More in Developer Tools
Hotel booking MCP server — 300K+ properties, real confirmation numbers, loyalty programs. Builders monetize every booking via Stripe Connect. The first MCP server that completes real hotel reservations inside AI conversations.
Manage AdGuard Home through AI assistants
Read-only Azure DevOps for MCP clients using only your existing browser session — no PAT, no Azure CLI. Browse work items, pull requests, comments, attachments and Artifacts feeds across every project, repo and feed you can access.
MCP server for Adobe Experience Manager Assets integration development
Servidor MCP para el tiempo oficial de España (API pública OpenData de AEMET). Predicción, observación y avisos como herramientas MCP tipadas.
A standalone MCP stdio bridge for Affinity by Canva's local MCP SSE server.