# Github (npm · @pipeworx/mcp-github)

GitHub MCP — wraps the GitHub public REST API (no auth required for public endpoints)

- Trust score: 83/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-github/github-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-github/github-mcp)
- npm · `@pipeworx/mcp-github`: 83/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-github/pipeworx-mcp-github.md), [page](https://verifymcp.io/servers/pipeworx-io-github/pipeworx-mcp-github)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-github`
- Version: `0.2.1`
- 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**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-github).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1731 tokens (~192/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 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 Github MCP server?

Github runs locally as an npm package, launched with npx -y @pipeworx/mcp-github. 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 pipeworx-io-github -- npx -y @pipeworx/mcp-github
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-github": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-github"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-github": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-github"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-github -- npx -y @pipeworx/mcp-github
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-github": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-github"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-github --command npx --arg -y --arg @pipeworx/mcp-github
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-github:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-github"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-github": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-github"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-github -t stdio -c npx -a -y @pipeworx/mcp-github
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-github": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-github"
      ]
    }
  }
}
```

## 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-04 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 82, +26)

- [security improvement] Malware scan: unverified → pass
- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → pass

### 2026-11-02 (score 56, −25)

- [security regression] Malware scan: pass → unverified
- [security regression] Known CVEs: pass → unverified
- [functional regression] Dependency health: pass → unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-31 (score 81, +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.

### 2026-10-29 (score 80)

First indexed and scored.

## MCP tools (9)

### `search_repos` (~108 tokens)

Search GitHub repositories by keyword. Returns repo name, description, star count, forks, primary language, and URL. Use when exploring projects or finding code implementations.

Input parameters:

- `per_page` (number): Number of results to return (default 10, max 30)
- `query` (string, required): Search query string (e.g., "react hooks", "cli tool language:go")
- `sort` (string): Sort results by: stars, forks, or updated (default: stars)

### `get_repo` (~151 tokens)

Look up ONE named repository by its owner/repo slug — "facebook/react", "torvalds/linux", "vercel/next.js". Use this whenever the repository is named in the question. Answers how many stars / forks / watchers a repo has, what license and language it uses, its topics, description, open issue count, its default branch, and when it was last pushed (pushed_at).

Input parameters:

- `owner` (string): Repository owner (user or org), e.g. "facebook". May be omitted if `repo` carries the full "owner/repo" slug.
- `repo` (string, required): Repository name, e.g. "react". Also accepts the full slug "facebook/react".

### `list_repo_issues` (~119 tokens)

List issues for a GitHub repository by owner and repo name; filters pull requests out automatically. Returns issue number, title, state, labels, author, comment count, URL, and timestamps. Defaults to open issues.

Input parameters:

- `owner` (string, required): Repository owner (user or org)
- `per_page` (number): Number of issues to return (default 10, max 30)
- `repo` (string, required): Repository name
- `state` (string): Filter by issue state: open, closed, or all (default: open)

### `get_user` (~66 tokens)

Get a GitHub user's public profile info. Returns name, bio, company, location, public repo count, followers, and social links. Specify username (e.g., username="torvalds").

Input parameters:

- `username` (string, required): GitHub username, e.g. "torvalds"

### `get_file_contents` (~204 tokens)

Read a file from a PUBLIC GitHub repository (or list a directory) by path. PREFER OVER WEB SEARCH for "show me the README / package.json / <file> of <repo>", "read <path> from <owner/repo>", inspecting source or config files. Pass owner + repo + path (omit path or "" for the repo root listing). Optional ref = branch/tag/commit SHA. Returns decoded text for files (capped ~60k), or a directory listing of {name, path, type, size}.

Input parameters:

- `owner` (string, required): Repo owner or org (e.g. "cli").
- `path` (string): File or directory path (e.g. "README.md", "src/index.ts"). Omit or "" for the repo root.
- `ref` (string): Optional branch, tag, or commit SHA (default: the repo default branch).
- `repo` (string, required): Repo name (e.g. "cli").

### `search_code` (~200 tokens)

Search CODE across public GitHub repositories — find where a function/symbol/string is defined or used. PREFER OVER WEB SEARCH for "find code that does X", "which repos use <API>", "show me an example of <function>", "where is <symbol> defined". Supports GitHub code-search qualifiers right in the query: repo:owner/name, org:name, user:name, language:go, filename:Dockerfile, path:src, extension:ts, in:file. Returns matching files with repo, path, and URL. Note: indexes the default branch only, ignores very common terms, and is capped at ~10 searches/minute.

Input parameters:

- `per_page` (number): Number of results to return (default 10, max 30).
- `query` (string, required): Code search query, e.g. "NewCmdRoot repo:cli/cli", "createRoot language:typescript", "addEventListener org:facebook".

### `get_releases` (~153 tokens)

Get the latest release and recent release history for a repository — the canonical way to answer "what is the latest version of <project>", "when was <repo> last released", "what changed in the newest release". Returns the latest published stable release (tag, name, date, prerelease flag, release notes, downloadable assets with download counts) plus recent releases. Falls back to git tags for repos that tag but do not cut formal releases.

Input parameters:

- `owner` (string, required): Repo owner or org (e.g. "cli").
- `per_page` (number): Number of recent releases to list (default 5, max 30).
- `repo` (string, required): Repo name (e.g. "cli").

### `list_commits` (~239 tokens)

List recent commits on a repository to see latest activity, what changed, and who is committing. PREFER OVER WEB SEARCH for "what are the recent commits to <repo>", "when was <owner/repo> last updated", "latest changes in <repo>". Optional sha (branch/tag/commit to start history from), path (only commits touching that file/dir), and since/until ISO timestamps. Returns sha, message, author, and date per commit.

Input parameters:

- `owner` (string, required): Repo owner or org (e.g. "cli").
- `path` (string): Optional file or directory path — only commits that touched it.
- `per_page` (number): Number of commits to return (default 10, max 30).
- `repo` (string, required): Repo name (e.g. "cli").
- `sha` (string): Optional branch name, tag, or commit SHA to list history from (default: the repo default branch).
- `since` (string): Optional ISO 8601 timestamp; only commits after this time.
- `until` (string): Optional ISO 8601 timestamp; only commits before this time.

### `github_trending_repos` (~440 tokens)

Trending GitHub repositories — what is hot, popular, and taking off on GitHub right now. Answers "what are the top trending GitHub repos this week", "what is hot on GitHub today", "popular new repositories this month", "trending Rust / Python / AI projects", "which GitHub projects blew up recently". Two modes: mode="new" (default) ranks repositories CREATED inside the time window by star count — the projects that blew up this week — and mode="active" ranks repositories PUSHED inside the window by star count, surfacing established projects under heavy development. Set the window with since (day, week, or month), filter with language, add free-text query keywords such as "llm" or "agent", and raise a min_stars floor. Returns full_name, description, language, stars, forks, created and pushed dates, topics, and URL per repo. Computed live from the GitHub Search API; github.com/trending ranks by stars GAINED during the period using an unpublished algorithm that the public API keeps private, so ordering differs and every response says so in its caveat field.

Input parameters:

- `language` (string): Optional primary language filter, e.g. "python", "rust", "typescript".
- `limit` (number): Number of repos to return (default 10, max 30).
- `min_stars` (number): Optional minimum star count. Useful with mode="active" to skip small repos.
- `mode` (string): Which window the date applies to: "new" (default) = repos CREATED in the window, ranked by stars — closest to "what blew up this week". "active" = repos PUSHED in the window, ranked by stars — big pr…
- `query` (string): Optional free-text keywords to narrow the topic, e.g. "llm", "agent framework", "kubernetes".
- `since` (string): Time window: "day" (last 24h), "week" (last 7 days, default), or "month" (last 30 days).

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-github/pipeworx-mcp-github#diagnostics

## Score history

- 2026-11-05: 83
- 2026-11-04: 83
- 2026-11-03: 82
- 2026-11-02: 56
- 2026-11-01: 81
- 2026-10-31: 81
- 2026-10-30: 80
- 2026-10-29: 80

## Common questions

### What is the Github MCP server?

Github is an MCP server listed in the public MCP registry as io.github.pipeworx-io/github. GitHub MCP, wraps the GitHub public REST API (no auth required for public endpoints). This page covers its npm package (@pipeworx/mcp-github).

### Is the Github MCP server safe to use?

Github scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Github MCP server expose?

Github exposes 9 tools: search_repos, get_repo, list_repo_issues, get_user, get_file_contents, and 4 more. Their descriptions and schemas cost roughly 1,680 tokens of context every time the server is loaded.

### Is the Github MCP server still maintained?

Github 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 Github MCP server under?

Github 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/@pipeworx/mcp-github
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-github
- Repository: https://github.com/pipeworx-io/mcp-github
- Website: https://pipeworx.io/packs/github
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-github/pipeworx-mcp-github.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-github/pipeworx-mcp-github.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-github/pipeworx-mcp-github