Back to MCP Trust Indexm8ven
C
Emerging
74/100
53 min ago

GitLab MCP

Harness-neutral MCP server enabling GitLab repository workflows—merge requests, CI diagnosis, publishing, and variable management—through shared Agent Skills for Codex, Claude Code, Cline, Pi, and ChatGPT.

→ CobolJunkie/gitlab-mcp· listed on glama

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

CobolJunkie

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glama

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 2 credentials: GITLAB_PRIVATE_TOKEN, GITLAB_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configALLOW_SERVER_TOKEN_HTTPis disabled by default. =true exists only for
configGITLAB_ALLOW_INSECURE_HTTPinstance that cannot use TLS, set =true. The
🔐 secretGITLAB_PRIVATE_TOKEN
🔐 secretGITLAB_TOKEN$env: = "<token>"
configGITLAB_URL$env: = "https://gitlab.example.com"
configMCP_ALLOWED_HOSTSto a comma-separated allowlist of public host names. Put
configMCP_ALLOW_INSECURE_PUBLIC_URLtrue is available only for explicit local
configMCP_AUTH_FAILURE_LIMITlimits rejected tokens per directly connected
configMCP_AUTH_FAILURE_MAX_ENTRIESbounds failure-tracking state, default 1,024;
configMCP_AUTH_FAILURE_WINDOW_MSaddress within , default 20 failures per 60
configMCP_AUTH_VALIDATION_LIMIT
configMCP_AUTH_VALIDATION_WINDOW_MS
configMCP_HOST
configMCP_MAX_CONCURRENT_REQUESTScaps active MCP requests, default 32; and
configMCP_MAX_CONCURRENT_REQUESTS_PER_IDENTITYcaps requests for one validated
configMCP_MAX_REQUEST_BYTESpreventing unbounded request buffering. Set to an
configMCP_PORT
configMCP_PUBLIC_URL$env: = "https://mcp.example.com/mcp"
configMCP_READ_ONLYSet =true for an inspection-only deployment. In that mode the
configMCP_REQUEST_BODY_READ_TIMEOUT_MS
configMCP_SHUTDOWN_TIMEOUT_MS
configMCP_TOKEN_CACHE_MAX_ENTRIESlimits validated bearer identities, default
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

Domain consistency

npm scope @local doesn't match GitHub owner coboljunkie

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 1 concrete improvement we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/coboljunkie-gitlab-mcp-160eju)](https://m8ven.ai/mcp/coboljunkie-gitlab-mcp-160eju)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: ebd514ece97f00e19c73229578a15995b68c4418
code hash: f2979bd5ca9cdf9cea6c83d972d4a0b47ce57cec45238ad688230909d564a334
verified: 8/20/2026, 9:06:59 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client