MCP servers observed by Lowdown
ai.snowsure/snow MCP server: daily status and tool changes
Answered initialize and tools/list on all 30 daily checks recorded in the last 30 days (2026-10-20 to 2026-11-18); 48 tools listed. MCP Registry declaration recorded; observed daily by Lowdown Scanner since 2026-10-06; tool definitions last changed on 2026-11-11 after 13 days without change; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ai.snowsure/snow
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ai.snowsure/snow?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-18: the server answered initialize and tools/list.
- Observed days in the last 30: 30
- Answered initialize and tools/list: 30
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 30 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 5 of 30 compared days.
- 2026-11-11: descriptions changed
- 2026-10-29: input or output schemas changed, descriptions changed
- 2026-10-27: input or output schemas changed, descriptions changed
- 2026-10-24: descriptions changed
- 2026-10-23: input or output schemas changed, descriptions changed
What tools does it list?
48 tools on 2026-11-18:
ask_snowdatabook_lodgingcompare_forecastscompare_passescompare_resortsfind_best_powderfind_flights_to_powderfind_pass_resortsfind_powder_tripsfind_resorts_by_criteriaget_avalancheget_destinationget_elnino_rankingsget_elnino_signalget_insightsget_ml_trendsget_monthly_snowget_my_snow_reportget_operating_riskget_passget_powder_reelsget_regional_summaryget_resortget_resort_infoget_resort_photosget_road_accessget_road_camerasget_road_weatherget_season_leaderboardget_season_openingsget_snow_historyget_snow_qualityget_snow_reportget_southern_hemisphere_reportget_storm_watchget_trip_windowget_weather_forecastget_webcam_statuslist_alertslist_insight_categorieslist_saved_resortsplan_ski_road_tripplan_ski_tripremove_saved_resortsave_resortsearch_resortssubscribe_alertsunsubscribe_alerts
MCP Registry declaration
- Registry name:
ai.snowsure/snow - Declared version: 1.0.5
- Status: active
- Declared hosts:
www.snowsure.ai
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:ai.snowsure/snow", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ai.snowsure/snow?menu=install-check
When running its declared package, wrap it with the stdio proxy. Since lowdown-proxy 0.1.22 the proxy adds this record (install-check) to the server's initialize response; it changes no tool result and blocks nothing:
npx -y lowdown-proxy --target mcp:ai.snowsure/snow -- npx -y snowsure-mcp-server
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).