Nws
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
Scored across 41 tools
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.
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.
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.
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.
5 tool updates
- Added
company_facts - Added
kalshi_weather_edge - Added
release_calendar_markets - Added
resolution_audit - Added
resolution_diff
2 tool updates
- Changed
bet_research2 fields changed- changed
Input schema / examplesPrevious 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" + } +] - changed
Input schema / properties / market / descriptionPrevious 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."
- Changed
polymarket_kalshi_spread2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "topic": "fed" - }, - { - "topic": "btc" - } -]New value: +[ + { + "topic": "fed" + }, + { + "topic": "btc" + }, + { + "topic": "bitcoin" + }, + { + "topic": "fed rate decision" + } +] - changed
Input schema / properties / topic / descriptionPrevious 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
NOAA Weather MCP — National Weather Service forecasts and alerts
Smarter Weather MCP: forecasts, alerts, outlooks, observations, AQI, grids, and map imagery.
MET Norway (api.met.no) MCP — global weather, Nordics specials.
Hosted MCP server for Xweather weather data: conditions, forecasts, alerts, and more.
Related MCP Servers
- FlicenseNot gradedqualityCmaintenanceMCP server that provides US National Weather Service forecasts and active weather alerts through MCP tools, using no API key but supporting US locations only.-
- AlicenseAqualityAmaintenanceCombines National Weather Service alerts and forecasts with modern USGS water data, enabling weather and hydrology queries through MCP. No API key required, with persistent local caching.29Creative Commons Zero v1.0 Universal
- AlicenseNot gradedqualityDmaintenanceEnables to interact with comprehensive weather data through the MCP protocol, including current conditions, multi-day forecasts, hourly forecasts, and geocoding.7 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides 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 npmGPL 3.0
Glama MCP Gateway
Add one secure layer between your agents and this server.