io.github.malkreide/swiss-transport-mcp

The material explicitly states that no keys or environment variables are required. No API token, account password, or other sensitive credential is requested, so credential exposure and abuse risk appears low based on the provided facts.

Although no remote endpoint is declared, the described functionality—OJP 2.0 journey planning, SIRI-SX disruptions, fares, and train formation—normally implies outbound requests to transport data services. The material does not list concrete domains, data flows, or whether user queries are transmitted, so the actual egress destinations should be verified.

The system flags this tool as executes-code, meaning it runs locally as a process and executes its implementation code. This is normal for an MCP tool; the provided material shows no concrete red flags such as unusual system privileges, persistence mechanisms, or unrelated high-risk operations.

The material does not specify which local files, databases, or other resources it can read or write, and it declares no extra filesystem permissions. There is not enough evidence to claim overbroad access, but as a locally running MCP service it may still access whatever context and input the host grants, so restricting its runtime account and accessible directories is advisable.

The supply-chain signals are overall positive: it is listed in the official registry, has an open-source repository, and was updated within the last year, all of which reduce risk. However, the README is absent, the license is unspecified, and community adoption is currently very low (0 stars), so transparency and governance are only moderate; reviewing the source and dependency list before use is recommended.