npm/-jablum/weather-mcp/get_historical_weather / alternatives

Live alternatives to npm/-jablum/weather-mcp/get_historical_weather

The best live alternatives to npm/-jablum/weather-mcp/get_historical_weather right now are mcp-registry/io.github.pipeworx-io/weather/get_historical, mcp-registry/io.github.pipeworx-io/visualcrossing/weather_timeline — capability-matched and ranked by current reliability. npm/-jablum/weather-mcp/get_historical_weather itself is currently "unknown".

alternative	server
mcp-registry/io.github.pipeworx-io/weather/get_historical	io.github.pipeworx-io/weather	live status →
mcp-registry/io.github.pipeworx-io/visualcrossing/weather_timeline	io.github.pipeworx-io/visualcrossing	live status →

FAQ

What is the best alternative to npm/-jablum/weather-mcp/get_historical_weather?

mcp-registry/io.github.pipeworx-io/weather/get_historical is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/visualcrossing/weather_timeline. Glimind ranks alternatives by semantic similarity and live health.

Is npm/-jablum/weather-mcp/get_historical_weather down right now?

npm/-jablum/weather-mcp/get_historical_weather's current verdict is "unknown". See its live status and score at https://glimind.com/tool/npm%2F-jablum%2Fweather-mcp%2Fget_historical_weather.

How does Glimind pick alternatives?

By semantic capability match (what the tool does) filtered to tools that are healthy right now — from cross-ecosystem real usage. Neutral: Glimind sells no tools.

For agents

Get a live, capability-matched substitute in one call: GET https://glimind.com/v1/alternatives/npm%2F-jablum%2Fweather-mcp%2Fget_historical_weather or MCP find_alternatives. Check npm/-jablum/weather-mcp/get_historical_weather's live status: https://glimind.com/tool/npm/-jablum/weather-mcp/get_historical_weather.