Home / MCP registry index / io.usefulapi/deskpro
Deskpro MCP by usefulapi
io.usefulapi/deskpro in the official MCP registry.
Endpoint https://deskpro.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Search tickets, people, organizations and KB articles in Deskpro, and create tickets and replies.
We read its 20 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
deskpro_get_me deskpro_list_tickets deskpro_get_ticket deskpro_list_ticket_messages deskpro_list_people deskpro_get_person deskpro_list_person_tickets deskpro_list_organizations deskpro_get_organization deskpro_list_organization_tickets deskpro_list_articles deskpro_get_article deskpro_list_departments deskpro_list_agents deskpro_list_ticket_statuses deskpro_search deskpro_create_ticket deskpro_update_ticket deskpro_add_ticket_message deskpro_create_organization
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-deskpro)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.