compliance_check4 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 |
|---|---|---|
| device-house
https://device-house-mcp.fly.dev/mcp |
answers-mcp | 21 |
| orphicone-vigo
https://lsoatzzwpltpydwyfqqv.supabase.co/functions/v1/vigo-mcp |
answers-mcp | 10 |
| listinggood
https://listinggood.com/mcp |
answers-mcp | 8 |
| structureclerk
https://structureclerk.ca/api/mcp-http |
answers-mcp | 5 |
4 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.