io.usefulapi/deskpro
REMOTE · DESKPRO.USEFULAPI.IO · SCANNED OCT 3
Search tickets, people, organizations and KB articles in Deskpro, and create tickets and replies.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2503 tokens (~125/item across 20 items; 20 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.usefulapi/deskpro MCP server?
io.usefulapi/deskpro is a hosted endpoint at https://deskpro.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · deskpro.usefulapi.io
claude mcp add --transport http io-usefulapi-deskpro 'https://deskpro.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-deskpro": {
"url": "https://deskpro.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-deskpro": {
"type": "http",
"url": "https://deskpro.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-deskpro] url = "https://deskpro.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-deskpro": {
"type": "remote",
"url": "https://deskpro.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-deskpro --url 'https://deskpro.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-deskpro:
url: "https://deskpro.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-deskpro": {
"Transport": "http",
"Url": "https://deskpro.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-deskpro -t streamable-http -u 'https://deskpro.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-deskpro": {
"type": "http",
"url": "https://deskpro.usefulapi.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 0
- Server version: 1.3.0 → 1.5.1 functional
- 1 Oct 26 +5
- HTTPS: unverified → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.3.0 functional
- 30 Sept 26 +53
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Judged manipulation: pass security
- First check of Authorization: partial security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- 29 Sept 26 18
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Oct 2026 · Probed https://deskpro.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of deskpro.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://deskpro.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://deskpro.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://deskpro.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://deskpro.usefulapi.io/mcp |
| Authorisation server | https://deskpro.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://deskpro.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://deskpro.usefulapi.io/mcp | HTTPS enforced | 301 | https://deskpro.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
deskpro_add_ticket_message Reply to a ticket or add a note ~137
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.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Format of the body. Default text. |
| is_note | boolean | yes | true = internal agent note; false = public reply to the requester. |
| message | string | yes | The message body. |
| ticket_id | integer | yes | The ticket's numeric id. |
No output schema declared.
No examples provided.
deskpro_create_organization Create an organization ~87
Create a customer organization. Email domains auto-associate people with matching addresses. Deskpro: POST /api/v2/organizations.
| Name | Type | Req | Description |
|---|---|---|---|
| email_domains | array | – | Email domains belonging to the organization, e.g. example.com. |
| labels | array | – | Labels to set. |
| name | string | yes | The organization's name. |
| summary | string | – | A short description. |
No output schema declared.
No examples provided.
deskpro_create_ticket Create a ticket ~290
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | integer | – | Assign to this agent id. |
| agent_team | integer | – | Assign to this agent team id. |
| department | integer | – | Department id (see deskpro_list_departments). |
| labels | array | – | Labels to set. |
| message | string | yes | The first message body. |
| message_format | string | – | Format of the message body. Default text. |
| organization | integer | – | Organization id. |
| person_email | string | – | The requester's email (used when person_id is not given). |
| person_id | integer | – | The requester's person id. |
| person_name | string | – | The requester's name, for a new person. |
| status | string | – | Ticket status: awaiting_agent, awaiting_user, pending or resolved, optionally with a custom sub-status id suffix (e.g. pending.5 — see deskpro_list_ticket_statuses). The hidden (deleted/spam) status… |
| subject | string | yes | The ticket subject. |
| urgency | integer | – | Urgency 1-10. |
No output schema declared.
No examples provided.
deskpro_get_article Get one article ~54
Fetch a single knowledgebase article by id — title, content, status, categories and labels. Deskpro: GET /api/v2/articles/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| article_id | integer | yes | The article's numeric id. |
No output schema declared.
No examples provided.
deskpro_get_me Get the authenticated agent ~54
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
deskpro_get_organization Get one organization ~93
Fetch a single organization by id — name, summary, email domains, labels, custom fields and ticket count. Deskpro: GET /api/v2/organizations/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| include | string | – | Comma-separated related object types to side-load into the response's `linked` section, e.g. person,agent,department,organization. |
| organization_id | integer | yes | The organization's numeric id. |
No output schema declared.
No examples provided.
deskpro_get_person Get one person ~94
Fetch a single person by id — name, emails, phone numbers, organization, labels, custom fields and ticket count. Deskpro: GET /api/v2/people/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| include | string | – | Comma-separated related object types to side-load into the response's `linked` section, e.g. person,agent,department,organization. |
| person_id | integer | yes | The person's numeric id. |
No output schema declared.
No examples provided.
deskpro_get_ticket Get one ticket ~110
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| include | string | – | Comma-separated related object types to side-load into the response's `linked` section, e.g. person,agent,department,organization. |
| ticket_id | integer | yes | The ticket's numeric id. |
No output schema declared.
No examples provided.
deskpro_list_agents List agents ~94
List the helpdesk's agents (id, name, email, online state) — needed to assign a ticket. Deskpro: GET /api/v2/agents.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Results per page, 1-200. |
| online | – | – | 1 = online only, 0 = offline only, -1 = both. |
| page | integer | – | Page number, starting at 1. |
No output schema declared.
No examples provided.
deskpro_list_articles List knowledgebase articles ~121
List knowledgebase articles, filterable by category, status and author. Deskpro: GET /api/v2/articles.
| Name | Type | Req | Description |
|---|---|---|---|
| author | string | – | Only articles by this author id, or 'me' for the key's agent. |
| category | integer | – | Only articles in this category id. |
| count | integer | – | Results per page, 1-200. |
| order_by | string | – | Sort field. |
| page | integer | – | Page number, starting at 1. |
| status | string | – | Only articles in this status. |
No output schema declared.
No examples provided.
deskpro_list_departments List ticket departments ~78
List the ticket departments (id, title, parent, whether tickets/chat are enabled) — needed to route a new ticket. Deskpro: GET /api/v2/ticket_departments.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Results per page, 1-200. |
| page | integer | – | Page number, starting at 1. |
No output schema declared.
No examples provided.
deskpro_list_organization_tickets List an organization's tickets ~77
List the tickets belonging to one organization. Deskpro: GET /api/v2/organizations/{id}/tickets.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Results per page, 1-200. |
| organization_id | integer | yes | The organization's numeric id. |
| page | integer | – | Page number, starting at 1. |
No output schema declared.
No examples provided.
deskpro_list_organizations List organizations ~135
List customer organizations, filterable by name or labels. Deskpro: GET /api/v2/organizations.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Results per page, 1-200. |
| include | string | – | Comma-separated related object types to side-load into the response's `linked` section, e.g. person,agent,department,organization. |
| labels | string | – | Only organizations with these labels (comma-separated). |
| name | string | – | Only the organization with this name. |
| page | integer | – | Page number, starting at 1. |
| search | string | – | Search on name. |
No output schema declared.
No examples provided.
deskpro_list_people List people ~186
List people (end users and agents), searchable by name and filterable by email, organization or agent flag. Deskpro: GET /api/v2/people.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Results per page, 1-200. |
| include | string | – | Comma-separated related object types to side-load into the response's `linked` section, e.g. person,agent,department,organization. |
| is_agent | boolean | – | true for agents only, false for end users only. |
| order_by | string | – | Sort field. |
| order_dir | string | – | Sort direction. |
| organization | string | – | Only members of these organization ids (comma-separated). |
| page | integer | – | Page number, starting at 1. |
| primary_email | string | – | Only the person with this primary email. |
| search | string | – | Search on name. |
No output schema declared.
No examples provided.
deskpro_list_person_tickets List a person's tickets ~80
List the tickets raised by one person — their support history. Deskpro: GET /api/v2/people/{id}/tickets.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Results per page, 1-200. |
| page | integer | – | Page number, starting at 1. |
| person_id | integer | yes | The person's numeric id. |
No output schema declared.
No examples provided.
deskpro_list_ticket_messages List a ticket's messages ~130
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.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Results per page, 1-200. |
| include | string | – | Comma-separated related object types to side-load into the response's `linked` section, e.g. person,agent,department,organization. |
| page | integer | – | Page number, starting at 1. |
| ticket_id | integer | yes | The ticket's numeric id. |
No output schema declared.
No examples provided.
deskpro_list_ticket_statuses List ticket statuses ~91
List the ticket statuses and custom sub-statuses (status_type, status_code, title) configured on the helpdesk. Deskpro: GET /api/v2/ticket_statuses.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Results per page, 1-200. |
| page | integer | – | Page number, starting at 1. |
| status_type | string | – | Only statuses of this type. |
No output schema declared.
No examples provided.
deskpro_list_tickets List tickets ~265
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | integer | – | Only tickets assigned to this agent id. |
| count | integer | – | Results per page, 1-200. |
| department | integer | – | Only tickets in this department id. |
| group_sort | string | – | Sort direction. |
| ids | string | – | Fetch exactly these ticket ids (comma-separated). |
| include | string | – | Comma-separated related object types to side-load into the response's `linked` section, e.g. person,agent,department,organization. |
| labels | string | – | Only tickets with these labels (comma-separated). |
| order_by | string | – | Sort field. |
| organization | integer | – | Only tickets from this organization id. |
| page | integer | – | Page number, starting at 1. |
| person | integer | – | Only tickets raised by this person id. |
| status | string | – | Only tickets in this status, e.g. awaiting_agent, awaiting_user, pending, resolved. |
No output schema declared.
No examples provided.
deskpro_search Search the helpdesk ~82
Quick search across tickets, people, organizations, articles, news, downloads, community topics and chats; results are grouped by type. Deskpro: GET /api/v2/search.
| Name | Type | Req | Description |
|---|---|---|---|
| q | string | yes | The search term. |
| types | string | – | Comma-separated types to search, e.g. ticket,person,organization. Omit for all. |
No output schema declared.
No examples provided.
deskpro_update_ticket Update a ticket ~245
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | integer | – | Assign to this agent id. |
| agent_team | integer | – | Assign to this agent team id. |
| department | integer | – | Move to this department id. |
| is_hold | boolean | – | Put the ticket on hold (true) or take it off hold (false). |
| labels | array | – | The ticket's labels. |
| organization | integer | – | Set the organization id. |
| status | string | – | Ticket status: awaiting_agent, awaiting_user, pending or resolved, optionally with a custom sub-status id suffix (e.g. pending.5 — see deskpro_list_ticket_statuses). The hidden (deleted/spam) status… |
| subject | string | – | New subject. |
| ticket_id | integer | yes | The ticket's numeric id. |
| urgency | integer | – | Urgency 1-10. |
No output schema declared.
No examples provided.
What is the io.usefulapi/deskpro MCP server?
io.usefulapi/deskpro is an MCP server listed in the public MCP registry as io.usefulapi/deskpro. Search tickets, people, organizations and KB articles in Deskpro, and create tickets and replies. This page covers its hosted endpoint (https://deskpro.usefulapi.io/mcp).
Is the io.usefulapi/deskpro MCP server safe to use?
io.usefulapi/deskpro scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.usefulapi/deskpro MCP server expose?
io.usefulapi/deskpro exposes 20 tools: deskpro_get_me, deskpro_list_tickets, deskpro_get_ticket, deskpro_list_ticket_messages, deskpro_list_people, and 15 more. Their descriptions and schemas cost roughly 2,503 tokens of context every time the server is loaded.
Does the io.usefulapi/deskpro MCP server require authentication?
Yes. io.usefulapi/deskpro asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.usefulapi/deskpro MCP server still maintained?
io.usefulapi/deskpro is still listed as active in the MCP registry. We last reached this channel on 3 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.