weather-mcp-server

The material states that no keys or environment variables are required, and it does not indicate any need for user API keys, tokens, or local sensitive credentials; based on the provided facts, credential exposure appears low.

The description explicitly says it works 'via the OpenWeatherMap API,' indicating outbound network requests to an external weather service. Although no specific host is listed and there is no evidence of unrelated data exfiltration, normal network egress is present.

The system flags that this tool executes code; as an MCP tool, this typically means running a local server process. The provided material does not show high-privilege system actions beyond its weather-query purpose, but local code execution still warrants caution.

The material does not claim any need to read or write local files or access databases, browsers, clipboards, or other sensitive resources. Based on the stated functionality, there is no sign of excessive data access.

There is a public GitHub repository, which provides some auditability and is a positive sign. However, the source is a third-party registry, the repo has 0 stars, no declared license, and unknown maintenance status, so trust and maintenance signals are weak and further code/dependency review is advisable before installation.