get_dataset16 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 |
|---|---|---|
| Newscatcher CatchAll API
https://catchall-mcp.newscatcherapi.com/mcp |
answers-mcp | 61 |
| sella-mcp
https://sellag.vercel.app/api/mcp |
answers-mcp | 52 |
| pipeworx-gateway
https://gateway.pipeworx.io/huggingface/mcp |
answers-mcp | 41 |
| pipeworx-gateway
https://gateway.pipeworx.io/data-gov-sg/mcp |
answers-mcp | 40 |
| pipeworx-gateway
https://gateway.pipeworx.io/uk-ons/mcp |
answers-mcp | 37 |
| pipeworx-gateway
https://gateway.pipeworx.io/bpstat-pt/mcp |
answers-mcp | 35 |
| pipeworx-gateway
https://gateway.pipeworx.io/cso-ie/mcp |
answers-mcp | 35 |
| pipeworx-gateway
https://gateway.pipeworx.io/dados-pt/mcp |
answers-mcp | 35 |
| pipeworx-gateway
https://gateway.pipeworx.io/statbel-be/mcp |
answers-mcp | 35 |
| pipeworx-gateway
https://gateway.pipeworx.io/cms/mcp |
answers-mcp | 34 |
| pipeworx-gateway
https://gateway.pipeworx.io/datagov/mcp |
answers-mcp | 34 |
| pipeworx-gateway
https://gateway.pipeworx.io/eurostat/mcp |
answers-mcp | 34 |
| pipeworx-gateway
https://gateway.pipeworx.io/nsi-bg/mcp |
answers-mcp | 34 |
| pipeworx-gateway
https://gateway.pipeworx.io/cdc/mcp |
answers-mcp | 33 |
| luxembourg-mcp
https://mcp.luxembourg-mcp.com/mcp |
answers-mcp | 28 |
| DataPulse MY
https://mcp.data-pulse.my/mcp |
answers-mcp | 18 |
16 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.