Home / MCP registry index / io.usefulapi/zendesk
Zendesk MCP by usefulapi
io.usefulapi/zendesk in the official MCP registry.
Endpoint https://zendesk.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Read tickets, users, orgs, macros and satisfaction ratings; create, update and comment on tickets.
We read its 19 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
zendesk_search zendesk_list_tickets zendesk_get_ticket zendesk_list_ticket_comments zendesk_current_user zendesk_get_user zendesk_search_users zendesk_list_organizations zendesk_get_organization zendesk_list_groups zendesk_list_views zendesk_execute_view zendesk_list_macros zendesk_list_ticket_fields zendesk_get_ticket_metrics zendesk_list_satisfaction_ratings zendesk_create_ticket zendesk_update_ticket zendesk_add_ticket_comment
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-zendesk)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.