Environment Canada Weather Alerts MCP Server
Related Servers
Alternatives to Environment Canada Weather Alerts MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceProvides access to National Weather Service (NWS) data, enabling users to retrieve active weather alerts for US states and weather forecasts for specific geographic coordinates.96 npmMIT
- FlicenseNot gradedqualityDmaintenanceProvides active weather alerts for U.S. states and 7-day forecasts for a given latitude and longitude.-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to access live weather data from Environment and Climate Change Canada via the GeoMet API.2 npmMIT
- FlicenseBqualityDmaintenanceProvides weather data including US alerts, US forecasts, and global 5-day forecasts without requiring any API keys.31-
- AlicenseNot gradedqualityCmaintenanceEnables access to authoritative US National Weather Service forecasts, hourly forecasts, active alerts, and station observations with no authentication required.1 npmMIT
- AlicenseBqualityDmaintenanceProvides access to US National Weather Service data including active alerts by state and short-term forecasts for specific coordinates.2MIT
TDQS
Scored across 4 tools
The four tools split into clear roles: summary (aggregate), details (single alert), list/filter (by province/keyword), and spatial (coordinates). The only mild overlap is between get_weather_alerts and get_alerts_near_coordinates, since both return alert lists, but their inputs (province/filters vs lat/lon) distinguish them well.
All tools share a consistent 'get_' prefix and snake_case convention. Minor deviations exist in noun form ('alert' vs 'alerts', 'weather_alerts' vs 'alerts_near_coordinates'), but the pattern remains predictable.
Four tools is a reasonable, well-scoped set for a read-only weather-alert service covering aggregate, detail, list, and spatial views. It is slightly lean and could arguably support one or two more query modes, but nothing is redundant.
The domain is alert retrieval, and the surface covers the main access patterns: summary, per-alert detail, filtered listing, and coordinate lookup. As a read-only external data feed, no CRUD lifecycle is expected, so coverage is nearly complete with only minor gaps.