Deskpro MCP by usefulapi
io.usefulapi/deskprousefulapi.iostreamable-httpv1.40.4Scanned
Search tickets, people, organizations and KB articles in Deskpro, and create tickets and replies.
20 tools: 4 can delete or cancel things and 16 only read.
- Reads private data · 7
- Reads text others write · 12
- Can send data out · 1
- No findings
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
4 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Deskpro MCP by usefulapi can do
The Deskpro MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 20 tools. It can delete or cancel things (4 tools: deskpro_create_ticket, deskpro_update_ticket, deskpro_add_ticket_message and deskpro_create_organization). 16 tools only read.
7 tools read private data (deskpro_list_ticket_messages, deskpro_list_people, deskpro_get_person and 4 more); 12 tools bring in text other people can write (deskpro_list_tickets, deskpro_get_ticket, deskpro_list_ticket_messages and 9 more); 1 tool can send data out of your system (deskpro_add_ticket_message). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Oct 25, 2026, version 1.40.4.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
20 tools
Deletes or cancels 4Claude Code: deny
deskpro_add_ticket_messageAdd a message to a ticket as the key's agent.Can send data outNo findings
Why it is in this group
- The name "deskpro_add_ticket_message" says "add": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- outboundThe name "deskpro_add_ticket_message" says "add" and "message": it writes something other people read.
Description, as the server wrote it Add a message to a ticket as the key's agent. With is_note=true it is an internal agent note (not shown to the requester); with is_note=false it is a REPLY that the helpdesk emails to the requester — that cannot be unsent. Deskpro: POST /api/v2/tickets/{id}/messages.
Annotations the server declares
- title: Reply to a ticket or add a note
- destructiveHint: true
deskpro_create_organizationCreate a customer organization.No findings
Why it is in this group
- The name "deskpro_create_organization" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Create a customer organization. Email domains auto-associate people with matching addresses. Deskpro: POST /api/v2/organizations.
Annotations the server declares
- title: Create an organization
- destructiveHint: true
deskpro_create_ticketOpen a new ticket for a requester (by person id, or by email — Deskpro creates the person if the email is new) with a first message.No findings
Why it is in this group
- The name "deskpro_create_ticket" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Open a new ticket for a requester (by person id, or by email — Deskpro creates the person if the email is new) with a first message. Depending on the helpdesk's triggers this may email the requester. Returns the created ticket. Deskpro: POST /api/v2/tickets.
Annotations the server declares
- title: Create a ticket
- destructiveHint: true
deskpro_update_ticketChange a ticket's subject, status, assignment, department, organization, urgency, hold state or labels.No findings
Why it is in this group
- The name "deskpro_update_ticket" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Change a ticket's subject, status, assignment, department, organization, urgency, hold state or labels. Only the fields you pass are sent. Reversible by updating again. Cannot set the hidden (deleted/spam) status. Deskpro: PUT /api/v2/tickets/{id}.
Annotations the server declares
- title: Update a ticket
- destructiveHint: true
Only reads 16Show 16 read-only tools
deskpro_get_articleFetch a single knowledgebase article by id — title, content, status, categories and labels.No findings
Why it is in this group
- The name "deskpro_get_article" says "get": a word for reading.
Description, as the server wrote it Fetch a single knowledgebase article by id — title, content, status, categories and labels. Deskpro: GET /api/v2/articles/{id}.
Annotations the server declares
- title: Get one article
- readOnlyHint: true
deskpro_get_meReturn who the API key acts as — the auth method, the bound person id and their profile.No findings
Why it is in this group
- The name "deskpro_get_me" says "get": a word for reading.
Description, as the server wrote it Return who the API key acts as — the auth method, the bound person id and their profile. A cheap way to confirm the helpdesk URL and key are right. Deskpro: GET /api/v2/me.
Annotations the server declares
- title: Get the authenticated agent
- readOnlyHint: true
deskpro_get_organizationFetch a single organization by id — name, summary, email domains, labels, custom fields and ticket count.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "deskpro_get_organization" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "fetch" and "email": it reads mail.
- untrusted-inputThe description's first sentence says "fetch" and "email": it reads inbound email, which other people can write.
Description, as the server wrote it Fetch a single organization by id — name, summary, email domains, labels, custom fields and ticket count. Deskpro: GET /api/v2/organizations/{id}.
Annotations the server declares
- title: Get one organization
- readOnlyHint: true
deskpro_get_personFetch a single person by id — name, emails, phone numbers, organization, labels, custom fields and ticket count.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "deskpro_get_person" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "fetch" and "email": it reads mail.
- untrusted-inputThe description's first sentence says "fetch" and "email": it reads inbound email, which other people can write.
Description, as the server wrote it Fetch a single person by id — name, emails, phone numbers, organization, labels, custom fields and ticket count. Deskpro: GET /api/v2/people/{id}.
Annotations the server declares
- title: Get one person
- readOnlyHint: true
deskpro_get_ticketFetch a single ticket by id, with its subject, status, assignment, requester, labels, custom fields, SLA state and timing.Reads text others writeNo findings
Why it is in this group
- The name "deskpro_get_ticket" says "get": a word for reading.
What it can reach
- untrusted-inputThe name "deskpro_get_ticket" says "get" and "ticket": it reads issues, which other people can write.
- untrusted-inputThe description's first sentence says "fetch" and "ticket": it reads issues, which other people can write.
Description, as the server wrote it Fetch a single ticket by id, with its subject, status, assignment, requester, labels, custom fields, SLA state and timing. A merged ticket redirects to the ticket it was merged into. Deskpro: GET /api/v2/tickets/{id}.
Annotations the server declares
- title: Get one ticket
- readOnlyHint: true
deskpro_list_agentsList the helpdesk's agents (id, name, email, online state) — needed to assign a ticket.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "deskpro_list_agents" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "email": it reads mail.
- untrusted-inputThe description's first sentence says "list" and "email": it reads inbound email, which other people can write.
Description, as the server wrote it List the helpdesk's agents (id, name, email, online state) — needed to assign a ticket. Deskpro: GET /api/v2/agents.
Annotations the server declares
- title: List agents
- readOnlyHint: true
deskpro_list_articlesList knowledgebase articles, filterable by category, status and author.No findings
Why it is in this group
- The name "deskpro_list_articles" says "list": a word for reading.
Description, as the server wrote it List knowledgebase articles, filterable by category, status and author. Deskpro: GET /api/v2/articles.
Annotations the server declares
- title: List knowledgebase articles
- readOnlyHint: true
deskpro_list_departmentsList the ticket departments (id, title, parent, whether tickets/chat are enabled) — needed to route a new ticket.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "deskpro_list_departments" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "chat": it reads messages.
- untrusted-inputThe description's first sentence says "list" and "ticket": it reads issues, which other people can write.
Description, as the server wrote it List the ticket departments (id, title, parent, whether tickets/chat are enabled) — needed to route a new ticket. Deskpro: GET /api/v2/ticket_departments.
Annotations the server declares
- title: List ticket departments
- readOnlyHint: true
deskpro_list_organization_ticketsList the tickets belonging to one organization.Reads text others writeNo findings
Why it is in this group
- The name "deskpro_list_organization_tickets" says "list": a word for reading.
What it can reach
- untrusted-inputThe name "deskpro_list_organization_tickets" says "list" and "ticket": it reads issues, which other people can write.
- untrusted-inputThe description's first sentence says "list" and "ticket": it reads issues, which other people can write.
Description, as the server wrote it List the tickets belonging to one organization. Deskpro: GET /api/v2/organizations/{id}/tickets.
Annotations the server declares
- title: List an organization's tickets
- readOnlyHint: true
deskpro_list_organizationsList customer organizations, filterable by name or labels.No findings
Why it is in this group
- The name "deskpro_list_organizations" says "list": a word for reading.
Description, as the server wrote it List customer organizations, filterable by name or labels. Deskpro: GET /api/v2/organizations.
Annotations the server declares
- title: List organizations
- readOnlyHint: true
deskpro_list_peopleList people (end users and agents), searchable by name and filterable by email, organization or agent flag.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "deskpro_list_people" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "email": it reads mail.
- untrusted-inputThe description's first sentence says "list" and "email": it reads inbound email, which other people can write.
Description, as the server wrote it List people (end users and agents), searchable by name and filterable by email, organization or agent flag. Deskpro: GET /api/v2/people.
Annotations the server declares
- title: List people
- readOnlyHint: true
deskpro_list_person_ticketsList the tickets raised by one person — their support history.Reads text others writeNo findings
Why it is in this group
- The name "deskpro_list_person_tickets" says "list": a word for reading.
What it can reach
- untrusted-inputThe name "deskpro_list_person_tickets" says "list" and "ticket": it reads issues, which other people can write.
- untrusted-inputThe description's first sentence says "list" and "ticket": it reads issues, which other people can write.
Description, as the server wrote it List the tickets raised by one person — their support history. Deskpro: GET /api/v2/people/{id}/tickets.
Annotations the server declares
- title: List a person's tickets
- readOnlyHint: true
deskpro_list_ticket_messagesList the conversation on one ticket — every reply and agent note, with its author, date, is_agent_note flag and HTML body.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "deskpro_list_ticket_messages" says "list": a word for reading.
What it can reach
- private-dataThe name "deskpro_list_ticket_messages" says "list" and "message": it reads messages.
- private-dataThe description's first sentence says "list" and "conversation": it reads messages.
- untrusted-inputThe name "deskpro_list_ticket_messages" says "list" and "ticket": it reads issues, which other people can write.
- untrusted-inputThe description's first sentence says "list" and "conversation": it reads messages, which other people can write.
Description, as the server wrote it List the conversation on one ticket — every reply and agent note, with its author, date, is_agent_note flag and HTML body. Deskpro: GET /api/v2/tickets/{id}/messages.
Annotations the server declares
- title: List a ticket's messages
- readOnlyHint: true
deskpro_list_ticket_statusesList the ticket statuses and custom sub-statuses (status_type, status_code, title) configured on the helpdesk.Reads text others writeNo findings
Why it is in this group
- The name "deskpro_list_ticket_statuses" says "list": a word for reading.
What it can reach
- untrusted-inputThe name "deskpro_list_ticket_statuses" says "list" and "ticket": it reads issues, which other people can write.
- untrusted-inputThe description's first sentence says "list" and "ticket": it reads issues, which other people can write.
Description, as the server wrote it List the ticket statuses and custom sub-statuses (status_type, status_code, title) configured on the helpdesk. Deskpro: GET /api/v2/ticket_statuses.
Annotations the server declares
- title: List ticket statuses
- readOnlyHint: true
deskpro_list_ticketsList tickets, filtered by status, assigned agent, requester, organization, department or labels, and sorted.Reads text others writeNo findings
Why it is in this group
- The name "deskpro_list_tickets" says "list": a word for reading.
What it can reach
- untrusted-inputThe name "deskpro_list_tickets" says "list" and "ticket": it reads issues, which other people can write.
- untrusted-inputThe description's first sentence says "list" and "ticket": it reads issues, which other people can write.
Description, as the server wrote it List tickets, filtered by status, assigned agent, requester, organization, department or labels, and sorted. Returns ticket objects (id, ref, subject, ticket_status, agent, person, department, urgency, labels, dates) plus pagination meta. Deskpro: GET /api/v2/tickets.
Annotations the server declares
- title: List tickets
- readOnlyHint: true
deskpro_searchQuick search across tickets, people, organizations, articles, news, downloads, community topics and chats; results are grouped by type.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "deskpro_search" says "search": a word for reading.
What it can reach
- private-dataThe description's first sentence says "chat": it reads messages.
- untrusted-inputThe description's first sentence says "ticket": it reads issues, which other people can write.
Description, as the server wrote it Quick search across tickets, people, organizations, articles, news, downloads, community topics and chats; results are grouped by type. Deskpro: GET /api/v2/search.
Annotations the server declares
- title: Search the helpdesk
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
84 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.
- Reads private data7
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write12
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__deskpro__deskpro_add_ticket_message"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:35 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: The server redirected a POST to a different request.
Posture changes
- Oct 29, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 4 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://deskpro.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://deskpro.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 4 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://deskpro.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://deskpro.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Install
Pinned to version 1.40.4. Values in angle brackets are yours to fill in.
claude mcp add --transport http deskpro https://deskpro.usefulapi.io/mcpclaude mcp add --transport http deskpro https://deskpro.usefulapi.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__deskpro__deskpro_get_me",
"mcp__deskpro__deskpro_list_tickets",
"mcp__deskpro__deskpro_get_ticket",
"mcp__deskpro__deskpro_list_ticket_messages",
"mcp__deskpro__deskpro_list_people",
"mcp__deskpro__deskpro_get_person",
"mcp__deskpro__deskpro_list_person_tickets",
"mcp__deskpro__deskpro_list_organizations",
"mcp__deskpro__deskpro_get_organization",
"mcp__deskpro__deskpro_list_organization_tickets",
"mcp__deskpro__deskpro_list_articles",
"mcp__deskpro__deskpro_get_article",
"mcp__deskpro__deskpro_list_departments",
"mcp__deskpro__deskpro_list_agents",
"mcp__deskpro__deskpro_list_ticket_statuses",
"mcp__deskpro__deskpro_search"
],
"ask": [],
"deny": [
"mcp__deskpro__deskpro_create_ticket",
"mcp__deskpro__deskpro_update_ticket",
"mcp__deskpro__deskpro_add_ticket_message",
"mcp__deskpro__deskpro_create_organization"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as deskpro. Review it before you use it.
Capability tags behind 13 rules
- mcp__deskpro__deskpro_list_tickets untrusted-input
- mcp__deskpro__deskpro_get_ticket untrusted-input
- mcp__deskpro__deskpro_list_ticket_messages private-data, untrusted-input
- mcp__deskpro__deskpro_list_people private-data, untrusted-input
- mcp__deskpro__deskpro_get_person private-data, untrusted-input
- mcp__deskpro__deskpro_list_person_tickets untrusted-input
- mcp__deskpro__deskpro_get_organization private-data, untrusted-input
- mcp__deskpro__deskpro_list_organization_tickets untrusted-input
- mcp__deskpro__deskpro_list_departments private-data, untrusted-input
- mcp__deskpro__deskpro_list_agents private-data, untrusted-input
- mcp__deskpro__deskpro_list_ticket_statuses untrusted-input
- mcp__deskpro__deskpro_search private-data, untrusted-input
- mcp__deskpro__deskpro_add_ticket_message outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/deskpro/verify?hash=1690e0466049d63a359f5ccd5111418c63c932f529717049e3d34903e1690566" | jq -e '.changed == false'Pinned hash 1690e0466049, from Oct 25, 2026, 23:19 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.usefulapi/deskpro/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/deskpro)Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.
Deskpro MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Deskpro MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 20 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Deskpro MCP by usefulapi delete data?
- Yes. 4 tools can delete, cancel or revoke something: deskpro_create_ticket, deskpro_update_ticket, deskpro_add_ticket_message and deskpro_create_organization.
Can the Deskpro MCP by usefulapi do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Deskpro MCP by usefulapi have?
- 20 tools: 4 destructive, 16 read. deskpro_create_ticket, deskpro_update_ticket, deskpro_add_ticket_message, deskpro_create_organization, deskpro_get_me, deskpro_list_tickets, deskpro_get_ticket, deskpro_list_ticket_messages and 12 more.
Does the Deskpro MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Deskpro MCP by usefulapi send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): deskpro_add_ticket_message.
Has the Deskpro MCP by usefulapi changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.