Back to the tool index

get_weather

13 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
gadgethumans-mcp
https://api.gadgethumans.com/mcp
answers-mcp 46
mellowmountainradio
https://mcp.mellowmountainradio.com/mcp
answers-mcp 46
datalastic-mcp
https://mcp.datalastic.com/mcp
answers-mcp 25
sphere-marketplace
https://starsphera.com/mcp/sse
answers-mcp 14
outdoorithm
https://mcp.outdoorithm.com/mcp
answers-mcp 13
refugio-san-bernardo-public
https://hawudqgbvwmgwhhcbthb.supabase.co/functions/v1/mcp-public
answers-mcp 9
weather
https://weather-mcp-2yhb.onrender.com/mcp
answers-mcp 5
travel_transportation_mcp
https://travel-transportation-mcp.mcpize.run/mcp
answers-mcp 4
AgentGeo
https://geo.memoryapi.org/mcp
answers-mcp 3
weather
https://ads.getlulu.dev/weather/mcp
answers-mcp 2
weather-mcp-server
https://nexgendata-mcp-proxy.steve-corbeil.workers.dev/weather-mcp-server/mcp
answers-mcp 1
mcp-killchain-stage1-weather
https://ailm.gtfo.dev/mcp
answers-mcp 1
echorune-radar
https://echorune.net/mcp
answers-mcp 1

13 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.