search_projects12 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 |
|---|---|---|
| tulugar
https://tulugar.com/api/mcp |
answers-mcp | 39 |
| pipeworx-gateway
https://gateway.pipeworx.io/openaire/mcp |
answers-mcp | 37 |
| pipeworx-gateway
https://gateway.pipeworx.io/osf/mcp |
answers-mcp | 34 |
| pipeworx-gateway
https://gateway.pipeworx.io/pride/mcp |
answers-mcp | 33 |
| MCP Market Russia
https://mcp-market.ru/mcp/ |
answers-mcp | 24 |
| msp-portfolio
https://msp-portfolio.mansio-dev.workers.dev/mcp |
answers-mcp | 18 |
| hiveround
https://hiveround.com/api/mcp |
answers-mcp | 14 |
| thisispaper
https://www.thisispaper.com/intelligence/api/mcp |
answers-mcp | 10 |
| watt-street
https://api.wattstreet.net/mcp |
answers-mcp | 7 |
| raintree-technology-public
https://raintree.technology/mcp |
answers-mcp | 7 |
| hireme-mcp
https://mcp.djaouad.tech/mcp |
answers-mcp | 5 |
| git-top
https://git.top/mcp/core |
answers-mcp | 5 |
12 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.