# Vision Helpdesk MCP by usefulapi (remote · vision-helpdesk.usefulapi.io)

Triage Vision Helpdesk tickets, read conversations, find clients and manage internal handoffs.

- Trust score: 18/100 (low)
- Change this week: −45
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

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

## Channel facts

- Endpoint: `https://vision-helpdesk.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.6.3`

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

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Vision Helpdesk MCP by usefulapi server?

Vision Helpdesk MCP by usefulapi is a hosted endpoint at https://vision-helpdesk.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-vision-helpdesk 'https://vision-helpdesk.usefulapi.io/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-vision-helpdesk": {
      "type": "http",
      "url": "https://vision-helpdesk.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-11-06 (score 18, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-02 (score 18, −48)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: 0.10 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Authorization: pass → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-10-31 (score 66, +3)

- [security improvement] Authorization: partial → pass
- [functional improvement] MCP protocol: fail → pass
- [functional] New prompt “find_tickets_by_reference_or_subject”
- [functional] New prompt “hand_off_a_support_ticket”
- [functional] New prompt “look_up_a_customer_before_replying”
- [functional] New prompt “review_overdue_support_tickets”
- [functional] MCP protocol version: 2025-06-18 → 2025-11-25
- [functional] Server version: 1.2.0 → 1.4.0
- [functional] Server version: 1.1.0 → 1.2.0
- [functional] Server version: 1.0.2 → 1.1.0

### 2026-10-30 (score 63, +1)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.0.1 → 1.0.2
- [functional] Server version: 1.0.0 → 1.0.1

### 2026-10-29 (score 62)

First indexed and scored.

## MCP tools (19)

### `vision_get_dashboard_counts` (~37 tokens)

Get dashboard counts

The ticket counts of the staff dashboard (quick view): for example new, open, overdue and assigned tickets. ticket / quick_view.

### `vision_list_tickets` (~187 tokens)

List tickets

List tickets, with at most ONE filter: a ticket id, a status id, a department id or a folder (inbox, new, overdue, assigned, trash, spam, draft). Without a filter it lists the tickets the API user can see. Status ids come from vision_list_statuses. ticket / get_tickets.

Input parameters:

- `department_id` (integer): Only tickets of this department id.
- `folder` (string): A ticket folder.
- `include_count` (boolean): Also ask for the total count.
- `limit` (integer): How many results to return, 1-100 (default 25).
- `offset` (integer): How many results to skip (default 0), for the next page.
- `status_id` (integer): Only tickets with this status id (vision_list_statuses).
- `ticket_id` (integer): Only this ticket.

### `vision_search_tickets` (~123 tokens)

Search tickets by reference or subject

Find tickets by an EXACT ticket reference (the ticket hash such as VHD-218) or an EXACT subject. Give one of them. ticket / get_tickets with a filter on ticket_hash or subject.

Input parameters:

- `limit` (integer): How many results to return, 1-100 (default 25).
- `offset` (integer): How many results to skip (default 0), for the next page.
- `subject` (string): The exact ticket subject.
- `ticket_hash` (string): The ticket reference, for example VHD-218.

### `vision_get_ticket` (~52 tokens)

Get ticket

One ticket with its fields (status, owner, priority, department...) and its posts (the conversation). ticket / ticket_details.

Input parameters:

- `ticket_id` (integer, required): Ticket id (the number, not the reference).

### `vision_list_tickets_by_tag` (~37 tokens)

List tickets by tag

Tickets that carry a tag, by tag id. ticket / tag_search.

Input parameters:

- `tag_id` (integer, required): Tag id.

### `vision_list_tickets_by_label` (~39 tokens)

List tickets by label

Tickets that carry a label, by label id. ticket / search_label_tickets.

Input parameters:

- `label_id` (integer, required): Label id.

### `vision_list_statuses` (~47 tokens)

List ticket statuses

The ticket statuses of a department (ids and names), for filters and status changes. ticket / get_status.

Input parameters:

- `department_id` (integer, required): Department id (statuses are per department).

### `vision_list_priorities` (~36 tokens)

List ticket priorities

The ticket priorities of a department (ids and names). ticket / get_priority.

Input parameters:

- `department_id` (integer, required): Department id.

### `vision_list_ticket_types` (~37 tokens)

List ticket types

The ticket types of a department (ids and names). ticket / get_ticket_type.

Input parameters:

- `department_id` (integer, required): Department id.

### `vision_list_clients` (~153 tokens)

List clients

List clients (customers), with at most ONE filter: a client id, a first name (exact), or a parent client id (lists that client's contacts). client / get_clients.

Input parameters:

- `client_id` (integer): Only this client.
- `first_name` (string): Clients with exactly this first name.
- `include_count` (boolean): Also ask for the total count.
- `limit` (integer): How many clients to return, 1-200 (default 50). The helpdesk returns the whole list; it is cut here.
- `offset` (integer): How many results to skip (default 0), for the next page.
- `parent_id` (integer): The contacts of this client.

### `vision_search_clients` (~79 tokens)

Search clients

Search clients by name or email text. client / list_clients.

Input parameters:

- `limit` (integer): How many clients to return, 1-200 (default 50).
- `offset` (integer): How many results to skip (default 0), for the next page.
- `text` (string, required): Part of a client name or email address.

### `vision_get_client_summary` (~34 tokens)

Get client summary

A client's summary: notes and ticket counts. client / get_summary.

Input parameters:

- `client_id` (integer, required): Client id.

### `vision_create_ticket` (~407 tokens)

Create ticket

WRITE: confirm:true required. open a new ticket for a client, given by client id or email. By default no email and no autoresponder is sent; a normal ticket's first post is created on behalf of the client and shown to the client. Internal tickets are staff-only and cannot have client recipients or email enabled. Look up the department, status, priority and type ids first (vision_list_statuses, vision_list_priorities, vision_list_ticket_types). ticket / open_new_ticket.

Input parameters:

- `as_client` (boolean): true (default): the post is the client's own; false: it is a staff reply.
- `cc` (string): CC email addresses.
- `client_email` (string): A valid client email address. Give this or client_id.
- `client_id` (integer): The client the ticket is for. Give this or client_email (not needed for an internal ticket).
- `confirm` (boolean, required): Required: confirm the exact change and any client-visible or email effects before setting true.
- `department_id` (integer, required): Department id.
- `domain_id` (integer, required): Domain id the ticket is opened under (1 on a single-domain helpdesk).
- `from` (string, required): The from address shown on the post, for example support@yourcompany.com.
- `internal` (boolean): An internal ticket (default false).
- `message` (string, required): The first post (HTML allowed).
- `owner_ids` (array): Staff ids that own the ticket.
- `priority_id` (integer, required): Priority id.
- `send_autoresponder` (boolean): Send the autoresponder email to the client (default false).
- `send_email` (boolean): Send the post by email to the client (default false).
- `status_id` (integer, required): Status id.
- `subject` (string, required): Ticket subject.
- `type_id` (integer, required): Ticket type id.
- `visible_to_client` (boolean): Show the first post to the client (default true).

### `vision_reply_to_ticket` (~158 tokens)

Reply to ticket

WRITE: confirm:true required. add a staff reply to a ticket. Say explicitly whether the client can see it (visible_to_client) and whether it is emailed to the client (send_email, default false). ticket / reply_ticket.

Input parameters:

- `confirm` (boolean, required): Required: confirm the exact change and any client-visible or email effects before setting true.
- `from` (string, required): The sender name or address shown on the reply.
- `message` (string, required): The reply text (HTML allowed).
- `send_email` (boolean): Email the reply to the client (default false).
- `ticket_id` (integer, required): Ticket id.
- `visible_to_client` (boolean, required): true: the client can see the reply; false: staff only.

### `vision_add_ticket_note` (~83 tokens)

Add ticket note

WRITE: confirm:true required. add an internal note to a ticket (not shown to the client). ticket / add_note with notetype 0.

Input parameters:

- `confirm` (boolean, required): Required: confirm the exact change and any client-visible or email effects before setting true.
- `note` (string, required): The note text.
- `ticket_id` (integer, required): Ticket id.

### `vision_add_client_note` (~78 tokens)

Add client note

WRITE: confirm:true required. add an internal note to a client record. ticket / add_note with notetype 1.

Input parameters:

- `client_id` (integer, required): Client id.
- `confirm` (boolean, required): Required: confirm the exact change and any client-visible or email effects before setting true.
- `note` (string, required): The note text.

### `vision_update_ticket_property` (~127 tokens)

Update ticket status, priority, department or type

WRITE: confirm:true required. change one property of a ticket to another id: status, priority, department or type. Look the ids up first (vision_list_statuses and the like). Changing the department can change which statuses and priorities apply. ticket / update_properties.

Input parameters:

- `confirm` (boolean, required): Required: confirm the exact change and any client-visible or email effects before setting true.
- `property` (string, required): What to change.
- `ticket_id` (integer, required): Ticket id.
- `value_id` (integer, required): The id of the new status, priority, department or type.

### `vision_assign_ticket_staff` (~93 tokens)

Assign or unassign ticket staff

WRITE: confirm:true required. add a staff member as an owner of a ticket, or remove one. ticket / update_properties with action staff.

Input parameters:

- `action` (string, required): assign or unassign.
- `confirm` (boolean, required): Required: confirm the exact change and any client-visible or email effects before setting true.
- `staff_id` (integer, required): Staff id.
- `ticket_id` (integer, required): Ticket id.

### `vision_add_ticket_tag` (~76 tokens)

Add tag to ticket

WRITE: confirm:true required. add a tag (by title) to a ticket. ticket / add_live_tag.

Input parameters:

- `confirm` (boolean, required): Required: confirm the exact change and any client-visible or email effects before setting true.
- `tag` (string, required): The tag title.
- `ticket_id` (integer, required): Ticket id.

## Diagnostics

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

## Score history

- 2026-11-06: 18
- 2026-11-05: 18
- 2026-11-04: 18
- 2026-11-03: 18
- 2026-11-02: 18
- 2026-11-01: 66
- 2026-10-31: 66
- 2026-10-30: 63
- 2026-10-29: 62

## Common questions

### What is the Vision Helpdesk MCP by usefulapi server?

Vision Helpdesk MCP by usefulapi is listed in the public MCP registry as io.usefulapi/vision-helpdesk. Triage Vision Helpdesk tickets, read conversations, find clients and manage internal handoffs. This page covers its hosted endpoint (https://vision-helpdesk.usefulapi.io/mcp).

### Is the Vision Helpdesk MCP by usefulapi server safe to use?

Vision Helpdesk MCP by usefulapi scores 18 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 Vision Helpdesk MCP by usefulapi server expose?

Vision Helpdesk MCP by usefulapi exposes 19 tools: vision_get_dashboard_counts, vision_list_tickets, vision_search_tickets, vision_get_ticket, vision_list_tickets_by_tag, and 14 more. Their descriptions and schemas cost roughly 1,883 tokens of context every time the server is loaded.

### Does the Vision Helpdesk MCP by usefulapi server require authentication?

Its publisher declares no required credentials for Vision Helpdesk MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the Vision Helpdesk MCP by usefulapi server still maintained?

Vision Helpdesk MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Vision Helpdesk MCP by usefulapi server?

VerifyMCP ran 4 checks on Vision Helpdesk MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about Vision Helpdesk MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://vision-helpdesk.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/vision-helpdesk/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-vision-helpdesk/vision-helpdesk.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-vision-helpdesk/vision-helpdesk/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/io-usefulapi-vision-helpdesk/vision-helpdesk.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-vision-helpdesk/vision-helpdesk