search_providers10 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 |
|---|---|---|
| agentery
https://agentery.com/api/mcp |
answers-mcp | 19 |
| iGaming Tools MCP
https://mcp.i-gaming.tools/mcp |
answers-mcp | 17 |
| outagedeck
https://outagedeck.com/api/mcp |
answers-mcp | 14 |
| bezal
https://app.bezal.ai/api/mcp |
answers-mcp | 13 |
| loacare
https://www.loacare.com/api/mcp |
answers-mcp | 12 |
| LocalPro
https://mcp.localpro.dev/mcp |
answers-mcp | 5 |
| gph-intelligence
https://gph-mcp-server.pages.dev/mcp |
answers-mcp | 4 |
| weightmedscompare-build
https://jfwxdchauccbuwdqjnap.supabase.co/functions/v1/mcp |
answers-mcp | 4 |
| vitena-directory
https://api.vitena.care/mcp |
answers-mcp | 3 |
| 53ON
https://53on.com/mcp |
answers-mcp | 2 |
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.