# io.github.CloudCorpRecords/repocollab (oci · ghcr.io/cloudcorprecords/repocollab) GitLab projects, branches, files, issues and merge requests via the GitLab REST API. - Trust score: 40/100 (low) - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-11-05 ## Components - npm · `@reneturcios/repocollab`: 63/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-repocollab/reneturcios-repocollab.md), [page](https://verifymcp.io/servers/cloudcorprecords-repocollab/reneturcios-repocollab) - oci · `ghcr.io/cloudcorprecords/repocollab`: 40/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-repocollab/ghcr-io-cloudcorprecords-repocollab.md), [page](https://verifymcp.io/servers/cloudcorprecords-repocollab/ghcr-io-cloudcorprecords-repocollab) ## Channel facts - Registry: `oci` - Package: `ghcr.io/cloudcorprecords/repocollab` - Version: `0.1.0` - Transport: `stdio` ## Trust breakdown 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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-11-05. - **Supply Chain Security**: 0/100 - 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 could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read. - Install-script risk not yet assessed. - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read. - **Provenance & Transparency**: 45/100 - Source repository is publicly reachable at the declared URL. - Provenance check failed: no build-provenance attestation is published. - Clear OSI-approved license (MIT). - Actively maintained (last published 3 days ago). - Disclosure check failed: no security disclosure policy was found in the source repository. - **Schema Quality & AI Usability**: 73/100 - AI-judged instruction clarity (good). - Tool/resource definitions use about 987 tokens (~82/item across 12 items; 12 tools + 0 resources), lean. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 10/100 - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 100% of tool parameters carry a description. - **Tool Safety**: 75/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "create_merge_request" implies "merge" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. **Unverified: 1 category.** A category scored 0 because we could not verify it: 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. ## Install ### How do I install the io.github.CloudCorpRecords/repocollab MCP server? io.github.CloudCorpRecords/repocollab runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/repocollab:0.1.0 mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation. ### Claude ```bash claude mcp add cloudcorprecords-repocollab -- docker run --rm -i ghcr.io/cloudcorprecords/repocollab:0.1.0 mcp ``` ### Cursor ```json { "mcpServers": { "cloudcorprecords-repocollab": { "command": "docker", "args": [ "run", "--rm", "-i", "ghcr.io/cloudcorprecords/repocollab:0.1.0", "mcp" ] } } } ``` ### VS Code ```json { "servers": { "cloudcorprecords-repocollab": { "command": "docker", "args": [ "run", "--rm", "-i", "ghcr.io/cloudcorprecords/repocollab:0.1.0", "mcp" ] } } } ``` ### Codex ```bash codex mcp add cloudcorprecords-repocollab -- docker run --rm -i ghcr.io/cloudcorprecords/repocollab:0.1.0 mcp ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "cloudcorprecords-repocollab": { "type": "local", "command": [ "docker", "run", "--rm", "-i", "ghcr.io/cloudcorprecords/repocollab:0.1.0", "mcp" ], "enabled": true } } } ``` ### Hermes ```yaml mcp_servers: cloudcorprecords-repocollab: command: "docker" args: ["run", "--rm", "-i", "ghcr.io/cloudcorprecords/repocollab:0.1.0", "mcp"] ``` ### Netclaw ```json { "McpServers": { "cloudcorprecords-repocollab": { "Transport": "stdio", "Command": "docker", "Arguments": [ "run", "--rm", "-i", "ghcr.io/cloudcorprecords/repocollab:0.1.0", "mcp" ] } } } ``` ### Other ```json { "mcpServers": { "cloudcorprecords-repocollab": { "command": "docker", "args": [ "run", "--rm", "-i", "ghcr.io/cloudcorprecords/repocollab:0.1.0", "mcp" ] } } } ``` ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-11-04 (score 40, +1) No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-11-02 (score 39) First indexed and scored. ## MCP tools (12) ### `search_repositories` (~42 tokens) Search for GitLab projects by name, path, or description. Input parameters: - `search` (string, required): The search query string matched against project name, path, and description. ### `create_repository` (~63 tokens) Create a new GitLab project. Input parameters: - `description` (string): Optional description of the new project. - `name` (string, required): The name of the new GitLab project. - `visibility` (string): Optional project visibility level, such as private, internal, or public. ### `fork_repository` (~63 tokens) Fork a GitLab project, optionally into a namespace. Input parameters: - `namespace` (string): Optional target namespace (user or group path) to fork the project into. - `project_id` (string, required): The GitLab project identifier: a numeric ID or URL-encoded project path. ### `create_branch` (~82 tokens) Create a new branch in a GitLab project from a reference. Input parameters: - `branch` (string, required): The name of the new branch to create. - `project_id` (string, required): The GitLab project identifier: a numeric ID or URL-encoded project path. - `ref` (string): Optional source reference (branch, tag, or commit) to create the branch from. ### `get_file_contents` (~85 tokens) Get the contents of a file in a GitLab project at a reference. Input parameters: - `file_path` (string, required): The path of the file within the repository. - `project_id` (string, required): The GitLab project identifier: a numeric ID or URL-encoded project path. - `ref` (string): Optional reference (branch, tag, or commit) to read the file at. ### `create_or_update_file` (~138 tokens) Create a file in a GitLab project, or update it if it already exists. Input parameters: - `branch` (string, required): The branch to commit the file change to. - `commit_message` (string, required): The commit message for the file creation or update. - `content` (string, required): The full text content to write to the file. - `file_path` (string, required): The path of the file within the repository to create or update. - `previous_path` (string): Optional previous path of the file when renaming or moving it. - `project_id` (string, required): The GitLab project identifier: a numeric ID or URL-encoded project path. ### `create_issue` (~86 tokens) Create a new issue in a GitLab project. Input parameters: - `description` (string): Optional body text describing the issue. - `labels` (string): Optional comma-separated list of label names to apply to the issue. - `project_id` (string, required): The GitLab project identifier: a numeric ID or URL-encoded project path. - `title` (string, required): The title of the new issue. ### `list_issues` (~92 tokens) List issues in a GitLab project, optionally filtered by state. Input parameters: - `page` (number): Optional page number of results to return. - `per_page` (number): Optional number of results to return per page. - `project_id` (string, required): The GitLab project identifier: a numeric ID or URL-encoded project path. - `state` (string): Optional issue state filter, such as opened or closed. ### `get_issue` (~67 tokens) Get a single issue in a GitLab project by its IID. Input parameters: - `issue_iid` (number, required): The project-scoped internal ID (IID) of the issue to retrieve. - `project_id` (string, required): The GitLab project identifier: a numeric ID or URL-encoded project path. ### `create_merge_request` (~101 tokens) Create a new merge request in a GitLab project. Input parameters: - `description` (string): Optional body text describing the merge request. - `project_id` (string, required): The GitLab project identifier: a numeric ID or URL-encoded project path. - `source_branch` (string, required): The branch containing the changes to merge. - `target_branch` (string, required): The branch to merge the changes into. - `title` (string, required): The title of the new merge request. ### `list_merge_requests` (~97 tokens) List merge requests in a GitLab project, optionally filtered by state. Input parameters: - `page` (number): Optional page number of results to return. - `per_page` (number): Optional number of results to return per page. - `project_id` (string, required): The GitLab project identifier: a numeric ID or URL-encoded project path. - `state` (string): Optional merge request state filter, such as opened, closed, or merged. ### `get_merge_request` (~71 tokens) Get a single merge request in a GitLab project by its IID. Input parameters: - `merge_request_iid` (number, required): The project-scoped internal ID (IID) of the merge request to retrieve. - `project_id` (string, required): The GitLab project identifier: a numeric ID or URL-encoded project path. ## Diagnostics Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-repocollab/ghcr-io-cloudcorprecords-repocollab#diagnostics ## Score history - 2026-11-05: 40 - 2026-11-04: 40 - 2026-11-03: 39 - 2026-11-02: 39 ## Common questions ### What is the io.github.CloudCorpRecords/repocollab MCP server? io.github.CloudCorpRecords/repocollab is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/repocollab. GitLab projects, branches, files, issues and merge requests via the GitLab REST API. This page covers its container image (ghcr.io/cloudcorprecords/repocollab). ### Is the io.github.CloudCorpRecords/repocollab MCP server safe to use? io.github.CloudCorpRecords/repocollab scores 40 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. ### What tools does the io.github.CloudCorpRecords/repocollab MCP server expose? io.github.CloudCorpRecords/repocollab exposes 12 tools: search_repositories, create_repository, fork_repository, create_branch, get_file_contents, and 7 more. Their descriptions and schemas cost roughly 987 tokens of context every time the server is loaded. ### Is the io.github.CloudCorpRecords/repocollab MCP server still maintained? io.github.CloudCorpRecords/repocollab 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 licence is the io.github.CloudCorpRecords/repocollab MCP server under? io.github.CloudCorpRecords/repocollab declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls. ### What did VerifyMCP test on the io.github.CloudCorpRecords/repocollab MCP server? VerifyMCP ran 12 checks on io.github.CloudCorpRecords/repocollab, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about io.github.CloudCorpRecords/repocollab: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 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. ## Links - GitHub Container Registry: https://ghcr.io/cloudcorprecords/repocollab - Repository: https://github.com/CloudCorpRecords/repocollab - Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-repocollab/ghcr-io-cloudcorprecords-repocollab.xml - Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-repocollab/ghcr-io-cloudcorprecords-repocollab/changelog.json - Trust report (JSON): https://verifymcp.io/servers/cloudcorprecords-repocollab/ghcr-io-cloudcorprecords-repocollab.json - HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-repocollab/ghcr-io-cloudcorprecords-repocollab