Gitlab (therealchristhomas) MCP Server
@therealchristhomas/gitlab-mcp-server
npm
v1.5.2
Published by @therealchristhomas — 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 operations
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 − 7 = 93. 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 |
| −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 1
high Sensitive-source and external-sink co-existMTC-FLOW-004
Tools that read sensitive data ([get_file_contents]) and tools that can send data out ([create_issue]) are exposed together. An agent can move private data to the sink.
Evidence: sources [get_file_contents] → sinks [create_issue]
Fix: Keep secret-reading and egress capabilities on separate, separately-approved servers.
Location: flow get_file_contents → create_issue
Tools 30
Each tool and what it can reach — statically extracted from the published source.
create_issuenetwork egressget_file_contentsreads sensitive dataadd_issue_commentno sensitive capabilityadd_merge_request_commentno sensitive capabilitycreate_branchno sensitive capabilitycreate_group_milestoneno sensitive capabilitycreate_labelno sensitive capabilitycreate_merge_requestno sensitive capabilitycreate_milestoneno sensitive capabilitycreate_or_update_fileno sensitive capability
Show 20 more tools ↓
create_repositoryno sensitive capabilitydelete_group_milestoneno sensitive capabilitydelete_labelno sensitive capabilitydelete_milestoneno sensitive capabilityfork_repositoryno sensitive capabilitylist_group_milestonesno sensitive capabilitylist_issuesno sensitive capabilitylist_labelsno sensitive capabilitylist_merge_requestsno sensitive capabilitylist_milestonesno sensitive capabilitymerge_merge_requestno sensitive capabilitypush_filesno sensitive capabilitysearch_groupsno sensitive capabilitysearch_issuesno sensitive capabilitysearch_repositoriesno sensitive capabilityupdate_group_milestoneno sensitive capabilityupdate_issueno sensitive capabilityupdate_labelno sensitive capabilityupdate_merge_requestno sensitive capabilityupdate_milestoneno 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 (30 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 |
|---|---|---|---|---|
v1.5.2 latest |
A 93/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 @therealchristhomas/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.