io.github.cyanheads/transitland-mcp-server

The materials show a required TRANSITLAND_API_KEY, which is a sensitive credential for accessing the third-party Transitland service; if exposed, it could be abused to consume quota or make API calls on the user's behalf. TRANSITLAND_BASE_URL and MCP_LOG_LEVEL are less sensitive by themselves, but a configurable base URL could affect where requests are sent.

The functionality description clearly depends on Transitland v2 data, which normally implies outbound requests to related APIs. The materials do not list a concrete host, and TRANSITLAND_BASE_URL is configurable, so the actual egress destination cannot be confirmed from the provided facts, nor whether it could be redirected to an unexpected endpoint; there is no explicit evidence of data being sent to unrelated third parties.

The system checks indicate that this tool executes code or starts a local process, which is within the normal capability range of MCP tools. The provided materials do not show requests for system privileges beyond its stated function, nor any suspicious command execution or persistence behavior.

From the provided materials, it is not possible to confirm exactly which local files, caches, or logs it reads or writes; it is only clear that it runs locally and processes query-related data. There is no indication of broad filesystem access, browser data access, SSH keys, or other excessive permissions unrelated to transit queries, but the missing README leaves the data-handling boundaries insufficiently transparent.

It comes from the official Registry, has an open-source repository, and was updated within the last year; these are clear positive supply-chain signals. Low community stars and an undeclared license reduce adoption confidence and compliance clarity, but they do not by themselves constitute a high-risk red flag given the code is auditable.