io.github.ozanmutlu/gitlab-docs
NPM · GITLAB-DOCS-MCP
Search and browse 2,900+ official GitLab documentation pages via MCP
Available components
Last scanned (20 hours ago)
Scores higher than 93% of npm servers
Category Code Search and Documentation
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 59 of 163 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to ozanmutlu/Gitlab-Docs-MCP). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 1469 tokens (~14/item across 104 items; 3 tools + 101 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +11
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.73 functional
- 2 Nov 26 −15
- Tool safety: pass → unverified ▼ security
- Malware scan: pass → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Package version: 1.1.19 → 1.1.20 functional
- 28 Oct 26 +1
- Stability: 0.97 → pass security
- 27 Oct 26 +14
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.97 functional
- 26 Oct 26 −15
- Tool safety: pass → unverified ▼ security
- Malware scan: pass → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Package version: 1.1.18 → 1.1.19 functional
- 21 Oct 26 +1
- Stability: 0.97 → pass security
- 20 Oct 26 −1
- Stability: pass → 0.97 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed npm/gitlab-docs-mcp@1.1.20
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | ozanmutlu/Gitlab-Docs-MCP |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/ozanmutlu/Gitlab-Docs-MCP/.github/workflows/release.yml@refs/heads/master |
| Rekor log index | 3638104047 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:589e09a4fcdaeeb8385ae12f14660fbd2f2f6151263d0c4abc34500e83c73ce3ffc7c246027e05cae1b01e45ce602d66502c83dd5ecf8d830bcca38d5 |
Background: How many MCP packages publish verified provenance →
Dependencies 163 packages
| Packages resolved | 163 |
|---|---|
| Stale | 59 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
getDocPage Get Documentation Page ~65
Retrieve the full content of a GitLab documentation page by path. Returns complete configuration examples, YAML snippets, CLI commands, API request/response samples, and step-by-step setup guides. Use after searchGitLabDocs to get detailed page content.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
No output schema declared.
No examples provided.
listDocSections List Documentation Sections ~36
Browse GitLab documentation structure including sections for CI/CD, API, administration, user guides, development, security, operations, and integrations.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
searchGitLabDocs Search GitLab Documentation ~148
Search 2,900+ official GitLab documentation pages. Covers .gitlab-ci.yml syntax, CI/CD pipelines, runners, jobs, variables, artifacts, caching, environments, deployments, merge requests, approvals, code review, GitLab API (REST and GraphQL), container registry, package registry, Kubernetes agent, security scanning (SAST, DAST, dependency scanning, secret detection), GitLab Pages, authentication (SSO, SAML, LDAP, OAuth), permissions, admin settings, Gitaly, Sidekiq, Geo replication, and backup/restore.
| Name | Type | Req | Description |
|---|---|---|---|
| maxResults | integer | – | – |
| query | string | yes | – |
| section | string | – | – |
No output schema declared.
No examples provided.
How do I install the io.github.ozanmutlu/gitlab-docs MCP server?
io.github.ozanmutlu/gitlab-docs runs locally as an npm package, launched with npx -y gitlab-docs-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · gitlab-docs-mcp
claude mcp add ozanmutlu-gitlab-docs -- npx -y gitlab-docs-mcp
What is the io.github.ozanmutlu/gitlab-docs MCP server?
io.github.ozanmutlu/gitlab-docs is an MCP server listed in the public MCP registry as io.github.ozanmutlu/gitlab-docs. Search and browse 2,900+ official GitLab documentation pages via MCP. This page covers its npm package (gitlab-docs-mcp).
Is the io.github.ozanmutlu/gitlab-docs MCP server safe to use?
io.github.ozanmutlu/gitlab-docs scores 89 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.ozanmutlu/gitlab-docs MCP server expose?
io.github.ozanmutlu/gitlab-docs exposes 3 tools: searchGitLabDocs, getDocPage, listDocSections. Their descriptions and schemas cost roughly 249 tokens of context every time the server is loaded.
Is the io.github.ozanmutlu/gitlab-docs MCP server still maintained?
io.github.ozanmutlu/gitlab-docs is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.ozanmutlu/gitlab-docs MCP server under?
io.github.ozanmutlu/gitlab-docs declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.