{"id":"alexandredavi-mcp-webmvc-server","name":"mcp-webmvc-server","homepage":null,"repo_url":"https://github.com/alexandredavi/mcp-webmvc-server","category":"ai-ml","subcategories":[],"tags":["mcp","spring-boot","spring-ai","webmvc","sse","stdio","tools","weather"],"what_it_does":"A Spring Boot sample MCP server that exposes weather-related tools (forecast by lat/long and alerts by US state) via the Spring AI MCP Server WebMVC transport. It can run over HTTP SSE (default) or over STDIO for MCP clients.","use_cases":["Providing MCP tools for weather retrieval in an agent workflow","Demonstrating Spring AI MCP Server Boot Starter integration with WebMVC transport","Testing MCP client integrations using SSE or STDIO transports","Building a template for exposing domain APIs as MCP tools"],"not_for":["Production deployments without further hardening (auth, rate limiting, error modeling, input validation, observability)","Use as a complete/finished weather data service (it is described as a sample and weather implementation details are not provided here)","Use cases requiring strong contractual REST-style APIs beyond the MCP protocol"],"best_when":"You want a working reference implementation for an MCP server using Spring AI with either SSE or STDIO transport to expose typed tool callbacks.","avoid_when":"You need explicit authentication, fine-grained authorization, and documented rate limits out of the box, or you require an API spec such as OpenAPI for direct REST consumption.","alternatives":["Use a different MCP server implementation framework (e.g., another MCP SDK/library) with documented auth and operational controls","Build a REST API + separate tool adapter (bridge) rather than exposing MCP directly","Use Spring AI client/server boot starters and expand from a template with production-grade configuration"],"af_score":55.8,"security_score":32.5,"reliability_score":17.5,"package_type":"mcp_server","discovery_source":["github"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T19:50:51.169536+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":true,"mcp_server_url":"http://localhost:8080 (SSE mode per README; exact path for MCP message endpoint is /mcp/message)","has_sdk":false,"sdk_languages":["Java"],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":[],"oauth":false,"scopes":false,"notes":"No authentication/authorization is described for the MCP server itself in the provided README content."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"This appears to be a self-hosted sample project; no pricing model is described."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":55.8,"security_score":32.5,"reliability_score":17.5,"mcp_server_quality":70.0,"documentation_accuracy":75.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":95.0,"rate_limit_clarity":5.0,"tls_enforcement":60.0,"auth_strength":20.0,"scope_granularity":0.0,"dependency_hygiene":50.0,"secret_handling":40.0,"security_notes":"README does not describe authentication/authorization or rate limiting for the MCP server. TLS requirements are not discussed; if deployed behind HTTPS, TLS would be handled by the hosting layer. The project likely makes outbound calls to weather.gov (per description), but handling of API keys/secrets and safe logging is not evidenced in the provided content.","uptime_documented":0.0,"version_stability":20.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":["Server runs in two modes (SSE default vs STDIO via JVM properties); clients must match the transport configuration.","The README indicates a configurable SSE message endpoint (/mcp/message), so routing/endpoint assumptions may differ by configuration.","No explicit guidance is given for tool-level validation errors or how structured MCP errors are returned."]}}