Visual Crossing Weather (Unofficial)
Server Details
Unofficial Visual Crossing Weather MCP — wraps the Visual Crossing Weather Timeline API…
The last two health checks of this connector failed. 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
- 0.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-visualcrossing
- GitHub Stars
- 0
- Server Listing
- visualcrossing
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 47 tools
Descriptions work hard to steer callers (PREFER OVER, START HERE, use X instead of Y), but multiple clusters overlap heavily: ask_pipeworx / ask_pipeworx_beta (currently identical) / ask_pipeworx_grounded / deep_research / discover_tools / suggest_questions all answer 'find me an answer or a tool', and polymarket_arbitrage / polymarket_edges / polymarket_edge_tracker / bet_research / polymarket_fill_risk all claim pieces of the same betting-edge workflow. Entity tools (entity_profile vs company_facts vs compare_entities vs resolve_entity) are better separated but still need reading the description to pick correctly.
Casing is uniformly snake_case, but the naming grammar is mixed: noun_verb (ai_visibility_check, pipeworx_feedback), noun-only (entity_profile, forecast, current_conditions), verb_noun (discover_tools, compare_entities, validate_claim), and vendor-prefixed families (polymarket_*, ask_pipeworx_*, updown_*). Weather tools are especially inconsistent as a family: current_conditions, forecast, weather_timeline, kalshi_weather_edge.
47 tools is far above the workable range for a single MCP surface and forces the server to ship its own meta-navigation tools (discover_tools, suggest_questions) to compensate. The universal-router ambition explains the breadth, but the count is heavy enough that an agent must triage before acting.
Coverage is unusually deep: identity resolution, company fundamentals, historical and live weather, prediction-market pricing/mispricing/settlement, archive evidence, per-row research, memory, and subscriptions all have dedicated lifecycle support (subscribe/list/unsubscribe/recent_alerts, remember/recall/forget). Remaining gaps are minor conveniences rather than dead ends, since ask_pipeworx can route to any missing single-source lookup.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Unofficial OpenWeather MCP — wraps the OpenWeatherMap API (openweathermap.org)
Weather MCP — wraps Open-Meteo API (free, no auth)
WeatherAPI.com MCP — wraps WeatherAPI.com (api.weatherapi.com)
Unofficial Climate MCP — wraps Open-Meteo Climate API (free, no auth)
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables to interact with comprehensive weather data through the MCP protocol, including current conditions, multi-day forecasts, hourly forecasts, and geocoding.MIT
- AlicenseAqualityCmaintenanceMCP server for weather forecasts via Open-Meteo (no API key needed), providing current weather, hourly, and daily forecasts with geocoding support.3MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables retrieval of historical weather data (temperature, precipitation, conditions, etc.) from Visual Crossing for specified locations and dates.1GPL 3.0
- AlicenseNot gradedqualityDmaintenanceMCP server providing weather data via the Open-Meteo API, including geocoding, current conditions, daily and hourly forecasts, and city lookup. No API key required, with support for multiple units and transport types.1MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.