A
licenseA
qualityD
maintenanceSwiss open data MCP server — transport, weather, geodata, companies, etc,. Zero API keys.
76
227 npm
22
MIT
swiss-road-mobility-mcp
by malkreide
Related Servers
Alternatives to swiss-road-mobility-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceA zero-authentication MCP server for Swiss public transport, enabling users to query train connections, disruptions, station facilities, and plan journeys using natural language.12MIT
- AlicenseAqualityBmaintenanceMCP server for Swiss federal geodata -- maps, elevation, geocoding, cadastral extracts, and downloadable datasets via Swisstopo APIs.209MIT
- AlicenseBqualityDmaintenanceMCP server exposing all major Swiss official public APIs as native tools for any MCP-compatible AI agent.3416 npmMIT
- AlicenseAqualityAmaintenanceMCP server for Swiss electricity data from three official sources — production mix, consumption forecast, storage-lake fill, consumer price index, tariffs per municipality, and dataset discovery. Zero authentication.12MIT
- AlicenseAqualityDmaintenanceMCP server for Swiss public transport — connections, stationboards, real-time delays, and direct booking links for SBB.41MIT
TDQS
A4.2/5.0
Scored across 15 tools
Disambiguation5/5
Each tool targets a distinct aspect of Swiss road mobility: sharing, charging, traffic, counting, parking, classification, geocoding, and aggregated views. No two tools have overlapping purposes; even closely related tools (e.g., find vs search sharing, find vs status chargers) are clearly separated by their descriptions.
Naming Consistency4/5
All tools share the 'road_' prefix, which is good. However, the naming pattern is not uniform: some use verb_noun (find_sharing, classify_road) while others use noun_noun (sharing_providers, charger_status, traffic_situations). This slight inconsistency prevents a perfect score.
Tool Count5/5
With 15 tools, the server is well-scoped for its purpose—covering sharing, charging, traffic, counting, parking, classification, and geocoding. Each tool earns its place, and the count feels natural for the domain's breadth.
Completeness5/5
The tool surface appears complete for a read-only mobility data aggregation server. It covers all major phases (health check, search, status, planning, aggregation) and sub-domains, with no obvious missing operations like update or delete (which are out of scope).
Maintenance
ActivityNo data
ResponsivenessUnresponsive