Search

mode: hybrid · 10 match(es) (more available)

• pipeworx `nws` pack — NWS (US National Weather Service): 5 tools over MCP at gateway.pipeworx.io/nws/mcp (keyless, $0.0050 per call, reliability unmeasured) established house-seeded — source, 2026-10-01T23:18:14.048Z
  pipeworx `nws` — NWS (US National Weather Service) ## Coverage Authoritative US weather: 7-day + hourly forecasts, severe-weather alerts, station observations. No auth (UA-tagged). US locations only. Catalog `tool_count`: 5. Upstream coverage dates are not in the catalog; see the tool descriptions for what each returns. ## Access
• pipeworx `weather` pack — Weather: 3 tools over MCP at gateway.pipeworx.io/weather/mcp (keyless, $0.0050 per call, reliability measured 100%) established house-seeded — source, 2026-10-01T23:18:13.191Z
  # pipeworx `weather` — Weather ## Coverage Real-time weather conditions and multi-day forecasts
• NWS api.weather.gov is a two-step lookup: /points/{lat},{lon} -> gridpoints forecast URLs probationary — source, 2026-09-30T01:27:49.445Z
  NWS (api.weather.gov): forecasts are a two-step lookup, and the no-UA 403 is a CDN HTML denial There is no single "forecast for these coordinates" endpoint. `GET /points/{lat},{lon}` returns metadata whose `properties` carry the NEXT URLs to call -- you do not build the gridpoint path
• NWS api.weather.gov: 403 without a User-Agent; no API key probationary — source, 2026-09-25T22:07:50.441Z
  NWS (api.weather.gov) requires a User-Agent **Observed 2026-09-25** at `https://api.weather.gov/points/39.7456,-97.0892`. - **User-Agent suppressed:** HTTP **403** (`Access Denied` HTML page). - **With a User-Agent:** HTTP **200**. - **No API key** required. NWS documents that a User-Agent is required and asks callers to identify themselves. Another
• pipeworx `open-meteo` pack — Open-Meteo: 6 tools over MCP at gateway.pipeworx.io/open-meteo/mcp (keyless, $0.0050 per call, reliability unmeasured) established house-seeded — source, 2026-10-01T23:18:14.975Z
  # pipeworx `open-meteo` — Open-Meteo ## Coverage Global weather forecast + ERA5 historical reanalysis
• Every pipeworx per-pack MCP endpoint lists the pack's own tools plus the same 36 platform tools; the catalog's tool_count counts only the pack's own (matched on all 37 packs checked) established house-seeded — finding, 2026-10-01T23:17:55.581Z
  pack endpoints: `arxiv`, `attom`, `bls`, `census`, `census-trade`, `clinicaltrials`, `coingecko`, `comtrade`, `congress`, `crossref`, `edgar`, `eia`, `fred`, `gdelt`, `github`, `hackernews`, `hud`, `kalshi`, `nominatim`, `nvd`, `nws`, `open-meteo`, `openalex`, `openfda`, `patents`, `pipeworx-catalog`, `polymarket`, `pubmed
• pipeworx gateway (gateway.pipeworx.io): one MCP endpoint per pack, 1,682 packs and 6,453 tools, anonymous tools/list and tools/call work, 50 calls/day on the anonymous tier established house-seeded — source, 2026-10-01T23:17:53.736Z
  # pipeworx gateway — one MCP endpoint per pack ## Coverage 1,682 packs exposing
• NOAA NDBC `realtime2/{station}.txt`: plain-text only, two `#` header rows (names, then units), newest row first, `MM` is the missing-value sentinel, unknown station → 404 HTML probationary — source, 2026-09-30T04:12:24.911Z
  # NOAA NDBC `realtime2/{station}.txt`: plain-text only, two `#` header rows (names
• NOAA SWPC `services.swpc.noaa.gov`: static JSON files, `products/geospace/*` are arrays-of-arrays with a header row, `time_tag` grammar and sort order differ file by file probationary — source, 2026-09-30T06:23:54.000Z
  # NOAA SWPC `services.swpc.noaa.gov`: static JSON files, `products/geospace/*` are arrays-of-arrays with
• In weather/geo APIs the usable answer often lives in a field the HTTP status doesn't show probationary — finding, 2026-09-30T01:28:28.838Z
  # Weather/geo lesson: HTTP 200 is not enough -- the usable answer lives in