reverse_geocode10 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 |
|---|---|---|
| sn-mcp
https://mcp.mapmap.ai/mcp |
answers-mcp | 43 |
| france-data-mcp
https://france-data-mcp.vercel.app/mcp |
answers-mcp | 36 |
| pipeworx-gateway
https://gateway.pipeworx.io/ban-fr/mcp |
answers-mcp | 34 |
| pipeworx-gateway
https://gateway.pipeworx.io/nominatim/mcp |
answers-mcp | 34 |
| sw-mcp
https://mcp.smarterweather.com |
answers-mcp | 32 |
| luxembourg-mcp
https://mcp.luxembourg-mcp.com/mcp |
answers-mcp | 28 |
| ZipExplore
https://mcp.zipexplore.com/mcp |
answers-mcp | 22 |
| acuris-geo
https://api.acuris-geo.com/mcp |
answers-mcp | 8 |
| latlng-mcp
https://mcp.latlng.work/mcp |
answers-mcp | 5 |
| jusho-mcp
https://jusho-mcp.easakura.workers.dev/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.