LocalTides MCP Server

24 tools. 0 can modify or destroy data without limits.

Read-only server. Low risk, but rate limits prevent runaway API costs.

Last updated:

0 can modify or destroy data
24 read-only
24 tools total

Community server · catalogue entry verified 28/06/2026

How to control LocalTides MCP Server ↓

What LocalTides MCP Server exposes to your agents

Read (24) Write / Execute (0) Destructive / Financial (0)

What can go wrong

Even read-only tools carry cost. An agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up bills.

How to control LocalTides MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and LocalTides MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Cap read operations
{
  "get_current_predictions": {
    "limits": [
      {
        "counter": "get_current_predictions_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register LocalTides MCP Server — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON LOCALTIDES →

Instant setup, no code required.

All 24 LocalTides MCP Server tools

READ 24 tools
Read get_current_predictions Get current predictions Read get_currents Get currents data for a station Read get_extreme_water_levels Get extreme water levels and exceedance probabilities for a station Read get_high_tide_flooding_annual Get high tide flooding annual count data for a station Read get_high_tide_flooding_daily Get high tide flooding daily count data for a station Read get_high_tide_flooding_likelihoods Get high tide flooding daily likelihoods for a station Read get_high_tide_flooding_monthly Get high tide flooding monthly count data for a station Read get_high_tide_flooding_projections Get high tide flooding decadal projections for sea level rise scenarios Read get_high_tide_flooding_seasonal Get high tide flooding seasonal count data for a station Read get_meteorological_data Get meteorological data Read get_moon_phase Get moon phase information for a specific date Read get_moon_phases_range Get moon phase information for a date range Read get_next_moon_phase Get the next occurrence(s) of a specific moon phase Read get_next_sun_event Get the next occurrence(s) of a specific sun event Read get_parameter_definitions Get information about valid parameter values for NOAA API requests Read get_sea_level_trends Get sea level trends and error margins for a station Read get_station_details Get detailed information about a station Read get_stations Get list of stations Read get_sun_position Get sun position information for a specific date, time, and location Read get_sun_times Get sun rise/set and other sun event times for a specific date and location Read get_sun_times_range Get sun rise/set and other sun event times for a date range and location Read get_tide_predictions Get tide prediction data Read get_top_ten_water_levels Get top ten highest or lowest water levels for a station Read get_water_levels Get water level data for a station

Questions about LocalTides MCP Server

Is the LocalTides MCP Server MCP server safe to use without restrictions? +

The LocalTides MCP Server server is primarily read-only with 24 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the LocalTides MCP Server MCP server expose? +

24 tools across 1 categories: Read. 24 are read-only. 0 can modify, create, or delete data.

How do I enforce a policy on LocalTides MCP Server? +

Register the LocalTides MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every LocalTides MCP Server tool call.

Deterministic rules across all 24 LocalTides MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Instant setup, no code required.

24 LocalTides MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.