GitHub Trending MCP Server

The materials explicitly state that no keys or environment variables are required, and there is no indication of a GitHub token or other sensitive credential being requested, so credential exposure risk appears low.

Its stated function implies network access to retrieve GitHub Trending data, likely from GitHub-related pages or endpoints; although no specific host is declared and there is no evidence of sending user data to unrelated endpoints, the outbound network behavior still warrants caution.

The system checks indicate that it executes code; as an MCP tool, this typically means running a local service process. The materials do not show requests for unusual system privileges or operations unrelated to its stated purpose, so this remains within normal caution territory.

The available materials do not specify any local file read/write scope or data persistence needs, and no overbroad access is declared; however, as a locally running MCP service, it may theoretically access invocation context inputs and outputs, so least-privilege use is advisable.

A public source repository is available for review, which is a positive risk-reducing factor; however, it comes from a third-party registry, has no declared license, shows 0 stars, and has unknown maintenance status, so trust signals are limited and the code and dependencies should be reviewed before deployment.