Zendesk MCP by usefulapi
REMOTE · ZENDESK.USEFULAPI.IO
Read tickets, users, orgs, macros and satisfaction ratings; create, update and comment on tickets.
Available components
Last scanned (1 hour ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 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.
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.
- 1 Nov 26 −61
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → 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
- Stability: 0.97 → pass security
- MCP protocol: fail → pass ▲ functional
- New prompt “check_response_and_resolution_times_of_a_ticket” functional
- New prompt “create_a_ticket_reply_or_update_a_ticket” functional
- New prompt “find_customers_who_gave_a_low_satisfaction_rating” functional
- New prompt “find_tickets_with_zendesk_search” functional
- New prompt “read_a_ticket_with_its_comments” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.31.0 → 1.33.0 functional
- Server version: 1.30.0 → 1.31.0 functional
- Server version: 1.29.2 → 1.30.0 functional
- 30 Oct 26 +1
- Server version: 1.29.1 → 1.29.2 functional
- Server version: 1.29.0 → 1.29.1 functional
- 29 Oct 26 −1
- Stability: pass → 0.93 functional
- Server version: 1.28.0 → 1.29.0 functional
- Server version: 1.27.0 → 1.28.0 functional
- 28 Oct 26 0
- Server version: 1.25.0 → 1.27.0 functional
- 27 Oct 26 0
- Stability: 0.97 → pass security
- Server version: 1.24.0 → 1.25.0 functional
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 0
- Server version: 1.23.0 → 1.24.0 functional
- Server version: 1.22.0 → 1.23.0 functional
- Server version: 1.21.3 → 1.22.0 functional
- Server version: 1.21.0 → 1.21.3 functional
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 5 Nov 2026 · Probed https://zendesk.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 zendesk.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| usefulapi.io. | absent | 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://zendesk.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/zendesk/ |
| http (plaintext) | http://zendesk.usefulapi.io/mcp | Inconclusive | 302 | http://zendesk.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 →
zendesk_add_ticket_comment Add ticket comment ~96
MUTATING: add a comment to a ticket. `public` defaults to true (a reply visible to the requester); set it false for an internal agent note. Convenience over PUT /tickets/{id}.json.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Comment text (required). |
| id | integer | yes | Numeric ticket id (required). |
| public | boolean | – | Public reply (true, default) or internal note (false). |
No output schema declared.
No examples provided.
zendesk_create_ticket Create ticket ~204
MUTATING: create a new support ticket. `subject` and `comment_body` are required; the comment becomes the ticket's first message. Zendesk REST: POST /tickets.json.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee_id | integer | – | Agent id to assign the ticket to. |
| comment_body | string | yes | Body of the ticket's first comment (required). |
| comment_public | boolean | – | Whether the first comment is public (default true). |
| group_id | integer | – | Group id to assign the ticket to. |
| priority | string | – | Priority: urgent | high | normal | low. |
| requester_id | integer | – | User id of the ticket requester. |
| status | string | – | Status: new | open | pending | hold | solved | closed. |
| subject | string | yes | Ticket subject/title (required). |
| tags | array | – | Tags to set on the ticket. |
| type | string | – | Type: problem | incident | question | task. |
No output schema declared.
No examples provided.
zendesk_current_user Current user (whoami) ~36
Return the currently authenticated user — a quick way to verify credentials and subdomain. Zendesk REST: GET /users/me.json.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zendesk_execute_view Execute view ~109
Run a saved view by id and return the matching tickets. Zendesk REST: GET /views/{id}/execute.json.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Numeric view id (required; from zendesk_list_views). |
| page | integer | – | Page number for offset pagination. |
| per_page | integer | – | Records per page (max 100). |
| sort_by | string | – | Field to sort the resulting tickets by. |
| sort_order | string | – | Sort direction: asc or desc. |
No output schema declared.
No examples provided.
zendesk_get_organization Get organization ~42
Fetch a single organization by id. Zendesk REST: GET /organizations/{id}.json.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Numeric organization id (required). |
No output schema declared.
No examples provided.
zendesk_get_ticket Get ticket ~41
Fetch a single ticket by id. Zendesk REST: GET /tickets/{id}.json.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Numeric ticket id (required). |
No output schema declared.
No examples provided.
zendesk_get_ticket_metrics Get ticket metrics ~48
Fetch SLA / response / resolution time metrics for a ticket. Zendesk REST: GET /tickets/{id}/metrics.json.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Numeric ticket id (required). |
No output schema declared.
No examples provided.
zendesk_get_user Get user ~41
Fetch a single user by id. Zendesk REST: GET /users/{id}.json.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Numeric user id (required). |
No output schema declared.
No examples provided.
zendesk_list_groups List groups ~50
List agent groups. Zendesk REST: GET /groups.json.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number for offset pagination. |
| per_page | integer | – | Records per page (max 100). |
No output schema declared.
No examples provided.
zendesk_list_macros List macros ~68
List macros (reusable sets of ticket actions/replies agents apply). Zendesk REST: GET /macros.json.
| Name | Type | Req | Description |
|---|---|---|---|
| access | string | – | Filter by access, e.g. 'personal' or 'shared'. |
| active | boolean | – | If true, only active macros. |
No output schema declared.
No examples provided.
zendesk_list_organizations List organizations ~53
List organizations (offset pagination). Zendesk REST: GET /organizations.json.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number for offset pagination. |
| per_page | integer | – | Records per page (max 100). |
No output schema declared.
No examples provided.
zendesk_list_satisfaction_ratings List satisfaction ratings ~75
List customer satisfaction (CSAT) ratings, optionally filtered by score. Zendesk REST: GET /satisfaction_ratings.json.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number for offset pagination. |
| score | string | – | Filter by rating state, e.g. 'good', 'bad', or 'received'. |
No output schema declared.
No examples provided.
zendesk_list_ticket_comments List ticket comments ~80
List the comments (public replies and internal notes) on a ticket, oldest first. Zendesk REST: GET /tickets/{id}/comments.json.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Numeric ticket id (required). |
| page | integer | – | Page number for offset pagination. |
| per_page | integer | – | Records per page (max 100). |
No output schema declared.
No examples provided.
zendesk_list_ticket_fields List ticket fields ~42
List all standard and custom ticket fields — useful for discovering field ids/values before creating or updating tickets. Zendesk REST: GET /ticket_fields.json.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zendesk_list_tickets List tickets ~83
List recent tickets (offset pagination). Zendesk REST: GET /tickets.json.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number for offset pagination. |
| per_page | integer | – | Records per page (max 100). |
| sort_by | string | – | Field to sort by. |
| sort_order | string | – | Sort direction: asc or desc (default asc). |
No output schema declared.
No examples provided.
zendesk_list_views List views ~68
List saved ticket views (curated ticket lists). Use zendesk_execute_view to run one. Zendesk REST: GET /views.json.
| Name | Type | Req | Description |
|---|---|---|---|
| access | string | – | Filter by access: 'personal' or 'shared'. |
| active | boolean | – | If true, only active views. |
No output schema declared.
No examples provided.
zendesk_search Search ~133
Unified search across tickets, users, organizations and groups using Zendesk search syntax. Examples: `type:ticket status:open`, `type:user email:jane@acme.com`, `type:organization name:acme`. Zendesk REST: GET /search.json.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number for offset pagination. |
| query | string | yes | Zendesk search query, e.g. 'type:ticket status:open priority:high' (required). |
| sort_by | string | – | Field to sort by. |
| sort_order | string | – | Sort direction: asc or desc (default desc). |
No output schema declared.
No examples provided.
zendesk_search_users Search users ~94
Find users by name, email, phone, or other attributes. Zendesk REST: GET /users/search.json.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number for offset pagination. |
| per_page | integer | – | Records per page (max 100). |
| query | string | yes | Search string — a name, email, phone, or external id, e.g. 'jane@acme.com' (required). |
No output schema declared.
No examples provided.
zendesk_update_ticket Update ticket ~223
MUTATING: update an existing ticket. Provide the ticket `id` plus at least one field to change (status, priority, assignee_id, group_id, type, tags, or a comment). Zendesk REST: PUT /tickets/{id}.json.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee_id | integer | – | Agent id to (re)assign to. |
| comment_body | string | – | Body of a comment to add as part of this update. |
| comment_public | boolean | – | Whether the added comment is public (default true; set false for an internal note). |
| group_id | integer | – | Group id to (re)assign to. |
| id | integer | yes | Numeric ticket id (required). |
| priority | string | – | New priority: urgent | high | normal | low. |
| status | string | – | New status: new | open | pending | hold | solved | closed. |
| tags | array | – | Tags to set on the ticket (replaces existing). |
| type | string | – | New type: problem | incident | question | task. |
No output schema declared.
No examples provided.
How do I install the Zendesk MCP by usefulapi server?
Zendesk MCP by usefulapi is a hosted endpoint at https://zendesk.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 · zendesk.usefulapi.io
claude mcp add --transport http io-usefulapi-zendesk 'https://zendesk.usefulapi.io/mcp'
What is the Zendesk MCP by usefulapi server?
Zendesk MCP by usefulapi is listed in the public MCP registry as io.usefulapi/zendesk. Read tickets, users, orgs, macros and satisfaction ratings; create, update and comment on tickets. This page covers its hosted endpoint (https://zendesk.usefulapi.io/mcp).
Is the Zendesk MCP by usefulapi server safe to use?
Zendesk 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 Zendesk MCP by usefulapi server expose?
Zendesk MCP by usefulapi exposes 19 tools: zendesk_search, zendesk_list_tickets, zendesk_get_ticket, zendesk_list_ticket_comments, zendesk_current_user, and 14 more. Their descriptions and schemas cost roughly 1,586 tokens of context every time the server is loaded.
Does the Zendesk MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Zendesk 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 Zendesk MCP by usefulapi server still maintained?
Zendesk MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.