Weather MCP Server

The materials explicitly state that no API key is required, and no sensitive credentials are requested. Based on the provided facts, credential exposure or misuse risk appears low.

The description says it uses Open-Meteo for global weather, air quality, and climate data, which normally implies outbound requests to a weather data service. Although no remote host is listed in the system fields and there is no evidence of unrelated exfiltration, routine network egress to a service aligned with its stated function should be expected.

The system flags executes-code, meaning this MCP tool runs locally as a process and executes its server code. This is a normal capability for this type of tool, and the materials do not show requests for system privileges beyond its stated purpose.

The provided materials do not specify access to particular local files, databases, or system resources, nor do they declare any write scope. Still, as a locally running MCP service, it has at least the default data exposure of its runtime environment, so it should be deployed with least privilege and its actual file access should be verified.

A positive factor is that the source is open and auditable. However, it comes from a third-party registry, the GitHub repo has 0 stars, no declared license, and unknown maintenance status, so community trust and maintenance signals are weak and the code/dependencies should be reviewed before use.