io.usefulapi/zendesk

REMOTE · ZENDESK.USEFULAPI.IO · SCANNED AUG 3

Read tickets, users, orgs, macros and satisfaction ratings; create, update and comment on tickets.

Available components

58 58 Trust /100

Trust breakdown (6 categories)

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 →

Endpoint Security46

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
Authorisation not fully verified: this server exposes a tool marked destructive (zendesk_create_ticket) and its handshake is open, but we could not confirm whether a tool call is gated, so we do not assert it is callable unauthenticated. View diagnostics → Unverified
HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. 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 & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability81

AI-judged instruction clarity (excellent).Pass
Tool/resource definitions use about 1586 tokens (~83/item across 19 items; 19 tools + 0 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management3

Stability observed for 1 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

Capabilities60

Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · zendesk.usefulapi.io

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http io-usefulapi-zendesk https://zendesk.usefulapi.io/mcp

# ~/.codex/config.toml

[mcp_servers.io-usefulapi-zendesk]
url = "https://zendesk.usefulapi.io/mcp"

// opencode.json

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

# add to OpenClaw

openclaw mcp add io-usefulapi-zendesk --url https://zendesk.usefulapi.io/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  io-usefulapi-zendesk:
    url: "https://zendesk.usefulapi.io/mcp"

// mcp.json

{
  "mcpServers": {
    "io-usefulapi-zendesk": {
      "type": "http",
      "url": "https://zendesk.usefulapi.io/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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 Aug 26 +27
- Authorization: Authorisation not fully verified: this server exposes a tool marked destructive (zendesk_create_ticket) and its handshake is open, but we could not confirm whether a tool call is gated, so we do not assert it is callable unauthenticated. security
- New tool “zendesk_update_ticket”, which the server declares destructive security
- New tool “zendesk_add_ticket_comment”, which the server declares destructive security
- New tool “zendesk_create_ticket”, which the server declares destructive security
- Schema quality: unverified → fail ▼ functional
- Schema quality: unverified → excellent ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → pass ▲ functional
- Stability: unverified → 0.03 ▲ functional
- First check of Tool coverage: 100 functional
- New tool “zendesk_list_ticket_fields” functional
- New tool “zendesk_list_ticket_comments” functional
- New tool “zendesk_list_satisfaction_ratings” functional
- New tool “zendesk_list_organizations” functional
- New tool “zendesk_list_macros” functional
- New tool “zendesk_search_users” functional
- New tool “zendesk_current_user” functional
- New tool “zendesk_execute_view” functional
- New tool “zendesk_get_organization” functional
- New tool “zendesk_get_ticket” functional
- New tool “zendesk_get_ticket_metrics” functional
- New tool “zendesk_get_user” functional
- New tool “zendesk_list_groups” functional
- New tool “zendesk_search” functional
- New tool “zendesk_list_views” functional
- New tool “zendesk_list_tickets” functional
2 Aug 26 +13
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “zendesk_search_users” was removed ▼ security
- Tool “zendesk_create_ticket” was removed ▼ security
- Tool “zendesk_current_user” was removed ▼ security
- Tool “zendesk_execute_view” was removed ▼ security
- Tool “zendesk_add_ticket_comment” was removed ▼ security
- Tool “zendesk_get_organization” was removed ▼ security
- Tool “zendesk_get_ticket” was removed ▼ security
- Tool “zendesk_get_ticket_metrics” was removed ▼ security
- Tool “zendesk_get_user” was removed ▼ security
- Tool “zendesk_list_groups” was removed ▼ security
- Tool “zendesk_list_macros” was removed ▼ security
- Tool “zendesk_list_organizations” was removed ▼ security
- Tool “zendesk_list_satisfaction_ratings” was removed ▼ security
- Tool “zendesk_list_ticket_comments” was removed ▼ security
- Tool “zendesk_list_ticket_fields” was removed ▼ security
- Tool “zendesk_list_tickets” was removed ▼ security
- Tool “zendesk_list_views” was removed ▼ security
- Tool “zendesk_search” was removed ▼ security
- Tool “zendesk_update_ticket” was removed ▼ security
- Authorization: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Authorization: partial security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: unverified functional
- First check of Schema quality: unverified functional
- First check of Schema quality: unverified functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: pass functional
- First check of Schema quality: excellent functional
- First check of Schema quality: fail functional
1 Aug 26 18

First indexed and scored.

Show 1 earlier entry Hide earlier entries

Diagnostics

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 Aug 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	1 Aug 2026	30 Oct 2026	ECDSA 256	ECDSA-SHA256	7856fc188636d98b0ef6b5471bcaf2e9
SANs: usefulapi.io, zendesk.usefulapi.io, *.zendesk.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

DNSSEC insecure

Validation of zendesk.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 No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result	No authorisation required
HTTP status	200

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://zendesk.usefulapi.io/mcp	Verified	200
http (plaintext)	http://zendesk.usefulapi.io/mcp	Inconclusive	401

MCP tools — 19 exposed · ~1,586 tokens

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.

Tool Tokens

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.

Input Output Examples

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.

Input Output Examples

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 Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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 Output Examples

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.

Input Output Examples

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.

Input Output Examples

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:[email protected]`, `type:organization name:acme`. Zendesk REST: GET /search.json.

Input Output Examples

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.

Input Output Examples

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. '[email protected]' (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.

Input Output Examples

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.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

1 Aug 3 Aug