mcpapp1
Related Servers
Alternatives to mcpapp1
No user-submitted related servers found.
Related Servers
- FlicenseBqualityCmaintenanceEnables MCP clients to retrieve active weather alerts for US states and five-period forecasts for US coordinates.2-
- FlicenseNot gradedqualityDmaintenanceEnables users to get real-time weather alerts for US states and echo messages through both MCP server tools and a modern web interface. Provides weather information access with multiple deployment options for different use cases.1-
- FlicenseNot gradedqualityCmaintenanceEnables querying live U.S. National Weather Service alerts by state through MCP, with both Python and TypeScript implementations.-
- FlicenseNot gradedqualityCmaintenanceProvides MCP tools for retrieving active weather alerts by U.S. state and short-term forecasts by latitude/longitude using the National Weather Service API.-
- FlicenseNot gradedqualityDmaintenanceThis is a Model Context Protocol (MCP) server that provides weather information using the National Weather Service (NWS) API. Features Get weather alerts for a US state Get weather forecast for a specific location (using latitude and longitude)-
- FlicenseBqualityDmaintenanceProvides weather forecasts and alerts for US locations using the National Weather Service API. Enables users to retrieve active alerts by state and detailed forecasts by coordinates via MCP tools.2-
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or misselection. The tool's purpose is clearly defined in its name and description.
The single tool name follows the verb_noun pattern (get_alerts), which is clean and predictable. There are no other tools to create inconsistency.
One tool feels thin for a server, even one dedicated to weather alerts. While alerts retrieval is a focused task, a small set of supporting tools (e.g., list states or get alert details) would make the server feel more complete.
For the stated purpose of retrieving weather alerts, the get_alerts tool covers the core operation without obvious gaps. The domain is narrow, and no additional lifecycle operations are necessary for read-only alert access.