io.github.cyanheads/openaq-mcp-server

The materials show a requirement for OPENAQ_API_KEY, which is a sensitive credential; the other environment variables appear to be configuration values. If logs, config files, or process environments are exposed, the API key could be misused, but there is no explicit sign of credential theft or over-collection in the provided materials.

The tool is declared to connect to openaq.caseyjhand.com to retrieve air-quality data, which is consistent with its stated purpose and a known remote endpoint. The materials do not indicate that extra user data is sent to unrelated or unknown services, so this appears to be routine network access rather than high-risk exfiltration.

The system checks indicate that this MCP tool can execute code or start processes, which is a routine property of this tool class and warrants caution. The current description does not show requests for obviously unrelated high-privilege system operations, so this alone does not justify a high-risk rating.

The provided materials do not specify what local files or persisted data it accesses; as an MCP tool, it would typically at least handle runtime configuration and environment variables. There is no explicit indication of broad filesystem access, over-privileged behavior, or data access disproportionate to its purpose, but the lack of documentation reduces verifiability.

The source is an official registry entry with an auditable open-source repository and updates within the last year, all of which are strong positive signals. Although community stars are low and no license is stated, there are no current supply-chain red flags such as closed source, abandonment, or suspicious distribution.