Skip to main content
Glama
malkreide

swiss-environment-mcp

by malkreide
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to swiss-environment-mcp

No user-submitted related servers found.

    Related Servers

    • meteoswiss-mcp

      malkreide
      A
      license
      A
      quality
      A
      maintenance
      Enables AI models to access Swiss weather and climate data from MeteoSwiss, including current observations, forecasts, and warnings.
      6
      48 PyPI
      MIT

    • swiss-energy-mcp

      malkreide
      A
      license
      A
      quality
      A
      maintenance
      Enables AI assistants to access structured, location-based Swiss energy infrastructure data, including power plants, wind turbines, solar roof potential, and Energiestadt labels, via public APIs without authentication.
      10
      MIT

    • mcp-i14y

      fgouzi
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects AI assistants to the Swiss I14Y Interoperability Platform, enabling natural language exploration of government datasets, APIs, codelists, and public services.
      MIT
    • jiskta-mcp by Jiskta

      jiskta-mcpofficial

      Jiskta
      A
      license
      A
      quality
      F
      maintenance
      Provides AI assistants with direct access to historical air quality, ERA5 meteorology, water risk, geocoding, and industrial facility data via the Jiskta API.
      10
      MIT

    • @pipeworx/mcp-meteoswiss

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables discovery and direct access to Swiss weather and federal geodata from MeteoSwiss and swisstopo, including station search, collection browsing, and direct download URLs for CSV, GeoTIFF, and NetCDF assets.
      262 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 21 tools

    Disambiguation4/5

    Tools are organized into clear domain families (air, hydro, snow, noise, hunting, open data) with distinct list/current/detail/check roles, and cross-references in descriptions reduce risk of misselection. The main ambiguity is between env_hazard_overview and env_hazard_regions, which are both non-data routing tools, and env_hydro_history's name implies historical data while it only returns a current value and pointers.

    Naming Consistency5/5

    All tools consistently use the env_ prefix with snake_case and a predictable domain+resource pattern, e.g. env_nabel_stations/env_nabel_current, env_hydro_stations/env_hydro_current, env_bafu_datasets/env_bafu_dataset_detail. Parallel suffixes like _current, _check, and _detail make the set highly navigable.

    Tool Count3/5

    21 tools is at the heavy end of the range, though the broad Swiss-environment scope gives most tools a distinct purpose. The count is inflated by meta-tools like env_hazard_overview and env_hazard_regions, which route rather than retrieve data, and could potentially be consolidated.

    Completeness3/5

    The set covers the major advertised domains: air, water, snow, natural hazards, noise, hunting, and open data. However, env_nabel_current returns only metadata and download links rather than actual air-quality values, and env_hydro_history explicitly cannot deliver true historical time series, leaving notable gaps for common data retrieval workflows.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources