geocode11 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 |
|---|---|---|
| gadgethumans-mcp
https://api.gadgethumans.com/mcp |
answers-mcp | 46 |
| sn-mcp
https://mcp.mapmap.ai/mcp |
answers-mcp | 43 |
| pipeworx-gateway
https://gateway.pipeworx.io/maptiler/mcp |
answers-mcp | 39 |
| pipeworx-gateway
https://gateway.pipeworx.io/open-meteo/mcp |
answers-mcp | 37 |
| pipeworx-gateway
https://gateway.pipeworx.io/openweather/mcp |
answers-mcp | 35 |
| pipeworx-gateway
https://gateway.pipeworx.io/ban-fr/mcp |
answers-mcp | 34 |
| pipeworx-gateway
https://gateway.pipeworx.io/opencages/mcp |
answers-mcp | 33 |
| skill-audit
https://eltociear-skill-audit.hf.space/mcp |
answers-mcp | 11 |
| tokenguard
https://eltociear-tokenguard.hf.space/mcp |
answers-mcp | 9 |
| weather-intel
https://weather.datakoot.com/mcp |
answers-mcp | 6 |
| dfetcher
https://dfetcher.com/mcp |
answers-mcp | 3 |
11 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.