create_watch7 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 |
|---|---|---|
| com.wingmanprotocol.agent/gateway https://agent.wingmanprotocol.com/mcp |
answers-mcp | 57 |
| com.wingmanprotocol.agent/gateway https://wingmanprotocol.com/mcp |
answers-mcp | 57 |
| zenvault https://api.zenvault.eu/mcp |
answers-mcp | 44 |
| Vaquill Legal Research https://mcp.vaquill.ai/s/_ |
answers-mcp | 25 |
| longwatch https://longwatch.dev/mcp |
answers-mcp | 18 |
| watchtower-sanctions-screening https://watchtower-api.com/mcp |
answers-mcp | 13 |
| ZoningVerdict https://zoningverdict.com/api/mcp?ref=mcp-registry |
answers-mcp | 7 |
7 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.