GitLab Documentation MCP Server
OCI · DOCKER.IO/NUNOLIMA/GITLAB-DOCS-MCP:18.7
Searchable access to GitLab documentation from multiple repositories with full-text search.
Available components
Last scanned (13 hours ago)
Scores higher than 6% of OCI 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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: we could not find this package in its registry.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: we could not find this package in its registry.Unverified
Provenance & Transparency26
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: the declared version isn't published, so its provenance can't be verified. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Maintenance history not yet determined.Unverified
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
- Schema quality not yet verified: this package could not be installed in a clean environment, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: this package could not be installed in a clean environment, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: this package could not be installed in a clean environment, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: this package could not be installed in a clean environment, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: this package could not be installed in a clean environment, so we never saw its MCP handshake.Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (4)
- Source repository
- Provenance
- License
- Security disclosure
Checks we could not complete (10)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain Security (scores 0 for this)No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
- Known CVEs in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: we could not find this package in its registry.
- Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
- Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: we could not find this package in its registry.
- Maintenance in Provenance & TransparencyMaintenance history not yet determined.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema quality not yet verified: this package could not be installed in a clean environment, so we have no schema to assess.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: this package could not be installed in a clean environment, so we have no schema to compare.
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: this package could not be installed in a clean environment, so we have no tool definitions to assess.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: this package could not be installed in a clean environment, so we have no tool text to scan.
- Capabilities in Capabilities (scores 0 for this)Protocol version not yet verified: this package could not be installed in a clean environment, so we never saw its MCP handshake.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 21 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 20 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 16 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 15 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 9 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 8 Sept 26 0
- Security disclosure: fail → unverified ▼ 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 5 Nov 2026 · Analysed oci/docker.io/nunolima/gitlab-docs-mcp:18.7
Provenance Version not published
The package exists but this version is not published, so there is no artifact to attest.
| Result | Version not published |
|---|---|
| Ecosystem | oci |
| Reason | No trust root |
Background: How many MCP packages publish verified provenance →
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 →
Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.
How do I install the GitLab Documentation MCP Server server?
GitLab Documentation MCP Server runs locally as a container image, launched with docker run --rm -i docker.io/nunolima/gitlab-docs-mcp:18.7. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · docker.io/nunolima/gitlab-docs-mcp:18.7
claude mcp add nunolima-gitlab-docs-mcp -- docker run --rm -i docker.io/nunolima/gitlab-docs-mcp:18.7
What is the GitLab Documentation MCP Server server?
GitLab Documentation MCP Server is listed in the public MCP registry as io.github.nunolima/gitlab-docs-mcp. Searchable access to GitLab documentation from multiple repositories with full-text search. This page covers its container image (docker.io/nunolima/gitlab-docs-mcp:18.7).
Is the GitLab Documentation MCP Server server safe to use?
GitLab Documentation MCP Server scores 5 out of 100 on VerifyMCP. 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.
Is the GitLab Documentation MCP Server server still maintained?
GitLab Documentation MCP Server is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the GitLab Documentation MCP Server server?
VerifyMCP ran 4 checks on GitLab Documentation MCP Server, covering Source repository, Provenance, License and Security disclosure. 10 items could not be completed, a gap on our side rather than a finding about GitLab Documentation MCP Server: Malware scan, Known CVEs, Install scripts, Dependency health and 6 more. 6 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.