F
Warning
36/100
12 hours ago

Warning. Serious findings — read the checks before connecting. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

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 the top badge — read-only, revoke anytime. What we access →

Install from

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

// key findings
🚨
Secret credentials may flow to a network call
4 flows detected: GITLAB_API_URL. We can’t prove the destination matches the brand the credential belongs to.
🚨
Known vulnerabilities in dependencies: 1 critical, 1 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 5 credentials: DOWNLOAD_TOKEN_SECRET, GITLAB_OAUTH_CLIENT_SECRET, GITLAB_TOKEN, GH_TOKEN, GITHUB_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies1 critical1 high

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

criticalform-data@4.0.0GHSA-fjxv-7rqg-78g4

form-data uses unsafe random function in form-data for choosing boundary

highform-data@4.0.0GHSA-hmw2-7cc7-3qxx

form-data: CRLF injection in form-data via unescaped multipart field names and filenames

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// required environment variables
This server reads these from process.env. You'll be asked to provide them before it can run. Since this is a local server, you set these in your own MCP client configuration and they stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configComSpec
configDEFAULT_NULL
configDISCUSSION_ID
🔐 secretDOWNLOAD_TOKEN_SECRET
configDOWNLOAD_TOKEN_TTL
configGITLAB_ALLOWED_PROJECT_IDS
configGITLAB_API_URLapi-url - GitLab API URL (replaces )
configGITLAB_COMMIT_FILES_PER_PAGE
configGITLAB_GRAPHQL_URL
configGITLAB_OAUTH_CLIENT_IDLocal OAuth: GITLAB_USE_OAUTH=true, , GITLAB_OAUTH_REDIRECT_URI, GITLAB_API_URL
🔐 secretGITLAB_OAUTH_CLIENT_SECRET
configGITLAB_OAUTH_REDIRECT_URIis for local OAuth (GITLAB_USE_OAUTH) only. It does
configGITLAB_OAUTH_TOKEN_PATH
configGITLAB_OAUTH_TOKEN_SCRIPT
configGITLAB_OAUTH_TOKEN_SCRIPT_TIMEOUT_SECONDS
configGITLAB_PROJECT_ID
configGITLAB_READ_ONLY_MODEread-only=true - Enable read-only mode (replaces , deprecated — prefer --permission-mode=readonly)
🔐 secretGITLAB_TOKEN
configISSUE_IID
configLOG_FORMAT
configLOG_LEVEL
configMAX_REQUESTS_PER_MINUTERemote multi-user HTTP: STREAMABLE_HTTP=true, REMOTE_AUTHORIZATION=true (or GITLAB_MCP_OAUTH=true), MCP_TRUST_PROXY=true (behind a reverse proxy), =300, MCP_SERVER_URL or MCP_ALLOWED_HOSTS, HOST, PORT
configMAX_SESSIONSCapacity limit: Server accepts up to concurrent sessions (default 1000)
configMCP_DANGEROUSLY_ALLOW_INSECURE_ISSUER_URLNo Set true for local HTTP dev only
configMCP_SERVER_NAMEMultiple side-by-side deployments: set a distinct per instance (e.g. gitlab-selfhosted-readonly) so clients, logs, and telemetry can tell them apart
configNOTE_ID
configOAUTH_REGISTER_RATE_LIMIT_PER_HOURDCR rate limiting: POST /register is limited to
configPROJECT_ID
configSESSION_TIMEOUT_SECONDSSession timeout: Auth tokens expire after (default 1 hour) of inactivity. After timeout, the client must send auth headers again. The transport session remains active.
configWORKSPACE_ROOT
configSTAR_HISTORY_REPO
configSTAR_HISTORY_OUT
🔐 secretGH_TOKEN
🔐 secretGITHUB_TOKEN
// full audit trail
The full breakdown of what we checked, the deductions that landed, the network hosts, the dependency advisories, and concrete fix guidance is available to verified publishers.
// improvement guidance — verified publishers only
We have 7 concrete improvements 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 Verified](https://m8ven.ai/badge/mcp/zereight-gitlab-mcp-rq4abf?variant=verified)](https://m8ven.ai/mcp/zereight-gitlab-mcp-rq4abf)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 926d42c8780cb9ec0cf3b5e187575bc3db205ff0
code hash: be8b888c33c05b460231dcfd83639107eea18cc3d7b29bfa84df2efbc6fc543e
verified: 8/13/2026, 9:39:37 PM
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