verify_email8 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 |
|---|---|---|
| Novence https://api.novence.ai/mcp |
answers-mcp | 43 |
| clariBI MCP Server https://claribi.com/mcp/v1/ |
answers-mcp | 26 |
| clariBI MCP Server https://claribi.com/mcp/v1/sse |
answers-mcp | 26 |
| verifly-mcp-server https://verifly.email/mcp |
answers-mcp | 17 |
| Qualisend https://app.qualisend.com/api/mcp |
answers-mcp | 12 |
| layercall https://www.layercall.com/api/mcp |
answers-mcp | 7 |
| verifox https://mcp.verifox.ai/mcp |
answers-mcp | 6 |
| proof-inbox https://mcp.proofinbox.com/mcp |
answers-mcp | 3 |
8 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.