Is ai.snowsure/snow up? Live MCP status
Yes, it is up. It answered an MCP initialize with no credential and negotiated protocol 2025-11-25.
A stock client connected with no credential and negotiated 2025-11-25. Use it.
| Outcome | usable |
|---|---|
| HTTP status | 200 |
| Protocol version | 2025-11-25 |
| Server says it is | snowsure-mcp 3.12.7 |
| Answered in | 682 ms |
| Endpoint checked | https://www.snowsure.ai/mcp |
| Checked |
One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.
Live status every few hours: Wellknown
Email me when this server changes
That was one look. To hear when it stops answering or its tools change, leave an address.
Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.
Monthly census, 6 October 2026
The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).
Agent discovery documents at this origin
| A2A agent card | Published, does not validate: an A2A 0.3 card: no `supportedInterfaces`, which 1.0 requires in place of `url` and `protocolVersion`. A2A 0.3 shape; 2 skills; JSONRPC./.well-known/agent-card.json |
|---|---|
| MCP server card (SEP-2127) | Not published (HTTP 404).https://www.snowsure.ai/mcp/server-card |
| MCP server card (SEP-1649 location) | Published, does not validate: `$schema` is required (and 2 more). SEP-1649 shape; snowsure-live 1.0.0; MCP 2025-03-26; streamable-http./.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026 |
| Web Bot Auth key directory | Published, does not validate: keys[0]: `alg` EdDSA is not in the HTTP Signature Algorithms registry (§5.5.1) (and 1 more). 1 key (Ed25519); the response is not signed./.well-known/http-message-signatures-directory |
Read at https://www.snowsure.ai with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.
Tool changes between snapshots
In the 2026-10 snapshot it listed 48 tools: ask_snowdata, book_lodging, compare_forecasts, compare_passes, compare_resorts, find_best_powder, find_flights_to_powder, find_pass_resorts, find_powder_trips, find_resorts_by_criteria, get_avalanche, get_destination, get_elnino_rankings, get_elnino_signal, get_insights, get_ml_trends, get_monthly_snow, get_my_snow_report, get_operating_risk, get_pass, get_powder_reels, get_regional_summary, get_resort, get_resort_info, get_resort_photos, get_road_access, get_road_cameras, get_road_weather, get_season_leaderboard, get_season_openings, get_snow_history, get_snow_quality, get_snow_report, get_southern_hemisphere_report, get_storm_watch, get_trip_window, get_weather_forecast, get_webcam_status, list_alerts, list_insight_categories, list_saved_resorts, plan_ski_road_trip, plan_ski_trip, remove_saved_resort, save_resort, search_resorts, subscribe_alerts, unsubscribe_alerts.
Its tools changed between 2026-09 and 2026-10:
- Added (1):
get_snow_quality book_lodging: input schema changedcompare_forecasts: description, input schema changedfind_best_powder: output schema changedfind_flights_to_powder: input schema changedget_avalanche: input schema changedget_elnino_signal: input schema changedget_monthly_snow: input schema changedget_operating_risk: input schema changedget_powder_reels: input schema changedget_resort: input schema changedget_resort_info: input schema changedget_resort_photos: input schema changedget_road_access: description, input schema changedget_road_cameras: description, input schema changedget_road_weather: description, input schema changedget_snow_history: input schema changedget_snow_report: output schema changedget_trip_window: input schema changedget_weather_forecast: description, input schema changedget_webcam_status: input schema changedremove_saved_resort: input schema changedsave_resort: input schema changedsubscribe_alerts: input schema changed
Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.
The listing
| Registry name | ai.snowsure/snow |
|---|---|
| Title | SnowSure — Snow & Ski |
| Description | Live ski snow, multi-model forecasts, powder rankings & a grounded Answer Engine for 500+ resorts. |
| Endpoint | https://www.snowsure.ai/mcp |
| Publisher repository | https://github.com/mikeslone/snowsure-web |
| Version | 1.0.4 |
| Listing updated |
Also
The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt