# io.github.CloudCorpRecords/codehost-port (npm · @reneturcios/codehost-port)

GitHub repositories, issues and pull requests via the REST API, as MCP tools.

- Trust score: 66/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@reneturcios/codehost-port`: 66/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-codehost-port/reneturcios-codehost-port.md), [page](https://verifymcp.io/servers/cloudcorprecords-codehost-port/reneturcios-codehost-port)
- oci · `ghcr.io/cloudcorprecords/codehost-port`: 41/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-codehost-port/ghcr-io-cloudcorprecords-codehost-port.md), [page](https://verifymcp.io/servers/cloudcorprecords-codehost-port/ghcr-io-cloudcorprecords-codehost-port)

## Channel facts

- Registry: `npm`
- Package: `@reneturcios/codehost-port`
- 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**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 30 of 93 dependencies flagged as unhealthy.
- **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 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1294 tokens (~92/item across 14 items; 14 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 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 14 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 14 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.

## Install

### How do I install the io.github.CloudCorpRecords/codehost-port MCP server?

io.github.CloudCorpRecords/codehost-port runs locally as an npm package, launched with npx -y @reneturcios/codehost-port. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add cloudcorprecords-codehost-port -- npx -y @reneturcios/codehost-port
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-codehost-port": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/codehost-port"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-codehost-port": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/codehost-port"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-codehost-port -- npx -y @reneturcios/codehost-port
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-codehost-port": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@reneturcios/codehost-port"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cloudcorprecords-codehost-port --command npx --arg -y --arg @reneturcios/codehost-port
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-codehost-port:
    command: "npx"
    args: ["-y", "@reneturcios/codehost-port"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-codehost-port": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@reneturcios/codehost-port"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add cloudcorprecords-codehost-port -t stdio -c npx -a -y @reneturcios/codehost-port
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-codehost-port": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/codehost-port"
      ]
    }
  }
}
```

## 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 66, +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.

### 2026-11-02 (score 65, +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.

### 2026-11-01 (score 64)

First indexed and scored.

## MCP tools (14)

### `create_repository` (~77 tokens)

Create a new GitHub repository for the authenticated user.

Input parameters:

- `autoInit` (boolean): Whether to initialize the new repository with a README file.
- `description` (string): A description of the new repository.
- `name` (string, required): The name of the new repository.
- `private` (boolean): Whether the new repository should be private.

### `fork_repository` (~47 tokens)

Fork a GitHub repository into the authenticated user's account.

Input parameters:

- `owner` (string, required): The owner of the repository to fork.
- `repo` (string, required): The name of the repository to fork.

### `create_branch` (~97 tokens)

Create a new branch in a repository, optionally from another branch.

Input parameters:

- `branch` (string, required): 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, required): The owner of the repository to create the branch in.
- `repo` (string, required): The name of the repository to create the branch in.

### `get_file_contents` (~89 tokens)

Get the contents of a file or directory from a GitHub repository.

Input parameters:

- `branch` (string): The branch to get the file contents from.
- `owner` (string, required): The owner of the repository to get file contents from.
- `path` (string, required): The path to the file or directory in the repository.
- `repo` (string, required): The name of the repository to get file contents from.

### `create_or_update_file` (~134 tokens)

Create or update a single file in a GitHub repository.

Input parameters:

- `branch` (string, required): The branch to create or update the file on.
- `content` (string, required): The new content of the file.
- `message` (string, required): The commit message for the file creation or update.
- `owner` (string, required): The owner of the repository containing the file.
- `path` (string, required): The path to the file in the repository.
- `repo` (string, required): The name of the repository containing the file.
- `sha` (string): The blob SHA of the file being replaced, required when updating an existing file.

### `push_files` (~100 tokens)

Push one or more files to a GitHub repository in a single commit.

Input parameters:

- `branch` (string, required): The branch to push the files to.
- `files` (array, required): The files to push, each with its path and content.
- `message` (string, required): The commit message for the push.
- `owner` (string, required): The owner of the repository to push files to.
- `repo` (string, required): The name of the repository to push files to.

### `search_repositories` (~58 tokens)

Search for GitHub repositories.

Input parameters:

- `page` (number): The page number of results to return.
- `perPage` (number): The maximum number of results to return per page.
- `query` (string, required): The search query for repositories.

### `search_code` (~59 tokens)

Search for code across GitHub repositories.

Input parameters:

- `page` (number): The page number of results to return.
- `perPage` (number): The maximum number of results to return per page.
- `q` (string, required): The search query for code.

### `list_issues` (~119 tokens)

List issues in a GitHub repository.

Input parameters:

- `labels` (string): Filter issues by label names, as a comma-separated string.
- `owner` (string, required): 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, required): The name of the repository to list issues in.
- `state` (string): Filter issues by state, such as 'open' or 'closed'.

### `get_issue` (~66 tokens)

Get the details of a specific issue in a GitHub repository.

Input parameters:

- `issue_number` (number, required): The number of the issue to retrieve.
- `owner` (string, required): The owner of the repository containing the issue.
- `repo` (string, required): The name of the repository containing the issue.

### `create_issue` (~112 tokens)

Create a new issue in a GitHub repository.

Input parameters:

- `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, required): The owner of the repository to create the issue in.
- `repo` (string, required): The name of the repository to create the issue in.
- `title` (string, required): The title of the new issue.

### `add_issue_comment` (~90 tokens)

Add a comment to an existing issue in a GitHub repository.

Input parameters:

- `body` (string, required): The text of the comment to add.
- `issue_number` (number, required): The number of the issue to add the comment to.
- `owner` (string, required): The owner of the repository containing the issue to comment on.
- `repo` (string, required): The name of the repository containing the issue to comment on.

### `list_pull_requests` (~107 tokens)

List pull requests in a GitHub repository.

Input parameters:

- `owner` (string, required): 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, required): The name of the repository to list pull requests in.
- `state` (string): Filter pull requests by state, such as 'open' or 'closed'.

### `create_pull_request` (~139 tokens)

Create a new pull request in a GitHub repository.

Input parameters:

- `base` (string, required): 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, required): The name of the branch to merge from (the source branch).
- `owner` (string, required): The owner of the repository to create the pull request in.
- `repo` (string, required): The name of the repository to create the pull request in.
- `title` (string, required): The title of the new pull request.

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-codehost-port/reneturcios-codehost-port#diagnostics

## Score history

- 2026-11-05: 66
- 2026-11-04: 65
- 2026-11-03: 65
- 2026-11-02: 65
- 2026-11-01: 64

## Common questions

### 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 npm package (@reneturcios/codehost-port).

### Is the io.github.CloudCorpRecords/codehost-port MCP server safe to use?

io.github.CloudCorpRecords/codehost-port 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-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.

## Links

- npm package: https://www.npmjs.com/package/@reneturcios/codehost-port
- Socket report: https://socket.dev/npm/package/@reneturcios/codehost-port
- Repository: https://github.com/CloudCorpRecords/codehost-port
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-codehost-port/reneturcios-codehost-port.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-codehost-port/reneturcios-codehost-port.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-codehost-port/reneturcios-codehost-port