Github
NPM · @PIPEWORX/MCP-GITHUB · 2 COMPONENTS
GitHub MCP — wraps the GitHub public REST API (no auth required for public endpoints)
Available components
Last scanned (5 hours ago)
Scores higher than 77% 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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-github). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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 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.
- 3 Nov 26 +26
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → pass ▲ functional
- 2 Nov 26 −25
- Malware scan: pass → unverified ▼ security
- Known CVEs: pass → unverified ▼ security
- Dependency health: pass → unverified ▼ functional
- Package version: 0.2.0 → 0.2.1 functional
- 31 Oct 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.
- 29 Oct 26 80
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/@pipeworx/mcp-github@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-github |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-github/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3637324738 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:6fd3c3379c25039901ad7af97fb0daa07be988b4eb2581d54dacc18638a677b66d94cf1c293f6bec4e41e64183b6ed9ff107265b6a91f8f66a4074b41 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
get_file_contents ~204
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | yes | 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 | yes | Repo name (e.g. "cli"). |
No output schema declared.
No examples provided.
get_releases ~153
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.
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | yes | Repo owner or org (e.g. "cli"). |
| per_page | number | – | Number of recent releases to list (default 5, max 30). |
| repo | string | yes | Repo name (e.g. "cli"). |
No output schema declared.
No examples provided.
get_repo ~151
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).
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | – | Repository owner (user or org), e.g. "facebook". May be omitted if `repo` carries the full "owner/repo" slug. |
| repo | string | yes | Repository name, e.g. "react". Also accepts the full slug "facebook/react". |
No output schema declared.
No examples provided.
get_user ~66
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").
| Name | Type | Req | Description |
|---|---|---|---|
| username | string | yes | GitHub username, e.g. "torvalds" |
No output schema declared.
No examples provided.
github_trending_repos ~440
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
list_commits ~239
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.
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | yes | 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 | yes | 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. |
No output schema declared.
No examples provided.
list_repo_issues ~119
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.
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | yes | Repository owner (user or org) |
| per_page | number | – | Number of issues to return (default 10, max 30) |
| repo | string | yes | Repository name |
| state | string | – | Filter by issue state: open, closed, or all (default: open) |
No output schema declared.
No examples provided.
search_code ~200
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.
| Name | Type | Req | Description |
|---|---|---|---|
| per_page | number | – | Number of results to return (default 10, max 30). |
| query | string | yes | Code search query, e.g. "NewCmdRoot repo:cli/cli", "createRoot language:typescript", "addEventListener org:facebook". |
No output schema declared.
No examples provided.
search_repos ~108
Search GitHub repositories by keyword. Returns repo name, description, star count, forks, primary language, and URL. Use when exploring projects or finding code implementations.
| Name | Type | Req | Description |
|---|---|---|---|
| per_page | number | – | Number of results to return (default 10, max 30) |
| query | string | yes | Search query string (e.g., "react hooks", "cli tool language:go") |
| sort | string | – | Sort results by: stars, forks, or updated (default: stars) |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-github
claude mcp add pipeworx-io-github -- npx -y @pipeworx/mcp-github
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.