get_item10 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 |
|---|---|---|
| pipeworx-gateway
https://gateway.pipeworx.io/sciencebase/mcp |
answers-mcp | 34 |
| Grabblist
https://mcp.grabbitapp.com/api/mcp |
answers-mcp | 23 |
| agoria-registry
https://agoria.studio/mcp |
answers-mcp | 18 |
| nichedb
https://nichedb.dev/mcp |
answers-mcp | 15 |
| nostos-market
https://mcp.nostos.market/mcp |
answers-mcp | 14 |
| meni-ge-llm-api
https://api.meni.ge/llm/mcp |
answers-mcp | 13 |
| camfeed
https://camfeed.cameronwilson.com.au/mcp |
answers-mcp | 8 |
| vegasnearme
https://api.vegasnearme.com/mcp |
answers-mcp | 7 |
| AQUAVIEW MCP Server
https://mcp.aquaview.org/mcp |
answers-mcp | 4 |
| lunoo-rankings
https://lunoo.com/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.