list_case_studies8 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 |
|---|---|---|
| com.gqlteam/site
https://mcp.gqlteam.com/mcp |
answers-mcp | 10 |
| flamel-public-content
https://www.flamel.ai/mcp |
answers-mcp | 9 |
| synergyboat-public
https://www.synergyboat.com/api/mcp |
answers-mcp | 9 |
| hibot-public
https://hibot.com/mcp/public |
answers-mcp | 7 |
| cymosoft
https://cymosoft.com/mcp |
answers-mcp | 6 |
| GingerLive
https://mcp.gingerlive.io/mcp |
answers-mcp | 6 |
| me.sudhanva/public-profile
https://sudhanva.me/mcp |
answers-mcp | 3 |
| me.sudhanva/public-profile
https://sudhanva.me/mcp/registry |
answers-mcp | 3 |
8 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.