get_alerts10 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.
| server | result when we called it | tools |
|---|---|---|
| CryptoData API
https://cryptodata-api.datachain.workers.dev/mcp |
answers-mcp | 48 |
| prowlo
https://api.prowlo.com/mcp |
answers-mcp | 47 |
| pipeworx-gateway
https://gateway.pipeworx.io/nws/mcp |
answers-mcp | 36 |
| sw-mcp
https://mcp.smarterweather.com |
answers-mcp | 32 |
| dns-doctor
https://dnsdoctor.dev/mcp |
answers-mcp | 16 |
| crosbynews-weather
https://crosbynews.com/mcp |
answers-mcp | 14 |
| metro-catalyst
https://cap-rate-signals-mcp-production.up.railway.app/mcp |
answers-mcp | 14 |
| prg-risk-mcp
https://prg-risk-mcp-production.up.railway.app/mcp |
answers-mcp | 5 |
| nws-alerts
https://mcp.olyport.com/nws-alerts/mcp |
answers-mcp | 3 |
| walletwatch
https://loki.freedomlab.space/mcp |
answers-mcp | 3 |
10 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.