Zendesk MCP
NPM · @MARKUSVANKEMPEN/ZENDESK-MCP-SERVER · SCANNED AUG 3
Zendesk MCP: 14 tools for AI agents — create, search, assign, comment, and close support tickets.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 53 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability40
- AI-judged instruction clarity (poor).Fail
- Tool/resource definitions use about 532 tokens (~38/item across 14 items; 14 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
npm · @markusvankempen/zendesk-mcp-server
claude mcp add markusvankempen-zendesk-mcp -- npx -y @markusvankempen/zendesk-mcp-server
codex mcp add markusvankempen-zendesk-mcp -- npx -y @markusvankempen/zendesk-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"markusvankempen-zendesk-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@markusvankempen/zendesk-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add markusvankempen-zendesk-mcp --command npx --arg -y --arg @markusvankempen/zendesk-mcp-server
mcp_servers:
markusvankempen-zendesk-mcp:
command: "npx"
args: ["-y", "@markusvankempen/zendesk-mcp-server"] {
"mcpServers": {
"markusvankempen-zendesk-mcp": {
"command": "npx",
"args": [
"-y",
"@markusvankempen/zendesk-mcp-server"
]
}
}
} 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.
- 2 Aug 26 +48
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Security disclosure: fail → unverified ▼ functional
- Dependency health: partial → unverified ▼ functional
- Schema quality: unverified → poor ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Maintenance: unverified → pass ▲ functional
- License: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Licence: Apache-2.0 functional
- 1 Aug 26 −11
- Tool coverage: 100 → unverified ▼ functional
- Dependency health: unverified → partial ▲ functional
- 31 Jul 26 −6
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −2
- Malware scan: pass → unverified ▼ security
- Dependency health: partial → unverified ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- 28 Jul 26 −16
- Tool coverage: 100 → unverified ▼ functional
- Dependency health: unverified → partial ▲ functional
- First check of Schema quality: unverified functional
- 27 Jul 26 42
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 3 Aug 2026 · Analysed npm/@markusvankempen/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 95 packages
95 packages in the resolved dependency tree · 95 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
add_ticket_comment ~41
Add a comment to an existing Zendesk ticket.
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | yes | — |
| public | boolean | — | — |
| ticket_id | integer | yes | — |
No output schema declared.
No examples provided.
assign_ticket ~47
Assign a Zendesk ticket to a group or to a specific agent.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee_email | string | — | — |
| group_name | string | — | — |
| ticket_id | integer | yes | — |
No output schema declared.
No examples provided.
close_ticket ~32
Mark a Zendesk ticket as solved.
| Name | Type | Req | Description |
|---|---|---|---|
| resolution_comment | string | — | — |
| ticket_id | integer | yes | — |
No output schema declared.
No examples provided.
create_ticket ~63
Create a Zendesk support ticket with correct requester attribution.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | — |
| priority | string | — | — |
| requester_email | string | yes | — |
| requester_name | string | — | — |
| subject | string | yes | — |
| tags | string | — | — |
No output schema declared.
No examples provided.
get_ticket ~25
Retrieve details of an existing Zendesk ticket.
| Name | Type | Req | Description |
|---|---|---|---|
| ticket_id | integer | yes | — |
No output schema declared.
No examples provided.
get_ticket_comments ~35
Retrieve comments and responses for a Zendesk ticket.
| Name | Type | Req | Description |
|---|---|---|---|
| include_private | boolean | — | — |
| ticket_id | integer | yes | — |
No output schema declared.
No examples provided.
get_ticket_metrics ~28
Retrieve SLA and timing metrics for a Zendesk ticket.
| Name | Type | Req | Description |
|---|---|---|---|
| ticket_id | integer | yes | — |
No output schema declared.
No examples provided.
get_user_by_email ~28
Look up a Zendesk user record by email address.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | — |
No output schema declared.
No examples provided.
list_all_tickets ~38
List tickets across the Zendesk instance, optionally filtered by status.
| Name | Type | Req | Description |
|---|---|---|---|
| max_results | integer | — | — |
| status | string | — | — |
No output schema declared.
No examples provided.
list_recent_tickets ~27
List the most recently updated Zendesk tickets.
| Name | Type | Req | Description |
|---|---|---|---|
| max_results | integer | — | — |
No output schema declared.
No examples provided.
list_tickets_for_requester ~37
List tickets created for a specific requester email.
| Name | Type | Req | Description |
|---|---|---|---|
| max_results | integer | — | — |
| requester_email | string | yes | — |
No output schema declared.
No examples provided.
reopen_ticket ~33
Reopen a solved or closed Zendesk ticket.
| Name | Type | Req | Description |
|---|---|---|---|
| reason | string | — | — |
| ticket_id | integer | yes | — |
No output schema declared.
No examples provided.
search_tickets ~37
Search Zendesk tickets using the Zendesk Search API query syntax.
| Name | Type | Req | Description |
|---|---|---|---|
| max_results | integer | — | — |
| query | string | yes | — |
No output schema declared.
No examples provided.
update_ticket ~61
Update an existing Zendesk ticket (status, priority, add comment, or tags).
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | — | — |
| priority | string | — | — |
| status | string | — | — |
| tags | string | — | — |
| ticket_id | integer | yes | — |
No output schema declared.
No examples provided.