MCP server for Swiss public transport data from opentransportdata.swiss. Provides journey planning (OJP), real-time departures, disruptions (SIRI-SX), occupancy forecasts, ticket prices (OJP Fare), train formations, stop search, and dataset catalog access via the Model Context Protocol.
Strong server with well-structured tools, clear naming conventions, and comprehensive parameter documentation. Most tools have proper input schemas and descriptions. Tool names follow verb_noun pattern (transport_search_*, transport_get_*, get_transport_*). Parameter descriptions are detailed with constraints (min/max, enums). However, output schemas are not explicitly documented in the source, and some tools (5-11) are inferred from audit files rather than directly visible in the main server.py, capping their individual scores at 50. Error handling and security controls are solid with tool integrity verification (SEC-022) and no secrets in parameters. Average tool score is 72, indicating good production readiness with minor documentation gaps.
Check the status and configuration of available transport APIs.
Get ticket prices for a journey using OJP Fare API.
Get train composition and car information for a specific train.
Get occupancy forecast for a specific train connection.
Get details and download links for a specific transport dataset.
Get current disruptions and service notices for Swiss public transport.
List available transport datasets from the open transport data catalog.
Tools 5 - 11 (get_transport_disruptions through get_transport_dataset) are defined in audit/findings/_generator.py rather than main server.py source.
Output schemas are not explicitly documented in visible source code. The rubric baseline shows 100% of A+ tools have documented return types. While the server likely returns structured data (inferred from tool names and descriptions), explicit schema definitions with fields and types are not visible in the provided source excerpt.
Inferred effective spec: 2025-06-18+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 68 | 2025-06-18+ | v2 |
Get real-time departures for a stop.
Plan a journey from origin to destination with OJP journey planner.
Search for stops/stations by name and find their IDs for use in other tools.
Find nearby stops by latitude and longitude coordinates.
Tools 5 - 8 have parameter descriptions that could be more specific about expected formats and ranges. For example, get_train_occupancy 'direction' param lacks guidance on valid values (e.g., destination city names, line terminuses).
check_transport_api_status tool accepts empty input but description is vague ('Check the status and configuration of available transport APIs'). Unclear what the LLM should expect in response or when to call this vs. other tools. Should clarify response structure and use case.
No explicit error handling guidance visible in tool definitions. Rubric pattern:recovery-guide requires error responses to tell the LLM what to do next. For example, if transport_search_stop returns no results or invalid stop_id is passed to transport_get_departures, the LLM needs guidance on recovery (retry with different query, call search_stop first, etc.).