get_job_status11 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 |
|---|---|---|
| fine-structure-mcp https://finestructure.ai/api/mcp |
answers-mcp | 84 |
| Newscatcher CatchAll API https://catchall-mcp.newscatcherapi.com/mcp |
answers-mcp | 61 |
| floot https://mcp.floot.com/mcp |
answers-mcp | 46 |
| com.daedalmap/county-map https://app.daedalmap.com/mcp |
answers-mcp | 30 |
| viral-outliers https://viraloutliers.com/api/mcp |
answers-mcp | 29 |
| com.daedalmap/geography https://app.daedalmap.com/mcp/geography |
answers-mcp | 20 |
| verifly-mcp-server https://verifly.email/mcp |
answers-mcp | 17 |
| weftly https://api.weftly.ai/mcp |
answers-mcp | 13 |
| com.daedalmap/boundaries https://app.daedalmap.com/mcp/boundaries |
answers-mcp | 11 |
| tintin-tryon https://tintin-x.com/mcp |
answers-mcp | 7 |
| ffpipe-gateway https://ffpipe.dev/mcp |
answers-mcp | 6 |
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.