Skip to content
Back to the index

noaa-coastwatch

pipeworx.ioInfrastructure🇺🇸

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

Noaa Coastwatch is an MCP server that exposes tools for searching NOAA CoastWatch's ERDDAP catalogue, inspecting dataset metadata, and querying buoy and station time series. It is intended for developers and researchers building data workflows that use ocean satellite and buoy observations.

Inferred · not functionally tested

WebAPICloud-managed
noaa-coastwatch preview
Visit pipeworx.io

Overview

5 features

Purpose: Finding dataset identifiers and querying NOAA CoastWatch ocean satellite and buoy data programmatically.

Inferred · not functionally tested

Audience: developers and ocean data researchers

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.

noaa-coastwatch is an API design, testing & docs project. Inferred · not functionally tested: It focuses on finding dataset identifiers and querying NOAA CoastWatch ocean satellite and buoy data programmatically. Inferred · not functionally tested: noaa-coastwatch is a B2B product aimed at developers and ocean data researchers. Basis unknown · not verified: It ships for the web and API.

It is developed by Pipeworx (United States). Inferred · not functionally tested: Key capabilities include dataset search, dataset metadata, and tabledap queries. 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

  • Dataset search
  • Dataset metadata
  • Tabledap queries
  • Buoy observations
  • Satellite datasets

Topics: Inferred · not functionally tested

Tags
noaa-dataocean-datasetserddapmcp-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 Coastwatch seen via MCP Registry (official)
    Source: MCP Registry (official) · Open

Frequently asked questions about noaa-coastwatch

What does noaa-coastwatch do?
Inferred · not functionally tested: Noaa-coastwatch focuses on finding dataset identifiers and querying NOAA CoastWatch ocean satellite and buoy data programmatically. It is catalogued under API design, testing & docs on PulseGate.
Who is noaa-coastwatch for?
Inferred · not functionally tested: noaa-coastwatch is a B2B product built for developers and ocean data researchers.
What platforms does noaa-coastwatch run on?
Basis unknown · not verified: noaa-coastwatch runs on the web and API.
Is noaa-coastwatch still active?
Unverified. noaa-coastwatch 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 are alternatives to noaa-coastwatch?
Similar projects tracked by PulseGate include noaa-swpc, noaa-tides, and noaa-spc.noaa-swpcnoaa-tidesnoaa-spc
Who makes noaa-coastwatch?
noaa-coastwatch is developed by Pipeworx, based in the United States.
Does noaa-coastwatch have an API or integrations?
Inferred · not functionally tested: Yes — noaa-coastwatch exposes an MCP server and a public API.

Similar projects

Closest matches by what these projects do