GitHub Issue MCP
NPM · GITHUB-ISSUE-MCP
AI-powered MCP server for generating GitHub issues and detecting semantic duplicates.
Available components
Last scanned (22 hours ago)
Scores higher than 65% 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 Security98
- 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
- 50 of 156 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 62 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 403 tokens (~80/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 12 Oct 26 −3
- Stability: pass → 0.80 functional
- 11 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 4 Oct 26 +1
- Stability: 0.97 → pass security
- 2 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
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 npm/github-issue-mcp@1.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 156 packages
| Packages resolved | 156 |
|---|---|
| Deprecated | 1 |
| Stale | 49 |
| 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 →
check_duplicate_issue ~104
Find the most likely existing open GitHub issues that could be related to a proposed issue. This tool retrieves open issues and performs cheap lexical candidate ranking. Treat the returned issues as candidates only; semantic duplicate determination must be done by the AI. Do not call list_github_issues separately for duplicate checking.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | Description of the proposed issue |
| owner | string | yes | GitHub repository owner |
| repo | string | yes | GitHub repository name |
No output schema declared.
No examples provided.
create_github_issue ~74
Create a new issue in a GitHub repository
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Issue body in Markdown |
| labels | array | – | GitHub labels to apply |
| owner | string | yes | GitHub repository owner |
| repo | string | yes | GitHub repository name |
| title | string | yes | Issue title |
No output schema declared.
No examples provided.
generate_issue ~142
Generate a structured GitHub issue using the issue description, issue details, and repository labels.
| Name | Type | Req | Description |
|---|---|---|---|
| actualBehavior | string | – | What actually happens |
| additionalContext | string | – | Logs, screenshots, related information, or other useful context |
| description | string | yes | Short natural-language description of the problem or request |
| environment | string | – | Browser, operating system, application version, etc. |
| expectedBehavior | string | – | What should happen |
| labels | array | – | Labels selected from the repository's available GitHub labels |
| reproductionSteps | string | – | Steps required to reproduce the issue |
| type | string | yes | Type of GitHub issue |
No output schema declared.
No examples provided.
list_github_issues ~42
List open issues in a GitHub repository
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | yes | GitHub repository owner |
| repo | string | yes | GitHub repository name |
No output schema declared.
No examples provided.
list_github_labels ~41
List labels available in a GitHub repository
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | yes | GitHub repository owner |
| repo | string | yes | GitHub repository name |
No output schema declared.
No examples provided.
How do I install the GitHub Issue MCP server?
GitHub Issue MCP runs locally as an npm package, launched with npx -y github-issue-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · github-issue-mcp
claude mcp add sarim-aliii-github-issue-mcp -- npx -y github-issue-mcp
What is the GitHub Issue MCP server?
GitHub Issue MCP is listed in the public MCP registry as io.github.sarim-aliii/github-issue-mcp. AI-powered MCP server for generating GitHub issues and detecting semantic duplicates. This page covers its npm package (github-issue-mcp).
Is the GitHub Issue MCP server safe to use?
GitHub Issue MCP scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 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 GitHub Issue MCP server expose?
GitHub Issue MCP exposes 5 tools: generate_issue, create_github_issue, list_github_issues, list_github_labels, check_duplicate_issue. Their descriptions and schemas cost roughly 403 tokens of context every time the server is loaded.
Is the GitHub Issue MCP server still maintained?
GitHub Issue 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.