`resolve`

9 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
pipeworx-gateway https://gateway.pipeworx.io/string-db/mcp	answers-mcp	36
pipeworx-gateway https://gateway.pipeworx.io/bioregistry/mcp	answers-mcp	35
pipeworx-gateway https://gateway.pipeworx.io/cactus/mcp	answers-mcp	33
whiteintel-mcp-server https://whiteintel.dev/api/mcp	answers-mcp	24
stackresolve https://mcp.stackresolve.dev/mcp	answers-mcp	15
kortex https://kortex.rohnelt.dev/mcp	answers-mcp	10
Tern https://mcp.tern0.com/mcp	answers-mcp	3
Tern https://world-resolver-mcp.ajithisaac.workers.dev/mcp	answers-mcp	3
entity-resolve https://entity-resolve.x402supply.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.