get_events16 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 |
|---|---|---|
| dayze
https://dayze.com/api/mcp |
answers-mcp | 81 |
| mellowmountainradio
https://mcp.mellowmountainradio.com/mcp |
answers-mcp | 46 |
| pipeworx-gateway
https://gateway.pipeworx.io/odds-api/mcp |
answers-mcp | 37 |
| anatome
https://anatome.dev/mcp |
answers-mcp | 36 |
| pipeworx-gateway
https://gateway.pipeworx.io/onthisday/mcp |
answers-mcp | 34 |
| duami
https://duami.ai/mcp |
answers-mcp | 29 |
| iturri-data
https://iturri.ai/mcp |
answers-mcp | 22 |
| signal-bureau
https://api.signalbureau.ai/api/mcp |
answers-mcp | 21 |
| hail
https://mcp.hail.so |
answers-mcp | 20 |
| Insourcia
https://mcp.insourcia.io/mcp |
answers-mcp | 18 |
| edgrapi
https://api.edgrapi.com/mcp |
answers-mcp | 15 |
| travellers-agent
https://agent.travellersgroup.com.au/v1/mcp |
answers-mcp | 12 |
| firmtape
https://mcp.firmtape.com/mcp |
answers-mcp | 9 |
| ticker-scout
https://mcp.tickerscout.ai/mcp |
answers-mcp | 6 |
| newsflash
https://newsflash.sh/mcp |
answers-mcp | 5 |
| shingou
https://api.shingou.io/mcp |
answers-mcp | 4 |
16 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.