coops.tides.predictions
Get predicted high and low tide times and heights for any NOAA CO-OPS tide gauge station in the US, Puerto Rico, Pacific Islands, and Great Lakes. Returns a chronological list of high (H) and low (L) tides with UTC timestamps and water heights. Specify a station_id (e.g. 8443970 for Boston, 94142...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/coops.tides.predictions.md
What coops.tides.predictions does on Apibase
AI agents call coops.tides.predictions to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
datum | string | — | Vertical datum for water height measurements. MLLW (Mean Lower Low Water) is the chart datum used for nautical charts. MSL = Mean Sea Level. Defaults to MLLW. |
limit | integer | — | Maximum number of tide predictions to return (1–500). Defaults to 100. A 7-day window typically has 28 high/low tides. |
units | string | — | Unit system for water heights. english = feet, metric = meters. Defaults to english. |
end_date | string | — | End date for tide predictions in YYYY-MM-DD or YYYYMMDD format (e.g. 2025-07-11). Defaults to 7 days from today. Maximum range: 366 days. |
begin_date | string | — | Start date for tide predictions in YYYY-MM-DD or YYYYMMDD format (e.g. 2025-07-04). Defaults to today. Maximum range: 366 days. |
station_id | string | Yes | NOAA CO-OPS station ID (4–7 digits, e.g. 8443970 for Boston MA). Find station IDs with the coops.tides.stations tool. |
Parameters from the server's own tool schema.
Why coops.tides.predictions is rated Low
Retrieves publicly available tide prediction data with no data modification, deletion, or external side effects.
From the tool's definition Get predicted high and low tide times and heights for any NOAA CO-OPS tide gauge station.
Attacks that exploit this kind of access
The rule that runs coops.tides.predictions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For coops.tides.predictions, this is the rule to start with:
coops.tides.predictions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every coops.tides.predictions call is checked against it from then on.
Questions about coops.tides.predictions
Get predicted high and low tide times and heights for any NOAA CO-OPS tide gauge station in the US, Puerto Rico, Pacific Islands, and Great Lakes. Returns a chronological list of high (H) and low (L) tides with UTC timestamps and water heights. Specify a station_id (e.g. 8443970 for Boston, 9414290 for San Francisco, 8518750 for New York) and optional date range (default: next 7 days). Datum defaults to MLLW (Mean Lower Low Water) — the reference datum used on NOAA nautical charts. Data is generated from harmonic tide predictions. Useful for sailing, fishing, coastal engineering, and flood planning. Source: NOAA Center for Operational Oceanographic Products and Services (CO-OPS) — tidesandcurrents.noaa.gov. No auth, US Gov public domain. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
coops.tides.predictions accepts 6 parameters: datum, limit, units, end_date, begin_date, station_id. Required: station_id. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for coops.tides.predictions: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Apibase. Nothing to install.
coops.tides.predictions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the coops.tides.predictions rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for coops.tides.predictions. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
coops.tides.predictions is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue