# io.github.CloudCorpRecords/repoport (oci · ghcr.io/cloudcorprecords/repoport)

Local git operations over MCP: status, diff, log, branches and commits.

- Trust score: 44/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@reneturcios/repoport`: 64/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-repoport/reneturcios-repoport.md), [page](https://verifymcp.io/servers/cloudcorprecords-repoport/reneturcios-repoport)
- oci · `ghcr.io/cloudcorprecords/repoport`: 44/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-repoport/ghcr-io-cloudcorprecords-repoport.md), [page](https://verifymcp.io/servers/cloudcorprecords-repoport/ghcr-io-cloudcorprecords-repoport)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/cloudcorprecords/repoport`
- 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 8 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 632 tokens (~52/item across 12 items; 12 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 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**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - 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/repoport MCP server?

io.github.CloudCorpRecords/repoport runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/repoport:0.1.0. 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-repoport -- docker run --rm -i ghcr.io/cloudcorprecords/repoport:0.1.0
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-repoport": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/repoport:0.1.0"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-repoport": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/repoport:0.1.0"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-repoport -- docker run --rm -i ghcr.io/cloudcorprecords/repoport:0.1.0
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-repoport": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/repoport:0.1.0"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-repoport:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/cloudcorprecords/repoport:0.1.0"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-repoport": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/repoport:0.1.0"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-repoport": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/repoport:0.1.0"
      ]
    }
  }
}
```

## 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-05 (score 44, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 43, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 42, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 41, +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-10-27 (score 40)

First indexed and scored.

## MCP tools (12)

### `git_status` (~31 tokens)

Show the working tree status of a repository.

Input parameters:

- `repo_path` (string, required): Path of the local git repository.

### `git_diff_unstaged` (~51 tokens)

Show unstaged changes in the working tree.

Input parameters:

- `context_lines` (integer): Number of context lines to include around each change.
- `repo_path` (string, required): Path of the local git repository.

### `git_diff_staged` (~49 tokens)

Show changes staged for the next commit.

Input parameters:

- `context_lines` (integer): Number of context lines to include around each change.
- `repo_path` (string, required): Path of the local git repository.

### `git_diff` (~65 tokens)

Show changes between the working tree and a target revision.

Input parameters:

- `context_lines` (integer): Number of context lines to include around each change.
- `repo_path` (string, required): Path of the local git repository.
- `target` (string, required): Target revision to compare the working tree against.

### `git_add` (~46 tokens)

Stage files for the next commit.

Input parameters:

- `files` (array, required): Files to stage, as paths relative to the repository.
- `repo_path` (string, required): Path of the local git repository.

### `git_reset` (~33 tokens)

Unstage all staged changes, keeping the working tree.

Input parameters:

- `repo_path` (string, required): Path of the local git repository.

### `git_commit` (~42 tokens)

Commit staged changes with a message.

Input parameters:

- `message` (string, required): Commit message for the staged changes.
- `repo_path` (string, required): Path of the local git repository.

### `git_log` (~78 tokens)

List recent commits, optionally within a timestamp window.

Input parameters:

- `end_timestamp` (string): Only return commits at or before this timestamp.
- `max_count` (integer): Maximum number of commits to return.
- `repo_path` (string, required): Path of the local git repository.
- `start_timestamp` (string): Only return commits at or after this timestamp.

### `git_show` (~49 tokens)

Show a commit or other revision object.

Input parameters:

- `repo_path` (string, required): Path of the local git repository.
- `revision` (string, required): Revision to show, such as a commit hash or a tag.

### `git_create_branch` (~64 tokens)

Create a new branch, optionally from a base branch.

Input parameters:

- `base_branch` (string): Optional branch to create the new branch from.
- `branch_name` (string, required): Name of the branch to create.
- `repo_path` (string, required): Path of the local git repository.

### `git_checkout` (~44 tokens)

Switch to an existing branch.

Input parameters:

- `branch_name` (string, required): Name of the existing branch to switch to.
- `repo_path` (string, required): Path of the local git repository.

### `git_branch` (~80 tokens)

List branches, optionally filtered by containment.

Input parameters:

- `branch_type` (string): Which branches to list: local, remote, or all.
- `contains` (string): Only list branches that contain this commit.
- `not_contains` (string): Only list branches that do not contain this commit.
- `repo_path` (string, required): Path of the local git repository.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-repoport/ghcr-io-cloudcorprecords-repoport#diagnostics

## Score history

- 2026-11-05: 44
- 2026-11-04: 43
- 2026-11-03: 43
- 2026-11-02: 42
- 2026-11-01: 42
- 2026-10-31: 41
- 2026-10-30: 41
- 2026-10-29: 41
- 2026-10-28: 40
- 2026-10-27: 40

## Common questions

### What is the io.github.CloudCorpRecords/repoport MCP server?

io.github.CloudCorpRecords/repoport is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/repoport. Local git operations over MCP: status, diff, log, branches and commits. This page covers its container image (ghcr.io/cloudcorprecords/repoport).

### Is the io.github.CloudCorpRecords/repoport MCP server safe to use?

io.github.CloudCorpRecords/repoport scores 44 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/repoport MCP server expose?

io.github.CloudCorpRecords/repoport exposes 12 tools: git_status, git_diff_unstaged, git_diff_staged, git_diff, git_add, and 7 more. Their descriptions and schemas cost roughly 632 tokens of context every time the server is loaded.

### Is the io.github.CloudCorpRecords/repoport MCP server still maintained?

io.github.CloudCorpRecords/repoport 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/repoport MCP server under?

io.github.CloudCorpRecords/repoport declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- GitHub Container Registry: https://ghcr.io/cloudcorprecords/repoport
- Repository: https://github.com/CloudCorpRecords/repoport
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-repoport/ghcr-io-cloudcorprecords-repoport.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-repoport/ghcr-io-cloudcorprecords-repoport.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-repoport/ghcr-io-cloudcorprecords-repoport