US tide predictions (NOAA, x402)

work.agentexchangePublished by agentexchange.workOfficial publisherv1.0.0Updated Nov 20, 2026

Ocean tide forecast for a US coastal point: 48 h of high/low tides from NOAA. x402, 0.01 per call.

The publisher's own server: Measured data: Claude Code and the coding-agent market

VerifiedStreamable HTTPWeb executableLocation & LifestyleData & Analytics

Overview

AI-generated overview

Remote MCP feed that returns 48-hour NOAA high and low tide forecasts for a US coastal point, paid per call via x402.

What you can do
  • Retrieve a 48-hour high/low tide forecast for a US coastal location from NOAA data.
  • Access it as one of a family of fixed public-data feeds the server exposes, alongside filings, recalls, weather alerts, Treasury and similar sources.
  • Each call is billed per request through x402 rather than through an account or API key.
When to use it
Useful when an assistant needs tide timing for a specific US coastal point, such as planning a beach visit, boating, fishing or coastal fieldwork, and a small per-call payment is acceptable.
Requirements
A remote streamable HTTP endpoint; no local runtime, package, account, environment variable or header is declared. Calls are paid through x402, so a compatible payment method is needed.
Before you install
Every call costs money (0.01 per call for tide data, 0.002 per call for the other feeds), so automated or repeated queries can accumulate charges. No authentication is declared, so payment handling happens through x402; confirm how your client authorizes spending before connecting.

Installation

In SourceWeft

  1. Open US tide predictions (NOAA, x402) in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/work.agentexchange%2Fus-tide-predictions/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "us-tide-predictions-noaa-x402": {
      "type": "http",
      "url": "https://feeds.agentexchange.work/mcp?tools=us_tide_predictions"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestNov 20, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Agentexchange integrations