Skip to content

Swiss public transport MCP server

ch.opendata/transportopendata.chstreamable-httpv1.0.0Scanned

Stations, connections and departures of Swiss public transport, with real-time delays.

4 tools: 3 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 3 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 4
  • Can send data out · 0
  • 1 finding

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Swiss public transport MCP server can do

The Swiss public transport MCP server is published by opendata.ch, a domain the MCP Registry verified. It has 4 tools. It can create or change data (3 tools: stations_nearby, connections and departures), but cannot delete data. 1 tool only reads.

4 tools bring in text other people can write (find_stations, stations_nearby, connections and 1 more).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Last scanned Nov 21, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Changes things 3Claude Code: ask
  • connectionsPublic transport connections from A to B: times, platforms, delays, changes, lines.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Public transport connections from A to B: times, platforms, delays, changes, lines.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: true
    • readOnlyHint: true
  • departuresThe departure (or arrival) board of a station, with platforms and delays.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    The departure (or arrival) board of a station, with platforms and delays.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: true
    • readOnlyHint: true
  • stations_nearbyThe stops closest to a point, with their distance in metres.Reads text others write1 finding

    Why it is in this group

    • The description's first verb is "stop": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "stations_nearby" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":true}; The description's first verb is "stop": a word for a change.

      What this check looks for
    Description, as the server wrote it
    The stops closest to a point, with their distance in metres.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: true
    • readOnlyHint: true
Only reads 1Show 1 read-only tool
  • find_stationsFind stations and stops by name.Reads text others writeNo findings

    Why it is in this group

    • The name "find_stations" says "find": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Find stations and stops by name. Returns their exact names and ids, best match first.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: true
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "stations_nearby" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":true}; The description's first verb is "stop": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http transport https://transport.opendata.ch/mcp
claude mcp add --transport http transport https://transport.opendata.ch/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__transport__find_stations"
    ],
    "ask": [
      "mcp__transport__stations_nearby",
      "mcp__transport__connections",
      "mcp__transport__departures"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as transport. Review it before you use it.

Capability tags behind 4 rules
  • mcp__transport__find_stations untrusted-input
  • mcp__transport__stations_nearby untrusted-input
  • mcp__transport__connections untrusted-input
  • mcp__transport__departures untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/ch.opendata/transport/verify?hash=2b3c180d7ea08e99791daea095728ee55e341029fe07be4d73857344f418a7c0" | jq -e '.changed == false'

Pinned hash 2b3c180d7ea0, from Nov 21, 2026, 20:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/ch.opendata/transport/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for ch.opendata/transport
[![Anlyon Radar](https://radar.anlyon.com/badge/ch.opendata/transport.svg)](https://radar.anlyon.com/servers/ch.opendata/transport)

Source: MCP Registry · repository. Synced Nov 21, 2026, 20:17 UTC.

Swiss public transport MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Swiss public transport MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 3 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Swiss public transport MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Swiss public transport MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Swiss public transport MCP server have?

4 tools: 3 write, 1 read. stations_nearby, connections, departures and find_stations.

Does the Swiss public transport MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Swiss public transport MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.