zendesk-mcp
PyPI
v0.1.4
Published by michaelrice — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
Zendesk MCP server for Claude Code and other MCP clients
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
In a packaging/dev/install script (shipped, but not the server runtime) (`.github/scripts/smoke_test.py:53`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: flush=True) proc = subprocess.Popen( command, stdin=subprocess.PIPE, stdout=subprocess.PIPE
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server .github/scripts/smoke_test.py
Each tool and what it can reach — statically extracted from the published source.
zendesk_download_attachmentingests untrusted inputzendesk_get_commentsingests untrusted inputzendesk_get_organizationingests untrusted inputzendesk_list_attachmentsingests untrusted inputzendesk_add_tagno sensitive capabilityzendesk_apply_macrono sensitive capabilityzendesk_assign_ticketno sensitive capabilityzendesk_create_ticketno sensitive capabilityzendesk_get_git_zen_linksno sensitive capabilityzendesk_get_group_usersno sensitive capabilityzendesk_get_groupsno sensitive capabilityzendesk_get_ticketno sensitive capabilityzendesk_get_ticketsno sensitive capabilityzendesk_get_time_trackingno sensitive capabilityzendesk_get_viewno sensitive capabilityzendesk_get_view_ticketsno sensitive capabilityzendesk_list_custom_statusesno sensitive capabilityzendesk_list_macrosno sensitive capabilityzendesk_list_viewsno sensitive capabilityzendesk_log_timeno sensitive capabilityzendesk_post_commentno sensitive capabilityzendesk_post_internal_noteno sensitive capabilityzendesk_preview_macrono sensitive capabilityzendesk_remove_tagno sensitive capabilityzendesk_search_ticketsno sensitive capabilityzendesk_search_usersno sensitive capabilityzendesk_set_ticket_statusno sensitive capabilityzendesk_ticket_to_gitlab_contextno sensitive capabilityzendesk_update_ticketno sensitive capabilityScan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.1.4 latest |
A 96/100 | 1 | 1.13.0 | 2026-08-25 |
v0.1.3 |
A 96/100 | 1 | 1.12.1 | 2026-08-12 |
v0.1.2 |
A 96/100 | 0 | 1.12.1 | 2026-07-27 |
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan zendesk-mcp --online --registry pypi
Independent packages implementing the same tool, scanned with the same engine. Compare all 9 side by side →
Deep Zendesk MCP server for your AI assistant: search, draft, update and translate Help Center articles and manage Support tickets end to end — comments, triage and image attachments.
MCP Server for Zendesk API with enhanced features
Zendesk MCP server — 14 support ticket tools for AI agents. Cursor, VS Code, Claude Desktop, watsonx Orchestrate, IBM Code Engine SSE.
Zendesk MCP server for Ticketing and Help Center APIs
Local MCP server exposing Zendesk Support, Macros, attachments, and Help Center reads to Claude Desktop and Claude Code. 23 tools.
Zendesk MCP Pack — tickets, users, organizations via OAuth.
Free public tax reference data — GST/VAT, income, company and capital-gains tax rules for 50+ countries.
The approval gate for unattended UCP buying agents — a policy/approval MCP proxy in front of a merchant's UCP checkout endpoint.
Autotask PSA MCP server. Generic entity query/get/create/update across the full REST API plus convenience tools for tickets, companies, contacts, projects, tasks and time entries. AI-safe with readonly mode and destructive-action confirmation. stdio + opt
MCP server for B2C Commerce developer experience tools
Search, compare and contact real-world companies through a public MCP business directory.
Norwegian business register (Brønnøysundregistrene) as an MCP server — companies, roles, subunits and annual accounts, with the register's silent traps encoded as guards.