Skip to content
Back to the index

noaa-tides

pipeworx.ioInfrastructure🇺🇸

No liveness check has reached it yet; it has been in the index since 10 Oct 2026. How this is checked

Noaa Tides is an HTTP JSON-RPC MCP server exposing tools for NOAA Tides & Currents data. Developers and AI agents can query stations, metadata, tide predictions, water levels, currents, meteorological observations, and vertical datums.

Inferred · not functionally tested

WebAPICloud-managed
noaa-tides preview
Visit pipeworx.io

Overview

6 features

Purpose: Accessing NOAA tide, current, water-level, and meteorological station data through a standardized MCP endpoint.

Inferred · not functionally tested

Audience: developers building data applications and AI agents

Inferred · not functionally tested

Functions: data_extraction

Inferred · not functionally tested

Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: unknown · Self-hosting: unknown

Recorded constraints: pricing: unknown · license: Proprietary · platforms: WEB · deployment: browser, api_only, cloud_managed

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: gateway.pipeworx.io. These links do not verify the individual claims.

In the API design, testing & docs space, noaa-tides takes a focused approach. Inferred · not functionally tested: It focuses on accessing NOAA tide, current, water-level, and meteorological station data through a standardized MCP endpoint. Inferred · not functionally tested: noaa-tides is a B2B product aimed at developers building data applications and AI agents. Basis unknown · not verified: It ships for the web and API.

Pipeworx builds and maintains noaa-tides. Inferred · not functionally tested: Key capabilities include station search, station metadata, and tide predictions. Inferred · not functionally tested: Catalogued interfaces include an MCP server and a public API.

Summary written by a language model from the project’s public pages.

Tasks: Inferred · not functionally tested

  • Station search
  • Station metadata
  • Tide predictions
  • Water-level readings
  • Current readings
  • Weather observations

Topics: Inferred · not functionally tested

Tags
noaa-datatide-predictionswater-levelsmcp-server

JSON profile · Text profile · Access guide

Built with & integrations

Hosting
Cloudflare
Connectors
MCPAPI
Runs on
BrowserAPI-onlyCloud-managed
Detected from
Cloudflare
cf-ray header

Trust & compliance

Public signals
HTTPS

Indexing history

1

What PulseGate has recorded for this listing

  1. Indexed10 Oct · 00:02 UTC
    Noaa Tides seen via MCP Registry (official)
    Source: MCP Registry (official) · Open

Frequently asked questions about noaa-tides

What is noaa-tides?
Inferred · not functionally tested: Noaa-tides focuses on accessing NOAA tide, current, water-level, and meteorological station data through a standardized MCP endpoint. It is catalogued under API design, testing & docs on PulseGate.
Who is noaa-tides for?
Inferred · not functionally tested: noaa-tides is a B2B product built for developers building data applications and AI agents.
What platforms does noaa-tides run on?
Basis unknown · not verified: noaa-tides runs on the web and API.
Is noaa-tides still active?
Unverified. noaa-tides has not been re-checked since it entered the index, so there is no finding either way — and only a positive finding would say otherwise.
What projects are similar to noaa-tides?
Similar projects tracked by PulseGate include noaa-coastwatch, tides-mcp, and noaa-swpc.noaa-coastwatchtides-mcpnoaa-swpc
Who develops noaa-tides?
noaa-tides is developed by Pipeworx, based in the United States.
Does noaa-tides have an API or integrations?
Inferred · not functionally tested: Yes — noaa-tides exposes an MCP server and a public API.

Similar projects

Closest matches by what these projects do