`list_events`

15 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
agendaforge-mcp https://mcp.agendaforge.app/mcp	answers-mcp	55
chronary https://api.chronary.ai/mcp	answers-mcp	54
peppolstatus https://mcp.peppolstatus.com	answers-mcp	51
lumify-mcp https://lumify.ai/mcp	answers-mcp	25
webhook-studio https://webhook-studio.com/mcp	answers-mcp	17
openvan-mcp https://mcp.openvan.camp/mcp	answers-mcp	14
toots-tickets https://toots.brussels/mcp	answers-mcp	12
openwein.de https://www.openwein.de/mcp	answers-mcp	12
masterminds-hq-mcp https://mcp.mastermindshq.business/mcp	answers-mcp	10
binasmart https://bina.et/mcp	answers-mcp	10
NEMPulse MCP https://nempulse.com.au/mcp	answers-mcp	8
etc-gigs https://emergingtechcenter.com/api/mcp	answers-mcp	8
travel-trends-public https://travel-trends.mmatinca.eu/mcp/v1	answers-mcp	8
devrel-directory https://devrel.directory/mcp	answers-mcp	6
clearmarket https://api.clearmarket.fyi/mcp	answers-mcp	6

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