io.github.CloudCorpRecords/codehost-port
OCI · GHCR.IO/CLOUDCORPRECORDS/CODEHOST-PORT · 2 COMPONENTS
GitHub repositories, issues and pull requests via the REST API, as MCP tools.
Available components
Last scanned (40 minutes ago)
Scores higher than 54% of OCI 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 Security0
- 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.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
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 Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1294 tokens (~92/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
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +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.
- 1 Nov 26 40
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 oci/ghcr.io/cloudcorprecords/codehost-port@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 | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 ~90
Add a comment to an existing issue in a GitHub repository.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | The text of the comment to add. |
| issue_number | number | yes | The number of the issue to add the comment to. |
| owner | string | yes | The owner of the repository containing the issue to comment on. |
| repo | string | yes | The name of the repository containing the issue to comment on. |
No output schema declared.
No examples provided.
create_branch ~97
Create a new branch in a repository, optionally from another branch.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | yes | The name of the new branch to create. |
| from_branch | string | – | The name of the branch to create the new branch from; defaults to the repository's default branch. |
| owner | string | yes | The owner of the repository to create the branch in. |
| repo | string | yes | The name of the repository to create the branch in. |
No output schema declared.
No examples provided.
create_issue ~112
Create a new issue in a GitHub repository.
| Name | Type | Req | Description |
|---|---|---|---|
| assignees | array | – | The usernames to assign to the new issue. |
| body | string | – | The body text of the new issue. |
| labels | array | – | The label names to add to the new issue. |
| owner | string | yes | The owner of the repository to create the issue in. |
| repo | string | yes | The name of the repository to create the issue in. |
| title | string | yes | The title of the new issue. |
No output schema declared.
No examples provided.
create_or_update_file ~134
Create or update a single file in a GitHub repository.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | yes | The branch to create or update the file on. |
| content | string | yes | The new content of the file. |
| message | string | yes | The commit message for the file creation or update. |
| owner | string | yes | The owner of the repository containing the file. |
| path | string | yes | The path to the file in the repository. |
| repo | string | yes | The name of the repository containing the file. |
| sha | string | – | The blob SHA of the file being replaced, required when updating an existing file. |
No output schema declared.
No examples provided.
create_pull_request ~139
Create a new pull request in a GitHub repository.
| Name | Type | Req | Description |
|---|---|---|---|
| base | string | yes | The name of the branch to merge into (the target branch). |
| body | string | – | The body text of the new pull request. |
| draft | boolean | – | Whether to create the pull request as a draft. |
| head | string | yes | The name of the branch to merge from (the source branch). |
| owner | string | yes | The owner of the repository to create the pull request in. |
| repo | string | yes | The name of the repository to create the pull request in. |
| title | string | yes | The title of the new pull request. |
No output schema declared.
No examples provided.
create_repository ~77
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 description of the new repository. |
| name | string | yes | The name of the new repository. |
| private | boolean | – | Whether the new repository should be private. |
No output schema declared.
No examples provided.
fork_repository ~47
Fork a GitHub repository into the authenticated user's account.
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | yes | The owner of the repository to fork. |
| repo | string | yes | The name of the repository to fork. |
No output schema declared.
No examples provided.
get_file_contents ~89
Get the contents of a file or directory from a GitHub repository.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | The branch to get the file contents from. |
| owner | string | yes | The owner of the repository to get file contents from. |
| path | string | yes | The path to the file or directory in the repository. |
| repo | string | yes | The name of the repository to get file contents from. |
No output schema declared.
No examples provided.
get_issue ~66
Get the details of a specific issue in a GitHub repository.
| Name | Type | Req | Description |
|---|---|---|---|
| issue_number | number | yes | The number of the issue to retrieve. |
| owner | string | yes | The owner of the repository containing the issue. |
| repo | string | yes | The name of the repository containing the issue. |
No output schema declared.
No examples provided.
list_issues ~119
List issues in a GitHub repository.
| Name | Type | Req | Description |
|---|---|---|---|
| labels | string | – | Filter issues by label names, as a comma-separated string. |
| owner | string | yes | The owner of the repository to list issues in. |
| page | number | – | The page number of issue results to return. |
| perPage | number | – | The maximum number of issues to return per page. |
| repo | string | yes | The name of the repository to list issues in. |
| state | string | – | Filter issues by state, such as 'open' or 'closed'. |
No output schema declared.
No examples provided.
list_pull_requests ~107
List pull requests in a GitHub repository.
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | yes | The owner of the repository to list pull requests in. |
| page | number | – | The page number of pull request results to return. |
| perPage | number | – | The maximum number of pull requests to return per page. |
| repo | string | yes | The name of the repository to list pull requests in. |
| state | string | – | Filter pull requests by state, such as 'open' or 'closed'. |
No output schema declared.
No examples provided.
push_files ~100
Push one or more files to a GitHub repository in a single commit.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | yes | The branch to push the files to. |
| files | array | yes | The files to push, each with its path and content. |
| message | string | yes | The commit message for the push. |
| owner | string | yes | The owner of the repository to push files to. |
| repo | string | yes | The name of the repository to push files to. |
No output schema declared.
No examples provided.
search_code ~59
Search for code across GitHub repositories.
| Name | Type | Req | Description |
|---|---|---|---|
| page | number | – | The page number of results to return. |
| perPage | number | – | The maximum number of results to return per page. |
| q | string | yes | The search query for code. |
No output schema declared.
No examples provided.
search_repositories ~58
Search for GitHub repositories.
| Name | Type | Req | Description |
|---|---|---|---|
| page | number | – | The page number of results to return. |
| perPage | number | – | The maximum number of results to return per page. |
| query | string | yes | The search query for repositories. |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/codehost-port MCP server?
io.github.CloudCorpRecords/codehost-port runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/codehost-port: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.
oci · ghcr.io/cloudcorprecords/codehost-port
claude mcp add cloudcorprecords-codehost-port -- docker run --rm -i ghcr.io/cloudcorprecords/codehost-port:0.1.0
What is the io.github.CloudCorpRecords/codehost-port MCP server?
io.github.CloudCorpRecords/codehost-port is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/codehost-port. GitHub repositories, issues and pull requests via the REST API, as MCP tools. This page covers its container image (ghcr.io/cloudcorprecords/codehost-port).
Is the io.github.CloudCorpRecords/codehost-port MCP server safe to use?
io.github.CloudCorpRecords/codehost-port scores 42 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/codehost-port MCP server expose?
io.github.CloudCorpRecords/codehost-port 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,294 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/codehost-port MCP server still maintained?
io.github.CloudCorpRecords/codehost-port 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-port MCP server under?
io.github.CloudCorpRecords/codehost-port declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.