io.github.CloudCorpRecords/repocollab
NPM · @RENETURCIOS/REPOCOLLAB · 2 COMPONENTS
GitLab projects, branches, files, issues and merge requests via the GitLab REST API.
Available components
Last scanned (4 hours ago)
Scores higher than 31% of npm servers
Category Version Control
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 987 tokens (~82/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 12 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
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.
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.
- 2 Nov 26 63
First indexed and scored.
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 npm/@reneturcios/repocollab@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
create_branch ~82
Create a new branch in a GitLab project from a reference.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | yes | The name of the new branch to create. |
| project_id | string | yes | 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. |
No output schema declared.
No examples provided.
create_issue ~86
Create a new issue in a GitLab project.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The GitLab project identifier: a numeric ID or URL-encoded project path. |
| title | string | yes | The title of the new issue. |
No output schema declared.
No examples provided.
create_merge_request ~101
Create a new merge request in a GitLab project.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Optional body text describing the merge request. |
| project_id | string | yes | The GitLab project identifier: a numeric ID or URL-encoded project path. |
| source_branch | string | yes | The branch containing the changes to merge. |
| target_branch | string | yes | The branch to merge the changes into. |
| title | string | yes | The title of the new merge request. |
No output schema declared.
No examples provided.
create_or_update_file ~138
Create a file in a GitLab project, or update it if it already exists.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | yes | The branch to commit the file change to. |
| commit_message | string | yes | The commit message for the file creation or update. |
| content | string | yes | The full text content to write to the file. |
| file_path | string | yes | 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 | yes | The GitLab project identifier: a numeric ID or URL-encoded project path. |
No output schema declared.
No examples provided.
create_repository ~63
Create a new GitLab project.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Optional description of the new project. |
| name | string | yes | The name of the new GitLab project. |
| visibility | string | – | Optional project visibility level, such as private, internal, or public. |
No output schema declared.
No examples provided.
fork_repository ~63
Fork a GitLab project, optionally into a namespace.
| Name | Type | Req | Description |
|---|---|---|---|
| namespace | string | – | Optional target namespace (user or group path) to fork the project into. |
| project_id | string | yes | The GitLab project identifier: a numeric ID or URL-encoded project path. |
No output schema declared.
No examples provided.
get_file_contents ~85
Get the contents of a file in a GitLab project at a reference.
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | The path of the file within the repository. |
| project_id | string | yes | 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. |
No output schema declared.
No examples provided.
get_issue ~67
Get a single issue in a GitLab project by its IID.
| Name | Type | Req | Description |
|---|---|---|---|
| issue_iid | number | yes | The project-scoped internal ID (IID) of the issue to retrieve. |
| project_id | string | yes | The GitLab project identifier: a numeric ID or URL-encoded project path. |
No output schema declared.
No examples provided.
get_merge_request ~71
Get a single merge request in a GitLab project by its IID.
| Name | Type | Req | Description |
|---|---|---|---|
| merge_request_iid | number | yes | The project-scoped internal ID (IID) of the merge request to retrieve. |
| project_id | string | yes | The GitLab project identifier: a numeric ID or URL-encoded project path. |
No output schema declared.
No examples provided.
list_issues ~92
List issues in a GitLab project, optionally filtered by state.
| Name | Type | Req | Description |
|---|---|---|---|
| page | number | – | Optional page number of results to return. |
| per_page | number | – | Optional number of results to return per page. |
| project_id | string | yes | The GitLab project identifier: a numeric ID or URL-encoded project path. |
| state | string | – | Optional issue state filter, such as opened or closed. |
No output schema declared.
No examples provided.
list_merge_requests ~97
List merge requests in a GitLab project, optionally filtered by state.
| Name | Type | Req | Description |
|---|---|---|---|
| page | number | – | Optional page number of results to return. |
| per_page | number | – | Optional number of results to return per page. |
| project_id | string | yes | 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. |
No output schema declared.
No examples provided.
search_repositories ~42
Search for GitLab projects by name, path, or description.
| Name | Type | Req | Description |
|---|---|---|---|
| search | string | yes | The search query string matched against project name, path, and description. |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/repocollab MCP server?
io.github.CloudCorpRecords/repocollab runs locally as an npm package, launched with npx -y @reneturcios/repocollab. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @reneturcios/repocollab
claude mcp add cloudcorprecords-repocollab -- npx -y @reneturcios/repocollab
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 npm package (@reneturcios/repocollab).
Is the io.github.CloudCorpRecords/repocollab MCP server safe to use?
io.github.CloudCorpRecords/repocollab scores 63 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. 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.