Home / MCP registry index / io.usefulapi/eventzilla
Eventzilla MCP by usefulapi
io.usefulapi/eventzilla in the official MCP registry.
Endpoint https://eventzilla.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Read Eventzilla events, tickets, orders, attendees and users; open or close ticket sales.
We read its 11 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
eventzilla_list_events eventzilla_get_event eventzilla_list_event_transactions eventzilla_list_event_attendees eventzilla_list_ticket_types eventzilla_list_categories eventzilla_get_attendee eventzilla_get_transaction eventzilla_list_users eventzilla_get_user eventzilla_toggle_event_sales
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-eventzilla)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.