Gitlab Http Api MCP Server
gitlab-http-api-mcp
npm
v0.2.6
Published by rkorablin — 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 over HTTP API (projects, issues, MRs, CI pipelines, jobs)
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:
| Points | Adoption-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 1
medium Untrusted input can drive an external actionMTC-FLOW-005
Untrusted-input tools ([gitlab_get_job_trace]) co-exist with external-action tools ([gitlab_create_issue, gitlab_create_issue_note]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.
Evidence: untrusted [gitlab_get_job_trace] → sinks [gitlab_create_issue, gitlab_create_issue_note]
Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.
Location: flow gitlab_get_job_trace → gitlab_create_issue
Tools 51
Each tool and what it can reach — statically extracted from the published source.
gitlab_create_issuenetwork egressgitlab_create_issue_notenetwork egressgitlab_get_job_traceingests untrusted inputgitlab_add_job_token_allowlistno sensitive capabilitygitlab_add_job_token_groups_allowlistno sensitive capabilitygitlab_cancel_pipelineno sensitive capabilitygitlab_create_group_variableno sensitive capabilitygitlab_create_merge_requestno sensitive capabilitygitlab_create_pipelineno sensitive capabilitygitlab_create_project_variableno sensitive capability
Show 41 more tools ↓
gitlab_create_repository_branchno sensitive capabilitygitlab_delete_group_variableno sensitive capabilitygitlab_delete_project_variableno sensitive capabilitygitlab_get_current_userno sensitive capabilitygitlab_get_group_variableno sensitive capabilitygitlab_get_issueno sensitive capabilitygitlab_get_job_token_scopeno sensitive capabilitygitlab_get_merge_requestno sensitive capabilitygitlab_get_merge_request_changesno sensitive capabilitygitlab_get_pipelineno sensitive capabilitygitlab_get_projectno sensitive capabilitygitlab_get_project_variableno sensitive capabilitygitlab_list_group_variablesno sensitive capabilitygitlab_list_issue_notesno sensitive capabilitygitlab_list_issuesno sensitive capabilitygitlab_list_job_token_allowlistno sensitive capabilitygitlab_list_job_token_groups_allowlistno sensitive capabilitygitlab_list_merge_request_discussionsno sensitive capabilitygitlab_list_merge_request_notesno sensitive capabilitygitlab_list_merge_requestsno sensitive capabilitygitlab_list_pipeline_jobsno sensitive capabilitygitlab_list_pipelinesno sensitive capabilitygitlab_list_project_variablesno sensitive capabilitygitlab_list_projectsno sensitive capabilitygitlab_list_protected_branchesno sensitive capabilitygitlab_list_repository_branchesno sensitive capabilitygitlab_merge_merge_requestno sensitive capabilitygitlab_play_jobno sensitive capabilitygitlab_protect_branchno sensitive capabilitygitlab_remove_job_token_allowlistno sensitive capabilitygitlab_remove_job_token_groups_allowlistno sensitive capabilitygitlab_retry_jobno sensitive capabilitygitlab_retry_pipelineno sensitive capabilitygitlab_unprotect_branchno sensitive capabilitygitlab_update_group_variableno sensitive capabilitygitlab_update_issueno sensitive capabilitygitlab_update_merge_requestno sensitive capabilitygitlab_update_projectno sensitive capabilitygitlab_update_project_variableno sensitive capabilitygitlab_upsert_group_variableno sensitive capabilitygitlab_upsert_project_variableno 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 (51 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 4
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.2.6 latest |
A 96/100 | 1 | 1.13.0 | 2026-09-10 |
v0.2.5 |
A 96/100 | 1 | 1.13.0 | 2026-09-09 |
v0.2.4 |
A 96/100 | 1 | 1.12.1 | 2026-08-09 |
v0.2.2 |
A 96/100 | 1 | 1.12.1 | 2026-08-04 |
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 gitlab-http-api-mcp --onlineMore 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.
Generates production-ready UI components from natural language, inspired by v0.
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.