io.github.CloudCorpRecords/repoport
NPM · @RENETURCIOS/REPOPORT · 2 COMPONENTS
Local git operations over MCP: status, diff, log, branches and commits.
Available components
Last scanned (2 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 8 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 632 tokens (~52/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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- 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.
- 28 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 27 Oct 26 49
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/repoport@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 →
git_add ~46
Stage files for the next commit.
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | yes | Files to stage, as paths relative to the repository. |
| repo_path | string | yes | Path of the local git repository. |
No output schema declared.
No examples provided.
git_branch ~80
List branches, optionally filtered by containment.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Path of the local git repository. |
No output schema declared.
No examples provided.
git_checkout ~44
Switch to an existing branch.
| Name | Type | Req | Description |
|---|---|---|---|
| branch_name | string | yes | Name of the existing branch to switch to. |
| repo_path | string | yes | Path of the local git repository. |
No output schema declared.
No examples provided.
git_commit ~42
Commit staged changes with a message.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | Commit message for the staged changes. |
| repo_path | string | yes | Path of the local git repository. |
No output schema declared.
No examples provided.
git_create_branch ~64
Create a new branch, optionally from a base branch.
| Name | Type | Req | Description |
|---|---|---|---|
| base_branch | string | – | Optional branch to create the new branch from. |
| branch_name | string | yes | Name of the branch to create. |
| repo_path | string | yes | Path of the local git repository. |
No output schema declared.
No examples provided.
git_diff ~65
Show changes between the working tree and a target revision.
| Name | Type | Req | Description |
|---|---|---|---|
| context_lines | integer | – | Number of context lines to include around each change. |
| repo_path | string | yes | Path of the local git repository. |
| target | string | yes | Target revision to compare the working tree against. |
No output schema declared.
No examples provided.
git_diff_staged ~49
Show changes staged for the next commit.
| Name | Type | Req | Description |
|---|---|---|---|
| context_lines | integer | – | Number of context lines to include around each change. |
| repo_path | string | yes | Path of the local git repository. |
No output schema declared.
No examples provided.
git_diff_unstaged ~51
Show unstaged changes in the working tree.
| Name | Type | Req | Description |
|---|---|---|---|
| context_lines | integer | – | Number of context lines to include around each change. |
| repo_path | string | yes | Path of the local git repository. |
No output schema declared.
No examples provided.
git_log ~78
List recent commits, optionally within a timestamp window.
| Name | Type | Req | Description |
|---|---|---|---|
| end_timestamp | string | – | Only return commits at or before this timestamp. |
| max_count | integer | – | Maximum number of commits to return. |
| repo_path | string | yes | Path of the local git repository. |
| start_timestamp | string | – | Only return commits at or after this timestamp. |
No output schema declared.
No examples provided.
git_reset ~33
Unstage all staged changes, keeping the working tree.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_path | string | yes | Path of the local git repository. |
No output schema declared.
No examples provided.
git_show ~49
Show a commit or other revision object.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_path | string | yes | Path of the local git repository. |
| revision | string | yes | Revision to show, such as a commit hash or a tag. |
No output schema declared.
No examples provided.
git_status ~31
Show the working tree status of a repository.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_path | string | yes | Path of the local git repository. |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/repoport MCP server?
io.github.CloudCorpRecords/repoport runs locally as an npm package, launched with npx -y @reneturcios/repoport. 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/repoport
claude mcp add cloudcorprecords-repoport -- npx -y @reneturcios/repoport
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 npm package (@reneturcios/repoport).
Is the io.github.CloudCorpRecords/repoport MCP server safe to use?
io.github.CloudCorpRecords/repoport scores 64 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/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.