{"id":"weather-mcp-server-wl","name":"weather-mcp-server-wl","homepage":"https://pypi.org/project/weather-mcp-server-wl/","repo_url":null,"category":"infrastructure","subcategories":[],"tags":["mcp","weather","ai-agents","tooling"],"what_it_does":"weather-mcp-server-wl appears to provide an MCP (Model Context Protocol) server for retrieving weather information for use by AI agents.","use_cases":["AI assistants that answer weather questions (current conditions, forecasts)","Workflow automation that needs weather context (routing, scheduling suggestions)","Location-based customer support or chatbots needing weather data"],"not_for":["High-assurance meteorological operations where authoritative data provenance and SLA are critical","Billing/commerce or transactional workflows","Use as a general-purpose geospatial database beyond weather"],"best_when":null,"avoid_when":null,"alternatives":["Using a weather data REST API directly from an AI agent","Other MCP weather servers (if available)","Weather providers SDKs (e.g., OpenWeather, WeatherAPI) with custom tool wrapping"],"af_score":36.2,"security_score":37.5,"reliability_score":10.0,"package_type":"mcp_server","discovery_source":["pypi"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T21:39:32.174603+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":true,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":[],"oauth":false,"scopes":false,"notes":null},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":null},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":36.2,"security_score":37.5,"reliability_score":10.0,"mcp_server_quality":55.0,"documentation_accuracy":30.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":50.0,"rate_limit_clarity":20.0,"tls_enforcement":50.0,"auth_strength":30.0,"scope_granularity":30.0,"dependency_hygiene":40.0,"secret_handling":40.0,"security_notes":"No repository manifest/README details were provided here, so scores are conservative. MCP servers that integrate with third-party weather APIs commonly require API keys; secret leakage risks depend on how configuration is handled (e.g., env vars vs logs) and whether the server validates inputs (locations) to prevent abuse.","uptime_documented":0.0,"version_stability":0.0,"breaking_changes_history":0.0,"error_recovery":40.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["Weather queries may require a location format (city name vs lat/long); ambiguity can cause failures.","If the server relies on an upstream weather provider, missing/invalid API keys or provider limits may surface as tool errors.","Time-sensitive data: repeated calls may return changing results; agents should avoid assuming deterministic responses."]}}