mcp-tenki
Related Servers
Alternatives to mcp-tenki
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceProvides weather information for 110 cities across Japan with natural language support for location names in kanji, hiragana, and katakana. Retrieves current weather conditions and forecasts using OpenMeteo API through MCP-compliant tools.1MIT
- FlicenseNot gradedqualityCmaintenanceEnables retrieval of weather information for major cities across Japan using the Japan Meteorological Agency API. Supports weather overviews, precipitation probability, and wind speed data with both local and remote OAuth 2.0 authenticated deployment options.7 npm-
- AlicenseAqualityBmaintenanceProvides access to Japan Meteorological Agency (JMA) weather data including real-time observations, historical weather data, and forecasts from 1286 AMeDAS stations across Japan.111MIT
- -
- AlicenseNot gradedqualityCmaintenanceEnables you to retrieve JMA weather forecasts, warnings/advisories, and earthquake reports by place name, with no API key required.MIT
- FlicenseNot gradedqualityCmaintenanceMCP server providing weather forecast, warnings, AMeDAS observations, and area search from Japan Meteorological Agency JSON APIs. It normalizes responses and supports Japanese place names.-
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as getting forecasts for Japanese locations, making it distinct by default.
The single tool follows a clear verb_noun pattern (get_forecast), which is consistent and predictable. Since there are no other tools, there is no inconsistency to evaluate.
One tool is too few for a weather forecasting server, as it lacks essential operations like searching locations, getting current conditions, or handling multiple forecast types. This minimal scope will likely cause agent failures due to incomplete functionality.
The server is severely incomplete for weather forecasting; it only provides forecasts without supporting related operations like current weather, alerts, or location validation. This creates significant gaps that will hinder agent workflows.