mcp-test
Related Servers
Alternatives to mcp-test
No user-submitted related servers found.
Related Servers
- FlicenseAqualityCmaintenanceProvides current weather data for any city using the Open-Meteo API, exposed as an MCP tool for integration with MCP clients.1-
- AlicenseNot gradedqualityDmaintenanceFetches current weather information for any city using the Open-Meteo API through a simple MCP tool interface.1,632 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables fetching current temperature for any city using the Open-Meteo API, requiring no API key.-
- AlicenseAqualityBmaintenanceMCP server that provides current weather for any city using Open-Meteo APIs. It exposes a single tool 'get_weather' returning temperature, humidity, wind, and other weather data.18 npmMIT
- FlicenseAqualityCmaintenanceProvides weather information through MCP tools, including city search, current weather, forecasts, comparisons, and warmest day identification, using the Open-Meteo API.7-
- FlicenseNot gradedqualityDmaintenanceProvides real-time weather information for any city worldwide using the Open-Meteo API, returning current temperature, wind speed, and geographic coordinates through a containerized MCP server.-
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of overlapping purposes or misselection. The single get_temperature action is completely unambiguous.
The one tool uses a clear get_ + noun naming convention. There are no competing conventions or mixed styles to create inconsistency.
A single tool is on the 'too few' end of the scale, making the server feel like a minimal stub rather than a useful service. Unless the intended purpose is literally only a current temperature lookup, this is insufficient.
For a temperature/weather-related domain, the surface lacks related operations such as unit selection, forecast, geocoding, or validation. The single lookup creates a dead end and leaves obvious gaps for broader temperature use cases.