A
licenseA
qualityF
maintenanceMCP server that connects AI models to Swiss federal geodata, offering tools for spatial queries like layer discovery, coordinate identification, building zones, and terrain heights.
9
MIT
swisstopo-mcp
by malkreide
Related Servers
Alternatives to swisstopo-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceSwiss open data MCP server — transport, weather, geodata, companies, etc,. Zero API keys.76275 npm22MIT
- AlicenseBqualityDmaintenanceMCP server exposing all major Swiss official public APIs as native tools for any MCP-compatible AI agent.342 npmMIT
- AlicenseAqualityDmaintenanceAn unofficial MCP server for accessing Swiss Federal Statistical Office (BFS) data.81MIT
- AlicenseAqualityAmaintenanceMCP 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.13MIT
- AlicenseAqualityAmaintenanceMCP server for querying Swiss environmental research data from WSL/EnviDat, including forest, snow, avalanche, and biodiversity datasets. No API key required.10MIT
TDQS
A4/5.0
Scored across 20 tools
Disambiguation3/5
Several tool pairs have overlapping purposes, such as get_oereb_extract vs oereb_at, get_egrid vs oereb_at, and find_commune vs lookup_postal_code vs search_address. The descriptions do clarify when to use each, but an agent may misselect based on names alone. More than one or two tools could be confused, so this is not mostly distinct.
Naming Consistency3/5
All tools share the swisstopo_ prefix, but the naming convention is mixed: verb-first names (get_height, search_geodata), noun-at names (zoning_at, municipality_at), and noun phrases (map_url, elevation_profile) are all present. This is a readable but inconsistent pattern, not a uniform verb_noun structure.
Tool Count4/5
With 20 tools, the server is on the heavier side but still reasonable for the broad Swiss geospatial domain it covers. Each tool addresses a distinct need (geocoding, elevation, map query, property restrictions, data download), so the count is only slightly above the ideal range.
Completeness5/5
The tool set covers the full lifecycle of common geospatial workflows: geocoding, reverse geocoding, coordinate conversion, elevation point/profile, map layer query, zoning/municipality lookups, EGRID/OEREB property information, STAC search/download, and address/PLZ/commune resolution. No critical operations appear to be missing for the announced purpose.
Maintenance
ActivityActive
ResponsivenessUnresponsive