list_alerts11 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 |
|---|---|---|
| crank-public
https://mcp.crank.ing/mcp |
answers-mcp | 184 |
| snowsure-mcp
https://www.snowsure.ai/mcp |
answers-mcp | 46 |
| tw-market-data
https://mcp.twmarketdata.com/mcp |
answers-mcp | 41 |
| pipeworx-gateway
https://gateway.pipeworx.io/nps/mcp |
answers-mcp | 37 |
| Finance Search
https://mcp.manawa.app/mcp |
answers-mcp | 31 |
| inboxguard
https://mcp.inboxguard.io/mcp |
answers-mcp | 28 |
| DMARC Examiner
https://mcp.dmarc-examiner.com/mcp |
answers-mcp | 21 |
| StatelessServer
https://monitoring.googleapis.com/mcp |
answers-mcp | 9 |
| pricetrack
https://pricetrack.dev/api/mcp |
answers-mcp | 8 |
| carrierscore-mcp-server
https://mcp.carrierscore.io/mcp |
answers-mcp | 8 |
| omniwatchguard
https://mcp.omniwatchguard.com/mcp |
answers-mcp | 7 |
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.