{"id":"chrischiedo-weather-mcp-server-java","name":"weather-mcp-server-java","homepage":null,"repo_url":"https://github.com/chrischiedo/weather-mcp-server-java","category":"ai-ml","subcategories":[],"tags":["mcp","java","spring-boot","weather","stdio-transport","tooling"],"what_it_does":"Provides a Model Context Protocol (MCP) weather tool via a Java (Spring Boot–based) MCP server using STDIO transport. The exposed tool fetches current weather details for a specified location by calling the free wttr.in weather endpoint (no API key mentioned).","use_cases":["Answering current-weather questions in an MCP-capable assistant/client","Lightweight local/offline integration where the assistant runs and the server is invoked via STDIO","Building demos or prototypes for MCP tool integration using a simple external data source"],"not_for":["Production-grade weather data needs with strong SLAs","Use cases requiring authentication/authorization controls around tool invocation","Forecasts, alerts, or richer weather history without further implementation"],"best_when":"When you want a simple MCP tool that returns current weather from wttr.in for arbitrary locations and you can run a local Java server process.","avoid_when":"When you need robust security boundaries (authz), strict uptime guarantees, or documented resiliency/error contracts for tool calls.","alternatives":["Use wttr.in directly from your application/agent without MCP","Build/host a custom MCP server around a commercial weather API with proper auth","Use other MCP weather/server examples or SDKs from the Spring AI ecosystem (if available)"],"af_score":47.8,"security_score":29.5,"reliability_score":18.8,"package_type":"mcp_server","discovery_source":["github"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T20:00:34.225255+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":"No authentication mechanism is described for MCP tool access. The README shows configuration for running over STDIO, implying local client-to-server communication without auth controls."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"No pricing for the service is mentioned. Weather data is sourced from wttr.in per README (no API key mentioned)."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":47.8,"security_score":29.5,"reliability_score":18.8,"mcp_server_quality":55.0,"documentation_accuracy":45.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":100.0,"rate_limit_clarity":10.0,"tls_enforcement":30.0,"auth_strength":5.0,"scope_granularity":0.0,"dependency_hygiene":55.0,"secret_handling":70.0,"security_notes":"No auth/authz controls are described for invoking MCP tools. Communication is STDIO (not network TLS in this design), but the README does not discuss process isolation or access control. Weather fetch relies on an unauthenticated public API (wttr.in); the README does not mention timeouts, input validation, SSRF protections, or response sanitization. Dependency list is minimal in the README but exact versions and vulnerability status are not provided.","uptime_documented":0.0,"version_stability":25.0,"breaking_changes_history":30.0,"error_recovery":20.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["MCP server is STDIO-based and typically started/stopped by the client (agent/host must manage the process lifecycle correctly).","Reliability depends on wttr.in availability and response format; no fallback or caching is described in the README."]}}