io.github.malkreide/swiss-transport-mcp
PYPI · SWISS-TRANSPORT-MCP · SCANNED SEP 20
OJP 2.0 journey planning, SIRI-SX disruptions, occupancy, fares, train formation
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 32 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency35
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (MIT License) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 51 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1964 tokens (~151/item across 13 items; 11 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the io.github.malkreide/swiss-transport-mcp server?
io.github.malkreide/swiss-transport-mcp runs locally as a PyPI package, launched with uvx swiss-transport-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · swiss-transport-mcp
claude mcp add malkreide-swiss-transport-mcp -- uvx swiss-transport-mcp
{
"mcpServers": {
"malkreide-swiss-transport-mcp": {
"command": "uvx",
"args": [
"swiss-transport-mcp"
]
}
}
} {
"servers": {
"malkreide-swiss-transport-mcp": {
"command": "uvx",
"args": [
"swiss-transport-mcp"
]
}
}
} codex mcp add malkreide-swiss-transport-mcp -- uvx swiss-transport-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"malkreide-swiss-transport-mcp": {
"type": "local",
"command": [
"uvx",
"swiss-transport-mcp"
],
"enabled": true
}
}
} openclaw mcp add malkreide-swiss-transport-mcp --command uvx --arg swiss-transport-mcp
mcp_servers:
malkreide-swiss-transport-mcp:
command: "uvx"
args: ["swiss-transport-mcp"] {
"McpServers": {
"malkreide-swiss-transport-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"swiss-transport-mcp"
]
}
}
} assistant mcp add malkreide-swiss-transport-mcp -t stdio -c uvx -a swiss-transport-mcp
{
"mcpServers": {
"malkreide-swiss-transport-mcp": {
"command": "uvx",
"args": [
"swiss-transport-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 −3
- Stability: pass → 0.80 functional
- 19 Sept 26 +1
- Stability: 0.97 → pass security
- 17 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 16 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 15 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 14 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 13 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 12 Sept 26 +12
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.77 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed pypi/swiss-transport-mcp@0.4.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 32 packages
| Packages resolved | 32 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_transport_api_status ~52
Prüft den Verbindungsstatus aller konfigurierten Transport-APIs. Zeigt an, welche APIs verfügbar sind, ob die API-Keys gültig sind und ob die Dienste erreichbar sind.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_ticket_price ~317
Ticketpreise für eine ÖV-Verbindung in der Schweiz abfragen. Berechnet den Fahrpreis für eine Verbindung inklusive Routeninformation. Zeigt reguläre Tarife an. Rabatte (Halbtax, GA) sind möglicherweise nicht vollständig berücksichtigt. Args: origin: Abfahrtsort (z.B. "Zürich HB", "Wädenswil", "Bern") destination: Ankunftsort (z.B. "Bern", "Luzern", "Basel SBB") departure_time: Abfahrtszeit im Format YYYY-MM-DDTHH:MM (z.B. "2026-03-01T08:00"). Standard: jetzt. travel_class: Reiseklasse. "first" = 1. Klasse, "second" = 2. Klasse. Beispiele: - Einfache Preisabfrage: get_ticket_price(origin="Zürich HB", destination="Bern") - Mit Zeitangabe: get_ticket_price(origin="Wädenswil", destination="Luzern", departure_time="2026-03-01T08:00") - 1. Klasse: get_ticket_price(origin="Basel SBB", destination="Genf", travel_class="first") Hinweis: Für verbindliche Preise immer sbb.ch oder den Schalter konsultieren.
| Name | Type | Req | Description |
|---|---|---|---|
| departure_time | string | – | – |
| destination | string | yes | – |
| origin | string | yes | – |
| travel_class | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_train_composition ~391
Zugzusammensetzung und Wagenreihung für einen Schweizer Zug abrufen. Zeigt die Wagenreihung, Klassen, Sektoren, Ausstattung (Rollstuhlplatz, Velohaken, Speisewagen, Familienzone) und Gleisbelegung an. Args: train_number: Zugnummer (z.B. "2806", "1009", "708"). Nur die Nummer, ohne Zugtyp-Präfix. railway_company: Eisenbahnunternehmen (EVU). Erlaubt: SBBP (SBB), BLSP (BLS), RhB (Rhätische Bahn), SOB (Südostbahn), THURBO, TPF, TRN, MBC, OeBB, VDBB, ZB. operation_date: Betriebstag YYYY-MM-DD. Standard: heute. Wichtig: Stop-based nur für HEUTE verfügbar. show_details: Detailgrad. "stop_based" = kompakt (empfohlen), "vehicle_based" = pro Fahrzeug, "full" = alles. Beispiele: - SBB-Zug: get_train_composition(train_number="1009") - BLS-Zug: get_train_composition(train_number="2806", railway_company="BLSP") - Detailliert: get_train_composition(train_number="708", show_details="vehicle_based") Typische Fragen, die damit beantwortet werden können: - "Hat der IC nach Bern einen Speisewagen?" - "Wo kann ich mit dem Rollstuhl einsteigen?" - "In welchem Sektor hält die 1. Klasse?" - "Gibt es Veloplätze im Zug?"
| Name | Type | Req | Description |
|---|---|---|---|
| operation_date | string | – | – |
| railway_company | string | – | – |
| show_details | string | – | – |
| train_number | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_train_occupancy ~351
Auslastungsprognose für Schweizer Züge abrufen. Zeigt, wie voll ein bestimmter Zug voraussichtlich sein wird, aufgeteilt nach 1. und 2. Klasse pro Streckenabschnitt. Auslastungsstufen: wenig belegt, mässig belegt, nur Stehplätze. Zwei Abfragemodi: 1. Nach Zugnummer: train_number + operator angeben 2. Nach Strecke: departure_station + arrival_station angeben Args: train_number: Zugnummer (z.B. "1009", "IC 708"). Zugtyp-Präfixe werden automatisch entfernt. departure_station: Abfahrtsort für Streckensuche (z.B. "Zürich HB") arrival_station: Ankunftsort für Streckensuche (z.B. "Bern") operation_date: Betriebstag YYYY-MM-DD (Standard: heute). Prognosen sind bis 3 Monate voraus verfügbar. operator: Betreiber-Code. "11"=SBB, "33"=BLS, "65"=Thurbo, "82"=SOB. Beispiele: - Bestimmter Zug: get_train_occupancy(train_number="1009") - BLS-Zug: get_train_occupancy(train_number="2806", operator="33") - Strecke: get_train_occupancy(departure_station="Zürich HB", arrival_station="Bern")
| Name | Type | Req | Description |
|---|---|---|---|
| arrival_station | string | – | – |
| departure_station | string | – | – |
| operation_date | string | – | – |
| operator | string | – | – |
| train_number | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_transport_disruptions ~239
Aktuelle Störungsmeldungen im Schweizer öffentlichen Verkehr abrufen. Liefert Informationen zu Zugausfällen, Verspätungen, Gleisänderungen, Streckensperrungen und anderen Betriebsstörungen. Args: filter_text: Suchbegriff zum Filtern (z.B. "Zürich", "S-Bahn", "IC 1", "Bern-Thun"). Leer = alle Störungen. language: Sprache der Meldungen. DE (Deutsch), FR (Französisch), IT (Italienisch), EN (Englisch). max_results: Maximale Anzahl Ergebnisse (1-50). Standard: 15. Beispiele: - Alle aktuellen Störungen: get_transport_disruptions() - Störungen in Zürich: get_transport_disruptions(filter_text="Zürich") - S-Bahn Störungen: get_transport_disruptions(filter_text="S-Bahn") - Strecke prüfen: get_transport_disruptions(filter_text="Bern")
| Name | Type | Req | Description |
|---|---|---|---|
| filter_text | string | – | – |
| language | string | – | – |
| max_results | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
transport_departures ~79
Get upcoming departures or arrivals at a Swiss public transport stop. Shows real-time information including delays when available. Like a digital departure board at a train station. Use transport_search_stop first to get the stop_id. Returns: Departures with line, destination, scheduled time, real-time time, delay, and platform.
| Name | Type | Req | Description |
|---|---|---|---|
| params | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | – |
| departures | array | – | – |
| hint | – | – | – |
| message | – | – | – |
| stop_id | – | – | – |
| stop_name | – | – | – |
| type | – | – | – |
No examples provided.
transport_get_dataset ~69
Get full details of a specific transport dataset. Returns metadata, description, all available resources (files/APIs) with download URLs and formats. Use transport_search_datasets first to find the dataset ID. Returns: Full dataset metadata, resources with URLs, and format info.
| Name | Type | Req | Description |
|---|---|---|---|
| params | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| description | – | – | – |
| id | – | – | – |
| last_modified | – | – | – |
| license | – | – | – |
| message | – | – | – |
| organization | – | – | – |
| resources | array | – | – |
| tags | array | – | – |
| title | – | – | – |
| url | – | – | – |
No examples provided.
transport_nearby_stops ~79
Find public transport stops near a geographic location. Useful for finding stops near a school, address, or point of interest. Swiss coordinates only (lat 45–48.5, lon 5.5–10.8). Returns: Nearby stops with id, name, coordinates, and distance info.
| Name | Type | Req | Description |
|---|---|---|---|
| params | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | – |
| hint | – | – | – |
| latitude | – | – | – |
| longitude | – | – | – |
| message | – | – | – |
| nearby_stops | array | – | – |
No examples provided.
transport_search_datasets ~76
Search the Swiss transport open data catalog (~90 datasets). Find datasets about timetables, real-time data, GTFS feeds, accessibility info, traffic counters, and more from opentransportdata.swiss. Returns: Matching datasets with name, description, formats, and download URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| params | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| datasets | array | – | – |
| hint | – | – | – |
| message | – | – | – |
| query | – | – | – |
| showing | integer | – | – |
| total_found | integer | – | – |
No examples provided.
transport_search_stop ~75
Search for Swiss public transport stops and stations by name. Searches across all Swiss public transport stops (train stations, tram/bus stops, boat stations). Returns stop IDs needed for transport_departures and transport_trip_plan. Returns: Matching stops with id, name, coordinates, and transport modes.
| Name | Type | Req | Description |
|---|---|---|---|
| params | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | – |
| hint | – | – | – |
| message | – | – | – |
| query | – | – | – |
| stops | array | – | – |
No examples provided.
transport_trip_plan ~106
Plan a journey between two locations in Switzerland. Works like the SBB app: enter origin and destination (stop IDs or place names), get multiple trip options with transfers, durations, and transport modes. For best results, use stop IDs from transport_search_stop. Place names (addresses) also work but may be slower. Returns: Trip options, each with legs (individual journey segments), total duration, number of transfers, and transport modes used.
| Name | Type | Req | Description |
|---|---|---|---|
| params | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | – |
| destination | – | – | – |
| hint | – | – | – |
| message | – | – | – |
| origin | – | – | – |
| trips | array | – | – |
No examples provided.
What is the io.github.malkreide/swiss-transport-mcp server?
io.github.malkreide/swiss-transport-mcp is listed in the public MCP registry as io.github.malkreide/swiss-transport-mcp. OJP 2.0 journey planning, SIRI-SX disruptions, occupancy, fares, train formation. This page covers its PyPI package (swiss-transport-mcp).
Is the io.github.malkreide/swiss-transport-mcp server safe to use?
io.github.malkreide/swiss-transport-mcp scores 63 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.malkreide/swiss-transport-mcp server expose?
io.github.malkreide/swiss-transport-mcp exposes 11 tools: transport_search_stop, transport_nearby_stops, transport_departures, transport_trip_plan, transport_search_datasets, and 6 more. Their descriptions and schemas cost roughly 1,834 tokens of context every time the server is loaded.
Is the io.github.malkreide/swiss-transport-mcp server still maintained?
io.github.malkreide/swiss-transport-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.