$ loading_
Manage GitHub repositories, issues, and pull requests through MCP or REST.
This MCP tool has an open-source repository and does not explicitly require secrets or remote endpoints, with no obvious high-risk red flags in the provided materials. However, it claims GitHub repository/issue/PR operations, which typically implies local server logic and handling of repository data, so it should still be used with normal caution for tool permissions.
The materials explicitly state that no keys or environment variables are required; there is no stated need for API tokens, account passwords, or other sensitive credentials. Based on the provided facts, credential exposure appears low, though any real GitHub integration should still be checked for undocumented authentication needs.
The description says it supports GitHub operations and a REST API, which functionally suggests likely network communication with GitHub-related services; however, the materials also say there are no remote hosts and no README is provided, so actual egress targets and scope cannot be confirmed. Network interaction is plausible, but there is no explicit red flag showing data exfiltration to unrelated or unknown endpoints.
The system checks explicitly mark this tool as executes-code, and as an MCP server/REST API service it would normally run a local process and handle requests. This is a standard capability for such tools; the provided materials do not show requests for unusual system privileges or clearly unrelated dangerous execution behavior.
It claims repository management, issues, and pull request capabilities, which implies possible reading or modifying repository content and related metadata; if local repositories are involved, it may also touch local files. Based on the materials, this is consistent with the stated functionality, and there is no evidence of clearly excessive access.
Positive factors: there is a public open-source repository under the MIT License, making it more auditable than closed-source software. Caution points: it comes from a third-party registry, has only 0 stars, unknown maintenance status, and no README was provided, limiting verifiable context; this makes supply-chain trust moderate but not enough on its own to classify as high risk.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "GitHub Prod MCP" yet — see the docs or source repo.
Use GitHub Prod MCP to list repositories active in my organization over the last 7 days, create an issue titled "Add project documentation" for any repo missing a README, and summarize the results.
A list of active repositories, details of created issues, and an execution summary.
Using GitHub Prod MCP, fetch all open pull requests assigned to me for review, group them by repository, flag items not updated for more than 3 days, and draft a follow-up message.
A grouped PR list, overdue flags, and a ready-to-send follow-up message.
Use GitHub Prod MCP to inspect open issues and unmerged pull requests under the current milestone of a target repository, then generate a pre-release checklist with risks and a recommended handling order.
A release-focused checklist with pending items, risk summaries, and priority recommendations.
Manage GitHub repositories, branches, pull requests, and commits through an MCP server.
Manage GitHub repos, issues, PRs, code search, and CI status in one place.
Create GitHub repositories quickly through MCP to start projects and collaboration.
Manage GitHub repositories, pull requests, issues, and workflows with natural language.
Manage GitHub repositories, labels, topics, and files through API automation.
Manage GitHub repositories, files, and user profiles through MCP actions.