Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search
Nothing to run from here
Codehost Remote is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
trust score
12
downloads a day
local
runs on your machine
308
downloads in 30d
What it does
Forward GitHub tools to the hosted GitHub Copilot remote MCP endpoint.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user codehost-remote-mcp '--' npx -y @reneturcios/codehost-remote mcp
# 2 — ask your agent for something these tools do
# create_repository, fork_repository, create_branch and 11 more
Codehost Remote costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
CLAll 425 servers
CloudCorpRecords425 servers
28 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Codehost Remote as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user codehost-remote-mcp '--' npx -y @reneturcios/codehost-remote mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
14 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Create a new GitHub repository for the authenticated user.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Name for the new repository. |
| description | string | no | A short description of the new repository. |
| private | boolean | no | Whether the new repository is private (true) or public (false). |
| autoInit | boolean | no | Whether to initialize the new repository with a README file. |
Fork a GitHub repository into the authenticated user's account.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| owner | string | yes | Owner of the repository to fork (user or organization name). |
| repo | string | yes | Name of the repository to fork. |
Create a new branch in a repository, optionally from another branch.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| owner | string | yes | Owner of the repository (user or organization name). |
| repo | string | yes | Name of the repository. |
| branch | string | yes | Name of the new branch to create. |
| from_branch | string | no | Name of the existing branch to create the new branch from. If omitted, the repository's default branch is used. |
Get the contents of a file or directory from a GitHub repository.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| owner | string | yes | Owner of the repository (user or organization name). |
| repo | string | yes | Name of the repository. |
| path | string | yes | Path of the file or directory to retrieve, relative to the repository root. |
| branch | string | no | Branch to get the contents from. If omitted, the repository's default branch is used. |
Create or update a single file in a GitHub repository.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| owner | string | yes | Owner of the repository (user or organization name). |
| repo | string | yes | Name of the repository. |
| path | string | yes | Path where the file will be created or updated, relative to the repository root. |
| content | string | yes | Contents of the file. |
| message | string | yes | Commit message for the file change. |
| branch | string | yes | Branch on which to create or update the file. |
| sha | string | no | SHA of the existing file being replaced. Required when updating an existing file; omit when creating a new file. |
Push one or more files to a GitHub repository in a single commit.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| owner | string | yes | Owner of the repository (user or organization name). |
| repo | string | yes | Name of the repository. |
| 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. |
Search for GitHub repositories.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | The repository search query string. |
| page | number | no | Page number of the search results to return, for pagination. |
| perPage | number | no | Number of search results per page, for pagination. |
Search for code across GitHub repositories.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | yes | The code search query string. |
| page | number | no | Page number of the search results to return, for pagination. |
| perPage | number | no | Number of search results per page, for pagination. |
List issues in a GitHub repository.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| owner | string | yes | Owner of the repository (user or organization name). |
| repo | string | yes | Name of the repository. |
| state | string | no | Filter issues by state: open, closed, or all. |
| labels | string | no | Comma-separated list of label names to filter issues by. |
| perPage | number | no | Number of issues per page, for pagination. |
| page | number | no | Page number of the issues to return, for pagination. |
Get the details of a specific issue in a GitHub repository.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| owner | string | yes | Owner of the repository (user or organization name). |
| repo | string | yes | Name of the repository. |
| issue_number | number | yes | Number of the issue to retrieve. |
Create a new issue in a GitHub repository.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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. |
| body | string | no | Body text of the new issue. |
| assignees | array | no | List of user logins to assign to the new issue. |
| labels | array | no | List of label names to apply to the new issue. |
Add a comment to an existing issue in a GitHub repository.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| owner | string | yes | Owner of the repository (user or organization name). |
| repo | string | yes | Name of the repository. |
| issue_number | number | yes | Number of the issue to comment on. |
| body | string | yes | Text of the comment to add. |
List pull requests in a GitHub repository.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| owner | string | yes | Owner of the repository (user or organization name). |
| repo | string | yes | Name of the repository. |
| state | string | no | Filter pull requests by state: open, closed, or all. |
| perPage | number | no | Number of pull requests per page, for pagination. |
| page | number | no | Page number of the pull requests to return, for pagination. |
Create a new pull request in a GitHub repository.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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. |
| body | string | no | Body text of the new pull request. |
| head | string | yes | Name of the branch containing the changes to merge (the source branch). |
| base | string | yes | Name of the branch to merge the changes into (the target branch). |
| draft | boolean | no | Whether to create the pull request as a draft. |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Codehost Remote or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 93 / 100
Release 0.1.0 · scanned 2 Nov 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 2 capability
Capabilityhigh
Coveragesource
Verificationrepo
Surface digestbdfa707dbe325c95ebeb85a1a9991c93dfb593c64251d45623352b636c9bfca4
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (14 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| create_repository | no tags | |
| fork_repository | no tags | |
| create_branch | no tags | |
| get_file_contents | sensitive-source | sensitive-source: keyword "get_file_contents" |
| create_or_update_file | no tags | |
| push_files | no tags | |
| search_repositories | no tags | |
| search_code | no tags | |
| list_issues | no tags | |
| get_issue | no tags | |
| create_issue | external-sink | external-sink: keyword "create_issue" |
| add_issue_comment | no tags | |
| list_pull_requests | no tags | |
| create_pull_request | external-sink | external-sink: keyword "create_pull_request" |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
get_file_contents → create_issue
A sensitive-source → external-sink chain exists: get_file_contents ⇒ create_issue.
Supply chain and provenance
Integrityfirst-seen
Surface digestbdfa707dbe325c95
Scanned2026-11-02
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.1.0. Pin a release below and the command asks for exactly that one.
0.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Codehost Remote can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.