GitHub MCP Server

The materials state there are no required keys or environment variables, but the tool claims to connect directly to the GitHub API, which often involves GitHub authentication in practice. The documentation does not explain auth method, permission scope, or token handling, leaving credential boundaries unclear.

Its stated functionality clearly requires access to the GitHub API, so network egress is expected and may include user queries and repository-related data. However, no specific remote endpoints are documented, reducing transparency. There is no evidence in the materials of data being sent to unrelated or unknown third-party endpoints.

System checks indicate the tool executes code or launches local processes, which is a common MCP capability. The available materials do not describe additional system privileges, command scope, or sandboxing, so this warrants normal caution but does not by itself justify a high-risk rating.

Based on the description, it primarily accesses live GitHub repository data, issues, PRs, and contributions. There is no explicit claim that it needs sensitive local files or data permissions beyond its stated purpose. However, with no README, it cannot be verified whether it also touches local workspaces, caches, or config files.

There is a public open-source repository, making the code auditable in principle, which is a positive sign. However, it comes from a third-party registry, has no declared license, 0 stars, unknown maintenance status, and very sparse documentation, so the supply-chain trust signals are weak and the repository and dependencies should be reviewed first.