io.github.malkreide/zurich-opendata-mcp

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

The description suggests functionality around Zurich open data (weather, air quality, parking, geodata, etc.), which typically implies access to related public data sources. Although no specific remote hosts are listed in the materials and no endpoint is provided in the checks, the function implies some network access. No red flag is visible for exfiltration to unknown or unrelated endpoints.

The system marks this tool as executes-code, indicating it runs or executes code locally as an MCP component. This is a normal capability for such tools; the materials do not show requests for unusual system privileges, unrelated execution behavior, or suspicious execution chains.

The available materials do not state any need to read or write specific local files, databases, or highly sensitive resources, and no README is available to define actual data access boundaries. As an MCP tool, some runtime data exposure should be assumed by default, but there is no evidence that its access scope exceeds what would be needed for city open data queries.

It comes from the official Registry, the repository is open source and auditable, and it has been updated within the last year—these are all positive signals that reduce risk. Community adoption is low (0 stars) and the license is unspecified, which suggests limited ecosystem maturity, but without other red flags this is better assessed as low risk rather than high risk.