weather-mcp-server-java

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).

Evaluated Apr 04, 2026 (16d ago)

Repo ↗ Ai Ml mcp java spring-boot weather stdio-transport tooling

⚙ Agent Friendliness

/ 100

Can an agent use this?

🔒 Security

/ 100

Is it safe for agents?

⚡ Reliability

/ 100

Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality

Documentation

Error Messages

Auth Simplicity

100

Rate Limits

🔒 Security

TLS Enforcement

Auth Strength

Scope Granularity

Dep. Hygiene

Secret Handling

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.

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

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.

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

Interface

REST API

GraphQL

gRPC

MCP Server

Yes

SDK

Webhooks

Authentication

OAuth: No Scopes: No

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

Free tier: No

Requires CC: No

No pricing for the service is mentioned. Weather data is sourced from wttr.in per README (no API key mentioned).

Agent Metadata

Pagination

none

Idempotent

False

Retry Guidance

Not documented

Known 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.

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)

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for weather-mcp-server-java.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-04-04.