Skip to main content
Glama

Server Details

NWS MCP — US National Weather Service (no auth)

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
41.9% over 41 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-nws
GitHub Stars
0
Server Listing
@pipeworx/nws

TDQS

A3.6/5.0

Scored across 41 tools

Disambiguation2/5

Several tools are near-interchangeable: ask_pipeworx and ask_pipeworx_beta are explicitly identical today, and ask_pipeworx_grounded reuses the same router with a different output contract. The polymarket family (bet_research, polymarket_edges, polymarket_arbitrage, polymarket_kalshi_spread) and company/entity lookup family also have overlapping entry points, so an agent can easily select the wrong one.

Naming Consistency3/5

Names are readable snake_case and prefix groups like get_*, polymarket_*, ask_*, and resolution_* provide some structure. However conventions are mixed: many tool names are not verb_noun, and product-specific names like ask_pipeworx_beta, kalshi_weather_edge, and generate_llms_txt break the pattern set by get_forecast, validate_claim, and scan_dependency.

Tool Count2/5

At 41 tools the server is over-scaled, especially for a server named Nws: only a handful are weather tools, while the rest belong to the broader Pipeworx data, prediction-market, memory, subscription, and AI-visibility platform. This would be better split into focused servers rather than one large grab-bag.

Completeness3/5

The broad data/research surface covers many use cases via the router, entity profiles, comparisons, claims, subscriptions, and memory. Notable gaps remain: no geocoding to feed the NWS lat/lon tools, no radar/marine NWS products, and no update operation for subscriptions.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 5 tool updates
    • Addedcompany_facts
    • Addedkalshi_weather_edge
    • Addedrelease_calendar_markets
    • Addedresolution_audit
    • Addedresolution_diff
  2. 2 tool updates
    • Changedbet_research2 fields changed
      • changedInput schema / examples
        Previous value: -[
        -  {
        -    "market": "will-bitcoin-reach-100k-in-july-2026"
        -  },
        -  {
        -    "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026"
        -  }
        -]New value: +[
        +  {
        +    "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination"
        +  },
        +  {
        +    "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination"
        +  }
        +]
      • changedInput schema / properties / market / description
        Previous value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
    • Changedpolymarket_kalshi_spread2 fields changed
      • changedInput schema / examples
        Previous value: -[
        -  {
        -    "topic": "fed"
        -  },
        -  {
        -    "topic": "btc"
        -  }
        -]New value: +[
        +  {
        +    "topic": "fed"
        +  },
        +  {
        +    "topic": "btc"
        +  },
        +  {
        +    "topic": "bitcoin"
        +  },
        +  {
        +    "topic": "fed rate decision"
        +  }
        +]
      • changedInput schema / properties / topic / description
        Previous value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."

Related MCP Connectors

Related MCP Servers

  • F
    license
    Not graded
    quality
    C
    maintenance
    MCP server that provides US National Weather Service forecasts and active weather alerts through MCP tools, using no API key but supporting US locations only.
    -
  • A
    license
    Not graded
    quality
    D
    maintenance
    Enables to interact with comprehensive weather data through the MCP protocol, including current conditions, multi-day forecasts, hourly forecasts, and geocoding.
    7 npm
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    Provides weather forecasts and active alerts for US locations using the National Weather Service API. It supports both local stdio and remote HTTP/SSE transport modes for flexible integration with MCP clients.
    85 npm
    GPL 3.0
Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.