mcp-swiss
Related Servers
Alternatives to mcp-swiss
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceAn MCP server that rolls 66 Swiss public data sources into 151 tools covering transport, weather, geodata, companies, sanctions, law, votes, tenders and statistics, with no API keys needed. Every answer is returned with licence, attribution and the exact upstream requests so results can be verified and cited.15195 npm2MIT
- AlicenseBqualityDmaintenanceMCP server exposing all major Swiss official public APIs as native tools for any MCP-compatible AI agent.3412 npmMIT
- AlicenseAqualityBmaintenanceMCP server for Swiss federal geodata -- maps, elevation, geocoding, cadastral extracts, and downloadable datasets via Swisstopo APIs.2039 PyPI12MIT
- AlicenseAqualityBmaintenanceMCP 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.1252 PyPIMIT
- AlicenseAqualityBmaintenanceMCP server for Switzerland's national metadata catalogue, enabling AI agents to discover datasets, APIs, public services, and publishers through free-text search and structured queries.1357 PyPIMIT
- AlicenseAqualityAmaintenanceMCP Server for Swiss road mobility — shared vehicles, EV charging, traffic alerts, Park & Rail, and multimodal trip planning.1547 PyPI1MIT
TDQS
Scored across 94 tools
Most tools map to distinct Swiss data domains, but there are real clusters of near-duplicates: search_opendata / search_statistics / search_real_estate_data all search catalogues, get_weather / get_ogd_recent / get_ogd_history / get_weather_history overlap on MeteoSwiss readings, and search_places / geocode / identify_location / search_map_layers all resolve locations. Descriptions usually clarify the intended boundary (e.g. get_rent_index explicitly disclaims being a rent index, get_traffic_count vs get_traffic_by_canton), which keeps it workable, but an agent must read carefully to pick correctly.
The dominant convention is snake_case verb_noun (get_vote_details, list_pollen_stations, search_companies, compare_electricity_tariffs) applied consistently across most of the 94 tools. Deviations are minor: bare verb names like geocode / reverse_geocode, and noun-first variants like buildings_near. Nothing is camelCase-mixed or chaotic.
94 tools in a single server is far past the practical ceiling; even though each contributes to a genuinely broad 'Swiss public data' scope, the surface is too large to navigate or select from reliably. This is really a federation of ~15 domain servers (weather, transit, parliament, geodata, energy, hazards) bundled into one.
Coverage across the chosen domains is unusually thorough: search plus detail pairs exist for businesses, dams, buildings, datasets, parliament affairs, votes, earthquakes, and stations, with canton/radius filters and supporting lookup tables (list_cantons, list_legal_forms, list_avalanche_regions). Gaps are mostly upstream-imposed dead ends (track_parcel and get_air_quality return only links, no live measurements) rather than missing tool patterns.