io.github.CloudCorpRecords/codehost-remote
NPM · @RENETURCIOS/CODEHOST-REMOTE · 2 COMPONENTS
Forward GitHub tools to the hosted GitHub Copilot remote MCP endpoint.
Available components
Last scanned (2 hours ago)
Scores higher than 34% 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 Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1267 tokens (~90/item across 14 items; 14 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 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
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 64
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/codehost-remote@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 →
add_issue_comment ~77
Add a comment to an existing issue in a GitHub repository.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Text of the comment to add. |
| issue_number | number | yes | Number of the issue to comment on. |
| owner | string | yes | Owner of the repository (user or organization name). |
| repo | string | yes | Name of the repository. |
No output schema declared.
No examples provided.
create_branch ~92
Create a new branch in a repository, optionally from another branch.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | yes | Name of the new branch to create. |
| from_branch | string | – | Name of the existing branch to create the new branch from. If omitted, the repository's default branch is used. |
| owner | string | yes | Owner of the repository (user or organization name). |
| repo | string | yes | Name of the repository. |
No output schema declared.
No examples provided.
create_issue ~107
Create a new issue in a GitHub repository.
| Name | Type | Req | Description |
|---|---|---|---|
| assignees | array | – | List of user logins to assign to the new issue. |
| body | string | – | Body text of the new issue. |
| labels | array | – | List of label names to apply to the new issue. |
| owner | string | yes | Owner of the repository (user or organization name). |
| repo | string | yes | Name of the repository. |
| title | string | yes | Title of the new issue. |
No output schema declared.
No examples provided.
create_or_update_file ~139
Create or update a single file in a GitHub repository.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | yes | Branch on which to create or update the file. |
| content | string | yes | Contents of the file. |
| message | string | yes | Commit message for the file change. |
| owner | string | yes | Owner of the repository (user or organization name). |
| path | string | yes | Path where the file will be created or updated, relative to the repository root. |
| repo | string | yes | Name of the repository. |
| sha | string | – | SHA of the existing file being replaced. Required when updating an existing file; omit when creating a new file. |
No output schema declared.
No examples provided.
create_pull_request ~130
Create a new pull request in a GitHub repository.
| Name | Type | Req | Description |
|---|---|---|---|
| base | string | yes | Name of the branch to merge the changes into (the target branch). |
| body | string | – | Body text of the new pull request. |
| draft | boolean | – | Whether to create the pull request as a draft. |
| head | string | yes | Name of the branch containing the changes to merge (the source branch). |
| owner | string | yes | Owner of the repository (user or organization name). |
| repo | string | yes | Name of the repository. |
| title | string | yes | Title of the new pull request. |
No output schema declared.
No examples provided.
create_repository ~83
Create a new GitHub repository for the authenticated user.
| Name | Type | Req | Description |
|---|---|---|---|
| autoInit | boolean | – | Whether to initialize the new repository with a README file. |
| description | string | – | A short description of the new repository. |
| name | string | yes | Name for the new repository. |
| private | boolean | – | Whether the new repository is private (true) or public (false). |
No output schema declared.
No examples provided.
fork_repository ~50
Fork a GitHub repository into the authenticated user's account.
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | yes | Owner of the repository to fork (user or organization name). |
| repo | string | yes | Name of the repository to fork. |
No output schema declared.
No examples provided.
get_file_contents ~95
Get the contents of a file or directory from a GitHub repository.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | Branch to get the contents from. If omitted, the repository's default branch is used. |
| owner | string | yes | Owner of the repository (user or organization name). |
| path | string | yes | Path of the file or directory to retrieve, relative to the repository root. |
| repo | string | yes | Name of the repository. |
No output schema declared.
No examples provided.
get_issue ~62
Get the details of a specific issue in a GitHub repository.
| Name | Type | Req | Description |
|---|---|---|---|
| issue_number | number | yes | Number of the issue to retrieve. |
| owner | string | yes | Owner of the repository (user or organization name). |
| repo | string | yes | Name of the repository. |
No output schema declared.
No examples provided.
list_issues ~113
List issues in a GitHub repository.
| Name | Type | Req | Description |
|---|---|---|---|
| labels | string | – | Comma-separated list of label names to filter issues by. |
| owner | string | yes | Owner of the repository (user or organization name). |
| page | number | – | Page number of the issues to return, for pagination. |
| perPage | number | – | Number of issues per page, for pagination. |
| repo | string | yes | Name of the repository. |
| state | string | – | Filter issues by state: open, closed, or all. |
No output schema declared.
No examples provided.
list_pull_requests ~99
List pull requests in a GitHub repository.
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | yes | Owner of the repository (user or organization name). |
| page | number | – | Page number of the pull requests to return, for pagination. |
| perPage | number | – | Number of pull requests per page, for pagination. |
| repo | string | yes | Name of the repository. |
| state | string | – | Filter pull requests by state: open, closed, or all. |
No output schema declared.
No examples provided.
push_files ~95
Push one or more files to a GitHub repository in a single commit.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | yes | Branch to push the files to. |
| files | array | yes | List of files to push, each with a path and its content. |
| message | string | yes | Commit message for the push. |
| owner | string | yes | Owner of the repository (user or organization name). |
| repo | string | yes | Name of the repository. |
No output schema declared.
No examples provided.
search_code ~63
Search for code across GitHub repositories.
| Name | Type | Req | Description |
|---|---|---|---|
| page | number | – | Page number of the search results to return, for pagination. |
| perPage | number | – | Number of search results per page, for pagination. |
| q | string | yes | The code search query string. |
No output schema declared.
No examples provided.
search_repositories ~62
Search for GitHub repositories.
| Name | Type | Req | Description |
|---|---|---|---|
| page | number | – | Page number of the search results to return, for pagination. |
| perPage | number | – | Number of search results per page, for pagination. |
| query | string | yes | The repository search query string. |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/codehost-remote MCP server?
io.github.CloudCorpRecords/codehost-remote runs locally as an npm package, launched with npx -y @reneturcios/codehost-remote. 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/codehost-remote
claude mcp add cloudcorprecords-codehost-remote -- npx -y @reneturcios/codehost-remote
What is the io.github.CloudCorpRecords/codehost-remote MCP server?
io.github.CloudCorpRecords/codehost-remote is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/codehost-remote. Forward GitHub tools to the hosted GitHub Copilot remote MCP endpoint. This page covers its npm package (@reneturcios/codehost-remote).
Is the io.github.CloudCorpRecords/codehost-remote MCP server safe to use?
io.github.CloudCorpRecords/codehost-remote scores 66 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/codehost-remote MCP server expose?
io.github.CloudCorpRecords/codehost-remote exposes 14 tools: create_repository, fork_repository, create_branch, get_file_contents, create_or_update_file, and 9 more. Their descriptions and schemas cost roughly 1,267 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/codehost-remote MCP server still maintained?
io.github.CloudCorpRecords/codehost-remote 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/codehost-remote MCP server under?
io.github.CloudCorpRecords/codehost-remote declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.