Analyze public GitHub repos and PRs for risks, findings, and merge readiness.
This MCP tool appears to analyze public GitHub repositories and PRs, requires no declared credentials, and benefits from positive trust signals including an official registry listing, open-source code, and recent maintenance. Overall risk is relatively low, with normal caution warranted for outbound network access and code execution capability, but no clear red flags are evident from the provided materials.
The materials explicitly state that no keys or environment variables are required; there is no indication that GitHub tokens, cloud secrets, or other sensitive credentials must be provided, so credential exposure risk appears low.
The tool connects to the remote endpoint mcp-github-screen.gitlumen.com and screens public GitHub repositories/PRs; this implies that repository identifiers, PR content, or analysis inputs may be sent to GitLumen’s service. This egress is aligned with the stated functionality, but it is still outbound data sharing that warrants caution.
The system flags this tool as having code-execution capability, meaning the MCP may start local processes or execute program logic on the host. The provided materials do not show requests for unusual system privileges or execution scope unrelated to its purpose, so this is best treated as normal MCP execution capability with caution.
The description only indicates analysis of public GitHub repositories and PRs, with no stated access to local files, disk writes, private repositories, or broad host-level data permissions. Based on the available materials, the data access scope appears consistent with the function and shows no obvious overreach.
Positive supply-chain signals include an official registry listing, an auditable open-source repository, and updates within the last year, all of which materially reduce risk. However, the repository does not declare a license and has very low visible community adoption (0 stars), so a caution rating is more appropriate than fully low risk.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "GitLumen MCP" MCP server from askskill: Run: claude mcp add --transport http 'io-github-gitlumen-team-gitlumen-mcp' 'https://mcp-github-screen.gitlumen.com/mcp'
Analyze the public changes in this GitHub PR, generate a risk map, list key findings, and judge whether it is ready to merge: <PR URL>
Returns high-, medium-, and low-risk areas, potential defects and blockers, plus a clear merge recommendation.
Scan this public GitHub repository and identify major risk areas, suspicious modules, and regions that need priority attention: <repository URL>
Outputs a repository-level risk map, highlights high-risk modules, and suggests follow-up review or remediation priorities.
Using this PR and the target repository context, determine whether the changes meet pre-release merge standards and explain the main reasons: <PR URL> <repository URL>
Provides a merge-readiness verdict, the main risk rationale, and recommended checks to complete before release.
Assess open-source health, dependency risks, trends, and license differences.
Scan code for security risks before commits with automated review assistance.
Manage GitHub repositories, branches, pull requests, and commits through an MCP server.
Connect GitHub repos so AI can analyze and build from real code.
Manage GitLab repositories, merge requests, issues, and pipelines using natural language.
Use natural language to review MRs, manage issues, and monitor GitLab pipelines.