validate_email9 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 |
|---|---|---|
| ia-qa-toolbox
https://www.ia-qa.com/mcp |
answers-mcp | 152 |
| qiniso
https://qiniso.qinisolabs.workers.dev/mcp |
answers-mcp | 56 |
| misarmail
https://api.misar.io/mail/mcp |
answers-mcp | 54 |
| toolforte
https://toolforte.com/api/mcp/mcp |
answers-mcp | 40 |
| eu-verify
https://data.greeneris.io/mcp |
answers-mcp | 19 |
| validation-api
https://validation-api.dropcoin.workers.dev/mcp |
answers-mcp | 6 |
| fabtally-valid
https://valid.fabtally.com/mcp |
answers-mcp | 5 |
| email-validator-api
https://api.lazy-mac.com/email-validator/mcp |
answers-mcp | 4 |
| Validate Email Address MCP Server
https://deva.dillilabs.com/mcp |
answers-mcp | 1 |
9 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.