MCP Weather Data Fetcher

The materials explicitly state there are no required keys or environment variables. No API tokens, account credentials, or local sensitive secrets are requested, so credential exposure and abuse risk appears low.

Although the listed remote host is 'none', the description says it retrieves live weather via OpenWeatherMap, which strongly suggests outbound requests to a third-party weather service. The materials do not specify exact domains, payloads, or whether user query content is transmitted, so the actual egress scope should be reviewed.

The system flags this tool as executes-code, meaning it has the normal MCP ability to run code or a local service process. The provided materials do not show requests for system privileges beyond its stated purpose, nor any suspicious execution chain, so this is standard caution rather than high risk.

The provided description does not claim any need to read or write local files, access databases, the clipboard, or other sensitive resources. Based on the stated function, it appears limited to receiving a city name and returning weather data, with no clear sign of excessive data access.

The project has a public GitHub repository, which is a meaningful risk-reducing factor because the source is auditable. However, it comes from a third-party registry, has 0 stars, no declared license, and unknown maintenance status, so community validation and governance signals are weak and the code and dependencies should be reviewed directly.