get_provider10 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 |
|---|---|---|
| apis.io https://apis.io/mcp |
answers-mcp | 133 |
| peppolstatus https://mcp.peppolstatus.com |
answers-mcp | 51 |
| tamgara https://api.tamgara.com/api/mcp |
answers-mcp | 33 |
| agentery https://agentery.com/api/mcp |
answers-mcp | 19 |
| inferenceindexer https://api.inferenceindexer.ai/mcp |
answers-mcp | 10 |
| neurocompare https://oppjwyhquadekoaadtka.supabase.co/functions/v1/mcp |
answers-mcp | 5 |
| securecloudstorage https://securecloudstorage.com/mcp |
answers-mcp | 5 |
| LocalPro https://mcp.localpro.dev/mcp |
answers-mcp | 5 |
| service-provider-index https://spi.fugentic.ai/mcp |
answers-mcp | 3 |
| vitena-directory https://api.vitena.care/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.