get_service13 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 |
|---|---|---|
| api-evangelist https://mcp.apievangelist.com/mcp |
answers-mcp | 67 |
| fiatdock https://fiatdock.com/mcp |
answers-mcp | 18 |
| com.gqlteam/site https://mcp.gqlteam.com/mcp |
answers-mcp | 10 |
| synergyboat-public https://www.synergyboat.com/api/mcp |
answers-mcp | 9 |
| RIX Freight MCP (multilingual) https://mcp.rixfreight-group.com/mcp |
answers-mcp | 8 |
| nAIm https://mcp.naim.janis7ewski.org/sse |
answers-mcp | 7 |
| nAIm https://mcp.naim.janis7ewski.org/mcp |
answers-mcp | 7 |
| Schlingloff Euromovers (multilingual) https://mcp.schlingloff-euromovers.de/mcp |
answers-mcp | 6 |
| StatelessServer https://run.googleapis.com/mcp |
answers-mcp | 5 |
| com.lakpura/mcp https://app.lakpura.com/api/mcp |
answers-mcp | 5 |
| com.lakpura/mcp https://mcp.lakpura.com |
answers-mcp | 5 |
| dribba-docs https://dribba.com/docs/mcp |
answers-mcp | 4 |
| vouchtrail https://vouchtrail.com/mcp |
answers-mcp | 3 |
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.