Skip to main content
Glama
evanfoglia

Beach Safety MCP

by evanfoglia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Beach Safety MCP

No user-submitted related servers found.

    Related Servers

    • Surf Forecast MCP

      lucasinocencio1
      F
      license
      Not graded
      quality
      C
      maintenance
      Provides surf forecast data including swell height, period, direction, and wind conditions for any location worldwide using the Open-Meteo Marine API. It also includes tools to find the best day to surf and integrates with MCP clients via a Python server.
      20
      -

    • shouldigo-surf-mcp

      orlench
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for real-time surf conditions at 5,000+ beaches worldwide. Enables checking surf conditions, finding nearest spots, and listing spots via natural language.
      22 npm
      1
      MIT

    • Weather MCP Server

      ajayamal
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides weather forecasts and active alerts for US locations using the National Weather Service API. It supports both local stdio and remote HTTP/SSE transport modes for flexible integration with MCP clients.
      55 npm
      GPL 3.0

    • MCP Surf Forecast

      luisaugustomachadomoretto
      F
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that provides real-time surf intelligence, including wave quality scoring, beach discovery, session planning, and forecast analysis across 12+ global data sources. It turns AI assistants into surf-savvy copilots for finding the perfect wave.
      1
      -
    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 4 tools

    Disambiguation4/5

    get_beach_report, get_surf_forecast, and get_uv_forecast have distinct, well-explained scopes with explicit guidance on when to use each. The main ambiguity is get_beach_json vs get_beach_report, which return the same data in different formats, so an agent could trivially misselect between them.

    Naming Consistency5/5

    All four tools follow a clean get_<noun>_<format> snake_case pattern (get_beach_json, get_beach_report, get_surf_forecast, get_uv_forecast). Naming is fully predictable and consistent.

    Tool Count5/5

    Four tightly scoped tools easily fit the beach safety domain, and each earns its place (full report, JSON variant, surf focus, UV focus). No bloat or missing core capability at this count.

    Completeness4/5

    Coverage of conditions, surf, and UV is solid for a beach safety surface, but tide tables, water quality, and hazard advisories are absent. These are minor gaps an agent can work around but are relevant for full beach safety.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources