GitHub MCP Server

The material explicitly states that no keys or environment variables are required, and no sensitive credentials are requested; based on the available information, credential exposure appears limited. If a GitHub token is later introduced in deployment, its scope should be reviewed separately.

Although the remote-endpoint field says 'none,' the description explicitly says it performs API calls to interact with GitHub, so normal outbound network traffic to GitHub-related APIs should be expected and user queries may be transmitted there. There is no evidence of exfiltration to unrelated or unknown third-party endpoints.

The system flags this tool as executes-code, meaning it runs locally as a process, which is a normal capability for this class of MCP tools. The available material does not show requests for unusual system privileges or clearly unrelated high-risk operations.

The material only indicates that it returns structured responses from GitHub API calls and does not declare local file read/write access, local database access, or broad system-resource permissions. Based on current information, data access appears mainly limited to GitHub resources requested by the user, with no clear signs of over-privilege.

A positive factor is the presence of an auditable open-source repository; however, the source is a third-party registry, no license is declared, community adoption is 0 stars, maintenance status is unknown, and the README is absent, leaving weak verifiability and maturity signals. Overall, this fits caution rather than high risk.