Vision Helpdesk MCP by usefulapi
REMOTE · VISION-HELPDESK.USEFULAPI.IO
Triage Vision Helpdesk tickets, read conversations, find clients and manage internal handoffs.
Available components
Last scanned (6 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 6 Nov 2026.
Category CRM and Sales
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- 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
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
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.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 2 Nov 26 −48
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.10 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- 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 functional
- 30 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.1 → 1.0.2 functional
- Server version: 1.0.0 → 1.0.1 functional
- 29 Oct 26 62
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 6 Nov 2026 · Probed https://vision-helpdesk.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 vision-helpdesk.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://vision-helpdesk.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/vision-helpdesk/ |
| http (plaintext) | http://vision-helpdesk.usefulapi.io/mcp | Inconclusive | 302 | http://vision-helpdesk.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 →
vision_add_client_note Add client note ~78
WRITE: confirm:true required. add an internal note to a client record. ticket / add_note with notetype 1.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | integer | yes | Client id. |
| confirm | boolean | yes | Required: confirm the exact change and any client-visible or email effects before setting true. |
| note | string | yes | The note text. |
No output schema declared.
No examples provided.
vision_add_ticket_note Add ticket note ~83
WRITE: confirm:true required. add an internal note to a ticket (not shown to the client). ticket / add_note with notetype 0.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | yes | Required: confirm the exact change and any client-visible or email effects before setting true. |
| note | string | yes | The note text. |
| ticket_id | integer | yes | Ticket id. |
No output schema declared.
No examples provided.
vision_add_ticket_tag Add tag to ticket ~76
WRITE: confirm:true required. add a tag (by title) to a ticket. ticket / add_live_tag.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | yes | Required: confirm the exact change and any client-visible or email effects before setting true. |
| tag | string | yes | The tag title. |
| ticket_id | integer | yes | Ticket id. |
No output schema declared.
No examples provided.
vision_assign_ticket_staff Assign or unassign ticket staff ~93
WRITE: confirm:true required. add a staff member as an owner of a ticket, or remove one. ticket / update_properties with action staff.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | assign or unassign. |
| confirm | boolean | yes | Required: confirm the exact change and any client-visible or email effects before setting true. |
| staff_id | integer | yes | Staff id. |
| ticket_id | integer | yes | Ticket id. |
No output schema declared.
No examples provided.
vision_create_ticket Create ticket ~407
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Required: confirm the exact change and any client-visible or email effects before setting true. |
| department_id | integer | yes | Department id. |
| domain_id | integer | yes | Domain id the ticket is opened under (1 on a single-domain helpdesk). |
| from | string | yes | The from address shown on the post, for example support@yourcompany.com. |
| internal | boolean | – | An internal ticket (default false). |
| message | string | yes | The first post (HTML allowed). |
| owner_ids | array | – | Staff ids that own the ticket. |
| priority_id | integer | yes | 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 | yes | Status id. |
| subject | string | yes | Ticket subject. |
| type_id | integer | yes | Ticket type id. |
| visible_to_client | boolean | – | Show the first post to the client (default true). |
No output schema declared.
No examples provided.
vision_get_client_summary Get client summary ~34
A client's summary: notes and ticket counts. client / get_summary.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | integer | yes | Client id. |
No output schema declared.
No examples provided.
vision_get_dashboard_counts Get dashboard counts ~37
The ticket counts of the staff dashboard (quick view): for example new, open, overdue and assigned tickets. ticket / quick_view.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
vision_get_ticket Get ticket ~52
One ticket with its fields (status, owner, priority, department...) and its posts (the conversation). ticket / ticket_details.
| Name | Type | Req | Description |
|---|---|---|---|
| ticket_id | integer | yes | Ticket id (the number, not the reference). |
No output schema declared.
No examples provided.
vision_list_clients List clients ~153
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
vision_list_priorities List ticket priorities ~36
The ticket priorities of a department (ids and names). ticket / get_priority.
| Name | Type | Req | Description |
|---|---|---|---|
| department_id | integer | yes | Department id. |
No output schema declared.
No examples provided.
vision_list_statuses List ticket statuses ~47
The ticket statuses of a department (ids and names), for filters and status changes. ticket / get_status.
| Name | Type | Req | Description |
|---|---|---|---|
| department_id | integer | yes | Department id (statuses are per department). |
No output schema declared.
No examples provided.
vision_list_ticket_types List ticket types ~37
The ticket types of a department (ids and names). ticket / get_ticket_type.
| Name | Type | Req | Description |
|---|---|---|---|
| department_id | integer | yes | Department id. |
No output schema declared.
No examples provided.
vision_list_tickets List tickets ~187
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
vision_list_tickets_by_label List tickets by label ~39
Tickets that carry a label, by label id. ticket / search_label_tickets.
| Name | Type | Req | Description |
|---|---|---|---|
| label_id | integer | yes | Label id. |
No output schema declared.
No examples provided.
vision_list_tickets_by_tag List tickets by tag ~37
Tickets that carry a tag, by tag id. ticket / tag_search.
| Name | Type | Req | Description |
|---|---|---|---|
| tag_id | integer | yes | Tag id. |
No output schema declared.
No examples provided.
vision_reply_to_ticket Reply to ticket ~158
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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | yes | Required: confirm the exact change and any client-visible or email effects before setting true. |
| from | string | yes | The sender name or address shown on the reply. |
| message | string | yes | The reply text (HTML allowed). |
| send_email | boolean | – | Email the reply to the client (default false). |
| ticket_id | integer | yes | Ticket id. |
| visible_to_client | boolean | yes | true: the client can see the reply; false: staff only. |
No output schema declared.
No examples provided.
vision_search_clients Search clients ~79
Search clients by name or email text. client / list_clients.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Part of a client name or email address. |
No output schema declared.
No examples provided.
vision_search_tickets Search tickets by reference or subject ~123
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
vision_update_ticket_property Update ticket status, priority, department or type ~127
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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | yes | Required: confirm the exact change and any client-visible or email effects before setting true. |
| property | string | yes | What to change. |
| ticket_id | integer | yes | Ticket id. |
| value_id | integer | yes | The id of the new status, priority, department or type. |
No output schema declared.
No examples provided.
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.
remote · vision-helpdesk.usefulapi.io
claude mcp add --transport http io-usefulapi-vision-helpdesk 'https://vision-helpdesk.usefulapi.io/mcp'
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.