Skip to main content
Glama
nabossha

LandiWetter MCP Server

by nabossha
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to LandiWetter MCP Server

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

    • MeteoSwiss MCP Server

      eins78
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides access to official MeteoSwiss weather data, including regional reports, daily forecasts, and website search functionality across multiple languages. It enables AI assistants to retrieve real-time weather information and documentation from MeteoSwiss using the Model Context Protocol.
      3
      Creative Commons Zero v1.0 Universal

    • meteo-swiss-mcp

      cuolm
      A
      license
      A
      quality
      A
      maintenance
      Exposes Swiss weather forecast data as MCP tools, including rainfall, sunshine, temperature, wind, and more, with local caching.
      8
      1
      Apache 2.0

    • @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

    • foehn

      kayhendriksen
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for querying MeteoSwiss open weather data, providing access to station data, forecasts, radar composites, and more via natural language.
      70 PyPI
      44
      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

    D1.7/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: getWeatherForecast retrieves weather data, while searchLocation finds geographic locations. There is no overlap or ambiguity between these functions, making it easy for an agent to select the correct tool based on the task.

    Naming Consistency4/5

    Both tools use a verb_noun pattern (getWeatherForecast and searchLocation), which is consistent and predictable. The minor deviation is the use of camelCase instead of snake_case, but this does not hinder readability or coherence within the set.

    Tool Count2/5

    With only 2 tools, the server feels thin for a weather and location domain. While it covers basic retrieval and search, it lacks essential operations like updating preferences, handling alerts, or managing saved locations, making the scope appear incomplete and underdeveloped.

    Completeness2/5

    Inferring the domain as weather and location services, the tool set is severely incomplete. It only provides forecast retrieval and location search, missing critical operations such as current weather data, historical forecasts, location management, or user-specific configurations, which are typical for such services.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources