Skip to main content
Glama
Hug0x0

mcp-cyclone-indian-ocean

by Hug0x0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to mcp-cyclone-indian-ocean

No user-submitted related servers found.

    Related Servers

    • mcp-mayotte

      Hug0x0
      A
      license
      A
      quality
      B
      maintenance
      MCP server for Mayotte public data, vigilance, administrative references, and local risk discovery, enabling users to search datasets, list communes, and fetch official information.
      10
      MIT

    • mcp-madagascar

      Hug0x0
      A
      license
      A
      quality
      B
      maintenance
      MCP server for discovering Madagascar-focused humanitarian, weather, risk, and open-data sources, with tools to search datasets, fetch alerts, and get weather information.
      9
      MIT

    • mcp-local-risk-france

      Hug0x0
      A
      license
      A
      quality
      B
      maintenance
      MCP server for discovering French local natural, technological, and industrial risks at commune level using Géorisques, administrative references, and open risk datasets. It provides tools to query risk sources, datasets, and commune briefs.
      12
      MIT

    • mcp-reunion

      Hug0x0
      A
      license
      A
      quality
      A
      maintenance
      MCP server providing 96 tools across 21 modules for La Réunion (French overseas region) open data: economy, demographics, geography, transport, health, education, elections, tourism, housing, and environment. Powered by data.regionreunion.com and data.gouv.fr.
      99
      31 npm
      2
      MIT

    • windscout-mcp

      jwillert
      A
      license
      A
      quality
      C
      maintenance
      MCP server for wind forecasts, live measurements, wave forecasts, and tides, enabling kite and surf spot checks via AI assistants.
      5
      4 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/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of cyclone monitoring: sources, current activity, archives, vigilance links, alert levels, commune exposure, commune listings, and notable events. No two tools overlap in purpose, making selection straightforward.

    Naming Consistency5/5

    All tool names follow the consistent pattern 'cyclone_' plus a verb_noun descriptor (e.g., get_sources, explain_alert_level, list_communes). The naming is uniform and predictable.

    Tool Count5/5

    With 8 tools, the set is well-scoped for a specialized cyclone monitoring server. Each tool serves a clear function without redundancy or unnecessary bloat.

    Completeness4/5

    The surface covers core activities: checking current conditions, historical archives, source listing, vigilance alerts, alert level explanations, and geographic exposure estimation. Minor gaps exist (e.g., no direct forecast fetch), but the provided tools cover the primary workflows without dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources