Back to the tool index

get_forecast

17 servers reported a tool by this name when we called them. Names are chosen by whoever wrote the server, so two tools sharing a name do not have to do the same thing. We record what was reported, not what it does.

serverresult when we called ittools
SimpleFunctions
https://simplefunctions.dev/api/mcp/mcp
answers-mcp 108
ask-ai-dataconnector
https://ask-ai-data-connector.com/mcp
answers-mcp 65
gadgethumans-mcp
https://api.gadgethumans.com/mcp
answers-mcp 46
pipeworx-gateway
https://gateway.pipeworx.io/nws/mcp
answers-mcp 36
pipeworx-gateway
https://gateway.pipeworx.io/airquality/mcp
answers-mcp 33
sw-mcp
https://mcp.smarterweather.com
answers-mcp 32
clariBI MCP Server
https://claribi.com/mcp/v1/
answers-mcp 26
clariBI MCP Server
https://claribi.com/mcp/v1/sse
answers-mcp 26
Quantustik
https://quantustik.com/mcp
answers-mcp 26
vibesprings
https://vibesprings.net/mcp
answers-mcp 25
crosbynews-weather
https://crosbynews.com/mcp
answers-mcp 14
aboard
https://aboard.untype.me/mcp
answers-mcp 9
met-weather
https://met-mcp.met-mcp-worker.workers.dev/mcp
answers-mcp 8
voltcast
https://voltcast.com/api/mcp
answers-mcp 7
ai-rate-limit-tracker
https://api.lazy-mac.com/ai-rate-limit-tracker/mcp
answers-mcp 4
nws-alerts
https://mcp.olyport.com/nws-alerts/mcp
answers-mcp 3
weather
https://ads.getlulu.dev/weather/mcp
answers-mcp 2

17 of these answered an MCP handshake on the day we checked. That is not a promise the tool works, only that the server was running and told us the tool existed.