Basic MCP Weather Tool
Related Servers
Alternatives to Basic MCP Weather Tool
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceA minimal MCP server that provides current weather and forecasts for any city using the free Open-Meteo API, no API key required.7-
- AlicenseNot gradedqualityDmaintenanceAn MCP server that offers arithmetic operations (addition and division) and current weather data from OpenWeatherMap. It serves as a learning project for building MCP servers with Node.js and TypeScript, supporting both stdio and Streamable HTTP transports.11ISC
- FlicenseNot gradedqualityDmaintenanceA minimal MCP server that provides weather data using Open-Meteo API, designed as a teaching tool for improving AI agent tool interfaces.-
- FlicenseBqualityDmaintenanceA simple MCP server that provides a tool to fetch current weather information for cities using the Open-Meteo API, communicating through stdin/stdout.12-
- FlicenseNot gradedqualityCmaintenanceA proof-of-concept MCP server that provides weather information using the Open-Meteo API, with tools for greeting, getting weather by coordinates, and by location name.-
- AlicenseNot gradedqualityDmaintenanceA MCP server for querying real-time weather information for any city worldwide using the free Open-Meteo API, supporting CLI and integration with AI clients like Claude and Cursor.12MIT
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'fetch-weather' has a clear and distinct purpose, making it impossible for an agent to misselect among non-existent alternatives.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'fetch-weather' follows a verb_noun pattern, and with no other tools to compare against, there are no deviations or inconsistencies in naming conventions.
A single tool for a weather server is too few for the apparent scope, as weather-related operations typically involve more than just fetching data (e.g., forecasts, historical data, or location-based queries). This minimal set feels thin and limits functionality, indicating a mismatch with the domain's needs.
The tool surface is severely incomplete for a weather domain. While 'fetch-weather' provides basic retrieval, there are obvious gaps such as lacking forecast tools, historical data access, or location-specific queries. This will likely cause agent failures when more comprehensive weather information is needed.