# io.usefulapi/deskpro (remote · deskpro.usefulapi.io)

Search tickets, people, organizations and KB articles in Deskpro, and create tickets and replies.

- Trust score: 77/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-03

## Components

- remote · `deskpro.usefulapi.io`: 77/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-deskpro/deskpro.md), [page](https://verifymcp.io/servers/io-usefulapi-deskpro/deskpro)

## Channel facts

- Endpoint: `https://deskpro.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-03.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http io-usefulapi-deskpro 'https://deskpro.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-deskpro": {
      "url": "https://deskpro.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-deskpro": {
      "type": "http",
      "url": "https://deskpro.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-deskpro]
url = "https://deskpro.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-deskpro": {
      "type": "remote",
      "url": "https://deskpro.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-deskpro --url 'https://deskpro.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-deskpro:
    url: "https://deskpro.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-deskpro": {
      "Transport": "http",
      "Url": "https://deskpro.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-deskpro -t streamable-http -u 'https://deskpro.usefulapi.io/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-03 (score 77, +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.

### 2026-10-02 (score 76, 0)

- [functional] Server version: 1.3.0 → 1.5.1

### 2026-10-01 (score 76, +5)

- [security improvement] HTTPS: unverified → pass
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.0.0 → 1.3.0

### 2026-09-30 (score 71, +53)

- [security improvement] Authorization: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [security] First check of Judged manipulation: pass
- [security] First check of Authorization: partial
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] 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

### 2026-09-29 (score 18)

First indexed and scored.

## MCP tools (20)

### `deskpro_get_me` (~54 tokens)

Get the authenticated agent

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.

### `deskpro_list_tickets` (~265 tokens)

List tickets

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.

Input parameters:

- `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.

### `deskpro_get_ticket` (~110 tokens)

Get one ticket

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}.

Input parameters:

- `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, required): The ticket's numeric id.

### `deskpro_list_ticket_messages` (~130 tokens)

List a ticket's messages

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.

Input parameters:

- `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, required): The ticket's numeric id.

### `deskpro_list_people` (~186 tokens)

List people

List people (end users and agents), searchable by name and filterable by email, organization or agent flag. Deskpro: GET /api/v2/people.

Input parameters:

- `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.

### `deskpro_get_person` (~94 tokens)

Get one person

Fetch a single person by id — name, emails, phone numbers, organization, labels, custom fields and ticket count. Deskpro: GET /api/v2/people/{id}.

Input parameters:

- `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, required): The person's numeric id.

### `deskpro_list_person_tickets` (~80 tokens)

List a person's tickets

List the tickets raised by one person — their support history. Deskpro: GET /api/v2/people/{id}/tickets.

Input parameters:

- `count` (integer): Results per page, 1-200.
- `page` (integer): Page number, starting at 1.
- `person_id` (integer, required): The person's numeric id.

### `deskpro_list_organizations` (~135 tokens)

List organizations

List customer organizations, filterable by name or labels. Deskpro: GET /api/v2/organizations.

Input parameters:

- `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.

### `deskpro_get_organization` (~93 tokens)

Get one organization

Fetch a single organization by id — name, summary, email domains, labels, custom fields and ticket count. Deskpro: GET /api/v2/organizations/{id}.

Input parameters:

- `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, required): The organization's numeric id.

### `deskpro_list_organization_tickets` (~77 tokens)

List an organization's tickets

List the tickets belonging to one organization. Deskpro: GET /api/v2/organizations/{id}/tickets.

Input parameters:

- `count` (integer): Results per page, 1-200.
- `organization_id` (integer, required): The organization's numeric id.
- `page` (integer): Page number, starting at 1.

### `deskpro_list_articles` (~121 tokens)

List knowledgebase articles

List knowledgebase articles, filterable by category, status and author. Deskpro: GET /api/v2/articles.

Input parameters:

- `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.

### `deskpro_get_article` (~54 tokens)

Get one article

Fetch a single knowledgebase article by id — title, content, status, categories and labels. Deskpro: GET /api/v2/articles/{id}.

Input parameters:

- `article_id` (integer, required): The article's numeric id.

### `deskpro_list_departments` (~78 tokens)

List ticket departments

List the ticket departments (id, title, parent, whether tickets/chat are enabled) — needed to route a new ticket. Deskpro: GET /api/v2/ticket_departments.

Input parameters:

- `count` (integer): Results per page, 1-200.
- `page` (integer): Page number, starting at 1.

### `deskpro_list_agents` (~94 tokens)

List agents

List the helpdesk's agents (id, name, email, online state) — needed to assign a ticket. Deskpro: GET /api/v2/agents.

Input parameters:

- `count` (integer): Results per page, 1-200.
- `online`: 1 = online only, 0 = offline only, -1 = both.
- `page` (integer): Page number, starting at 1.

### `deskpro_list_ticket_statuses` (~91 tokens)

List ticket statuses

List the ticket statuses and custom sub-statuses (status_type, status_code, title) configured on the helpdesk. Deskpro: GET /api/v2/ticket_statuses.

Input parameters:

- `count` (integer): Results per page, 1-200.
- `page` (integer): Page number, starting at 1.
- `status_type` (string): Only statuses of this type.

### `deskpro_search` (~82 tokens)

Search the helpdesk

Quick search across tickets, people, organizations, articles, news, downloads, community topics and chats; results are grouped by type. Deskpro: GET /api/v2/search.

Input parameters:

- `q` (string, required): The search term.
- `types` (string): Comma-separated types to search, e.g. ticket,person,organization. Omit for all.

### `deskpro_create_ticket` (~290 tokens)

Create a ticket

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.

Input parameters:

- `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, required): 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, required): The ticket subject.
- `urgency` (integer): Urgency 1-10.

### `deskpro_update_ticket` (~245 tokens)

Update a ticket

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}.

Input parameters:

- `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, required): The ticket's numeric id.
- `urgency` (integer): Urgency 1-10.

### `deskpro_add_ticket_message` (~137 tokens)

Reply to a ticket or add a note

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.

Input parameters:

- `format` (string): Format of the body. Default text.
- `is_note` (boolean, required): true = internal agent note; false = public reply to the requester.
- `message` (string, required): The message body.
- `ticket_id` (integer, required): The ticket's numeric id.

### `deskpro_create_organization` (~87 tokens)

Create an organization

Create a customer organization. Email domains auto-associate people with matching addresses. Deskpro: POST /api/v2/organizations.

Input parameters:

- `email_domains` (array): Email domains belonging to the organization, e.g. example.com.
- `labels` (array): Labels to set.
- `name` (string, required): The organization's name.
- `summary` (string): A short description.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-deskpro/deskpro#diagnostics

## Score history

- 2026-10-03: 77
- 2026-10-02: 76
- 2026-10-01: 76
- 2026-09-30: 71
- 2026-09-29: 18

## Common questions

### 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.

## Links

- Remote endpoint: https://deskpro.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-deskpro/deskpro.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-deskpro/deskpro.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-deskpro/deskpro