ip_lookup9 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 |
|---|---|---|
| blixtworks
https://www.blixtworks.com/mcp |
answers-mcp | 68 |
| arch-tools-mcp
https://arch-tools-mcp.onrender.com/sse |
answers-mcp | 63 |
| arch-tools-mcp
https://arch-tools-mcp.onrender.com/mcp |
answers-mcp | 63 |
| arch-tools
https://archtools.dev/mcp |
answers-mcp | 63 |
| contrastapi
https://api.contrastcyber.com/mcp/ |
answers-mcp | 55 |
| domainposture.com
https://www.domainposture.com/mcp/mcp |
answers-mcp | 22 |
| hackmyip
https://hackmyip.com/mcp |
answers-mcp | 15 |
| Abundance APIs
https://abundanceapis.com/mcp |
answers-mcp | 7 |
| RDAP API
https://rdapapi.io/mcp/rdap |
answers-mcp | 7 |
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.