Skip to main content
Glama
nawazxz

gb-climate-mcp

by nawazxz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to gb-climate-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-climate

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables querying historical and future climate projections (1950–2050) for temperature and precipitation, and comparing climate models to assess agreement and uncertainty.
      22 npm
      MIT

    • weather-intelligence

      lvfast
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables normalized current weather, forecasts, alerts, location resolution, and deterministic, explainable activity-risk assessments through MCP tools.
      1
      MIT

    • 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

    • mcp-weather

      loickaczmarek
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables to interact with comprehensive weather data through the MCP protocol, including current conditions, multi-day forecasts, hourly forecasts, and geocoding.
      12 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

    A3.8/5.0

    Scored across 6 tools

    Disambiguation4/5

    Most tools target clearly distinct outputs: listing stations, daily data, rain percentiles, flood outlook, and cross-station comparison are all separable. The only mild overlap is between compare_stations and climate_trend, since both surface trends-per-decade, but compare_stations is explicitly cross-station while climate_trend is single-station, so the descriptions keep them apart.

    Naming Consistency4/5

    All names use consistent snake_case, which is good. However the verb pattern is mixed: some are verb_noun (compare_stations, list_stations, get_daily_weather) while others are noun phrases (rain_thresholds, climate_trend, flood_risk_outlook), a minor deviation from a single predictable pattern.

    Tool Count5/5

    Six tools is well-scoped for a climate data server, covering discovery, retrieval, trend analysis, thresholds, and forecasting without redundancy. Each tool earns its place.

    Completeness4/5

    The surface covers the full lifecycle well: station discovery, daily historical retrieval, long-term trends, cross-station comparison, rain thresholds, and live flood screening. Minor gaps exist (e.g. no explicit station-metadata lookup beyond list_stations, no sub-daily history), but core workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources