Home / MCP registry index / io.usefulapi/tito
Tito MCP by usefulapi
io.usefulapi/tito in the official MCP registry.
Endpoint https://tito.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Look up events, releases, tickets, registrations and discount codes, and edit tickets and codes.
We read its 20 tools on 2026-10-21. 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
tito_whoami tito_list_events tito_get_event tito_list_releases tito_get_release tito_list_tickets tito_get_ticket tito_list_registrations tito_get_registration tito_list_discount_codes tito_get_discount_code tito_list_activities tito_list_questions tito_list_answers tito_list_checkin_lists tito_list_refunds tito_create_discount_code tito_update_discount_code tito_create_ticket tito_update_ticket
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-tito)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.