Weather MCP Server

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

The description says it uses the National Weather Service API for real-time weather data, which implies outbound network requests. Although no specific host is listed in the materials and the egress aligns with the stated purpose, query-related data would still be sent to an external service.

The system checks indicate that this tool executes code; as an MCP server, it typically runs a local process. The materials do not show requests for unusual system privileges or unrelated high-risk actions, but local code execution still merits caution.

The available materials do not state any need to read or write local files, access databases, system directories, or other sensitive resources. Based on the stated function, it appears focused on weather queries and alerts, with no clear signs of excessive data access.

There is a public open-source GitHub repository, which is a positive factor because the code can in principle be audited. However, the source is a third-party registry, the license is unspecified, community adoption is 0 stars, maintenance status is unknown, and the README is absent, so supply-chain trust and verifiability are only moderate.