Back to the tool index

get_deals

11 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.

serverresult when we called ittools
wafergraph-mcp
https://wafergraph-mcp.jwpalm99.workers.dev/mcp
answers-mcp 30
dealwize-mcp
https://api.dealwize.co/api/v1/mcp
answers-mcp 14
buywhere-catalog
https://mcp.buywhere.ai/mcp
answers-mcp 13
buywhere-catalog
https://api.buywhere.ai/mcp
answers-mcp 13
stymie-golf
https://mcp-production-680d.up.railway.app/mcp
answers-mcp 13
lmk-today
https://lmk.today/api/ucp/mcp
answers-mcp 13
propscorer
https://www.propscorer.com/api/mcp
answers-mcp 11
propscorer
https://mcp.propscorer.com
answers-mcp 11
tickets4pets
https://tickets4pets.org/mcp
answers-mcp 7
gocdkeys
https://gocdkeys.com/agent/mcp
answers-mcp 5
brickpulse
https://mcp.brickpulse.ai/mcp
answers-mcp 5

11 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.