GitHub Release MCP
PYPI · GH-RELEASE-MCP
List and download GitHub release assets with multi-mirror parallel ranged download.
Available components
Last scanned (1 day ago)
Scores higher than 65% of PyPI 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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → 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 zishuowang696/gh-release-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 240 tokens (~120/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 82% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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.
- 16 Oct 26 62
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 16 Oct 2026 · Analysed pypi/gh-release-mcp@0.1.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 | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | zishuowang696/gh-release-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/zishuowang696/gh-release-mcp/.github/workflows/publish.yml@refs/tags/v0.1.1 |
| Rekor log index | 3270193516 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:6547bf89712aaa90ea7ca47ab23ae94088545b41f7c3e742b1a0801e1499528e |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
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 →
download_release_asset ~164
Download release asset(s) with parallel ranged requests across mirrors. Pick one asset by exact name, or several via a glob pattern. Verifies sha256 when GitHub exposes a digest.
| Name | Type | Req | Description |
|---|---|---|---|
| connections | integer | – | Parallel segments per file (default 8). |
| dest | string | – | Destination directory (default: current dir). |
| mirrors | array | – | Mirror prefixes (must support HTTP Range). Default: ['https://ghproxy.net', 'https://ghfast.top'] |
| name | string | – | Exact asset name (optional). |
| owner | string | yes | – |
| pattern | string | – | Glob, e.g. '*PUBLIC*.zip' (optional). |
| repo | string | yes | – |
| tag | string | – | Release tag; omit or 'latest'. |
No output schema declared.
No examples provided.
list_release_assets ~76
List the downloadable assets of a GitHub release (name, size, url).
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | yes | Repo owner, e.g. NationalSecurityAgency |
| repo | string | yes | Repo name, e.g. ghidra |
| tag | string | – | Release tag; omit or 'latest' for the latest release. |
No output schema declared.
No examples provided.
How do I install the GitHub Release MCP server?
GitHub Release MCP runs locally as a PyPI package, launched with uvx gh-release-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · gh-release-mcp
claude mcp add zishuowang696-gh-release-mcp -- uvx gh-release-mcp
What is the GitHub Release MCP server?
GitHub Release MCP is listed in the public MCP registry as io.github.zishuowang696/gh-release-mcp. List and download GitHub release assets with multi-mirror parallel ranged download. This page covers its PyPI package (gh-release-mcp).
Is the GitHub Release MCP server safe to use?
GitHub Release MCP scores 62 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 2026. 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 Release MCP server expose?
GitHub Release MCP exposes 2 tools: list_release_assets, download_release_asset. Their descriptions and schemas cost roughly 240 tokens of context every time the server is loaded.
Is the GitHub Release MCP server still maintained?
GitHub Release MCP is still listed as active in the MCP registry. We last reached this channel on 16 October 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 Release MCP server under?
GitHub Release MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.