`get_service_info`

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.

server	result when we called it	tools
Xcatcher Remote MCP https://xcatcher.top/mcp	answers-mcp	17
machine-inbox https://machineinbox.com/mcp	answers-mcp	11
pro.magicmaster/mastering https://magicmaster.pro/mcp	answers-mcp	11
mydriverparis https://mcp-mydriverparis.mydriverparis.workers.dev/mcp	answers-mcp	10
merchant-context https://api.merchant.atomandbits.com/mcp	answers-mcp	9
ugc-pocket-mcp https://ugcpocket.com/mcp	answers-mcp	8
Glowjakt https://mcp.glowjakt.se/mcp	answers-mcp	7
rides-rs https://rides.rs/api/mcp	answers-mcp	6
liedetectortest https://liedetectortest.com/wp-json/ldt-mcp/v1/mcp	answers-mcp	5
gc-airport-transfers https://gc-airporttransfers.com/wp-json/atb-gateway/v1/mcp	answers-mcp	4
sukimalabo-tester https://egbtsqygtbkdfkywjofb.supabase.co/functions/v1/sukimalabo-tester	answers-mcp	3

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.