gitlab-mcp@13.3.0
CAUTION· startup onlyPublisher claims: "Advanced GitLab MCP server" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Startup only; authenticated tool behavior not tested.- Tested
- server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
- Not tested
- the tool list (the server exited before answering) · what the tools do when called with real credentials
What this means for the label: Caution here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
GITLAB_AUTH_COOKIE_PATHGITLAB_TOKENNODE_TLS_REJECT_UNAUTHORIZEDOAUTH_CLIENT_IDOAUTH_CLIENT_SECRETOAUTH_DEVICE_POLL_INTERVALOAUTH_DEVICE_TIMEOUTOAUTH_ENABLEDOAUTH_ISSUEROAUTH_REFRESH_TOKEN_TTLOAUTH_SCOPESOAUTH_SESSION_SECRETOAUTH_TOKEN_TTLUSE_ACCESS_TOKENSUSE_CI_TOKENSUSE_WEBHOOKSConfiguration, not credentials: DASHBOARD_ENABLED, DEFAULT_NULL, GITLAB_ALLOWED_PROJECT_IDS, GITLAB_ALLOWED_TOOLS_REGEX, GITLAB_API_BODY_TIMEOUT_MS, GITLAB_API_CONNECT_TIMEOUT_MS, GITLAB_API_HEADERS_TIMEOUT_MS, GITLAB_API_RETRY_BASE_DELAY_MS, GITLAB_API_RETRY_ENABLED, GITLAB_API_RETRY_MAX_ATTEMPTS, GITLAB_API_RETRY_MAX_DELAY_MS, GITLAB_API_URL, GITLAB_CA_CERT_PATH, GITLAB_CROSS_REFS, GITLAB_DEFAULT_NAMESPACE, GITLAB_DEFAULT_PROJECT, GITLAB_DENIED_ACTIONS, GITLAB_DENIED_TOOLS_REGEX, GITLAB_FAILURE_THRESHOLD, GITLAB_HEALTH_CHECK_INTERVAL_MS, GITLAB_HTTP_KEEPALIVE_TIMEOUT_MS, GITLAB_INIT_TIMEOUT_MS, GITLAB_INSTANCE_CACHE_MAX, GITLAB_INSTANCE_TTL_MS- Where it talks to
- no vendor host named in the codeAlso sw.foundation — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- the tool list (the server exited before answering) · what the tools do when called with real credentials
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names sw.foundation as well as its own vendor. The guard injects GITLAB_AUTH_COOKIE_PATH, GITLAB_TOKEN, NODE_TLS_REJECT_UNAUTHORIZED, OAUTH_CLIENT_ID, OAUTH_CLIENT_SECRET, OAUTH_DEVICE_POLL_INTERVAL, OAUTH_DEVICE_TIMEOUT, OAUTH_ENABLED, OAUTH_ISSUER, OAUTH_REFRESH_TOKEN_TTL, OAUTH_SCOPES, OAUTH_SESSION_SECRET, OAUTH_TOKEN_TTL, USE_ACCESS_TOKENS, USE_CI_TOKENS, USE_WEBHOOKS only into requests to the host you bind (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; startup only; authenticated tool behavior not tested) on 2026-11-11 and scored it 79/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: README links to an external installer; Access to sensitive file paths; Access to sensitive file paths. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 44 s · 2 scenarios · 0 deviationsStatic findings
https://github.com/structured-world/gitlab-mcp/releases/latest/download/gitlab-mcp-codex.zipFix: Pin versions and sources; vendor anything fetched at install time."dev:stdio": "node --env-file=.env.test -r source-map-support/register -r ts-node/register --experimental-specifier-resolution=node --experimental-print-required-tla --watch src/main.ts stdio",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."dev:sse": "node --env-file=.env.test -r source-map-support/register -r ts-node/register --experimental-specifier-resolution=node --experimental-print-required-tla --watch src/main.ts sse",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.console.log(JSON.stringify(output, null, 2));Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why."list-tools:dev": "node --env-file=.env.test -r source-map-support/register -r ts-node/register --experimental-specifier-resolution=node src/cli/list-tools.ts",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.console.log(JSON.stringify(output, null, 2));Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.console.log(JSON.stringify(output, null, 2));Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why."dev": "node --env-file=.env.test -r source-map-support/register -r ts-node/register --experimental-specifier-resolution=node --experimental-print-required-tla --watch src/main.ts",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."Run 'npx @structured-world/gitlab-mcp setup' for interactive configuration, " +Fix: Pin versions and sources; vendor anything fetched at install time.│ npx @structured-world/gitlab-mcp setup │Fix: Pin versions and sources; vendor anything fetched at install time.console.log(JSON.stringify(output, null, 2));Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.console.log(JSON.stringify(output, null, 2));Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.… - Unit test coverage\\n yarn test:integration - Integration tests (needs .env.test)\\n yarn test:all - Full suite (unit + integration)\\n yarn tes…Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for @structured-world/gitlab-mcp@13.3.0 as of 4d ago. This is the package itself, not its dependencies.
What would make this Verified
1 point to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim structured-world: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- README links to an external installer≈ +4 on the totalPin versions and sources; vendor anything fetched at install time.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- File type combined with upload action≈ +2 on the totalRemove the call, or declare the host in frontmatter and explain in the README what is sent and why.
- npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.