Zd Cli MCP Server

zd-cli PyPI v1.3.3

Published by andmarios — 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 CLI and MCP Server for Claude Code - Search tickets, manage support, and analyze metrics

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 93/100

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 − 7 = 93. 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:

PointsAdoption-risk factor
−6 capability blast radius (high) — 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.

Findings 3

high Shell/command execution in server code (src/zendesk_skill/crypto.py)MTC-SRC-002

In the server's implementation (`src/zendesk_skill/crypto.py:41`): 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: try: result = subprocess.run( ["ioreg", "-rd1", "-c", "IOPlatformExpertDevice"], captu

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 src/zendesk_skill/crypto.py

high Shell/command execution in server code (src/zendesk_skill/queries.py)MTC-SRC-002

In the server's implementation (`src/zendesk_skill/queries.py:348`): 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: try: result = subprocess.run( ["jq", jq_query, file_path], capture_output=True,

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 src/zendesk_skill/queries.py

low Shell/command execution in packaging/dev tooling (src/zendesk_skill/scripts/analyze_support_metrics.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`src/zendesk_skill/scripts/analyze_support_metrics.py:332`): 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: om API result = subprocess.run( ["uv", "run", "zd-cli", "ticket-metrics", str(tid)], cap

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 src/zendesk_skill/scripts/analyze_support_metrics.py

Tools 26

Each tool and what it can reach — statically extracted from the published source.

  • zendesk_get_attachmentingests untrusted input
  • zendesk_get_linked_incidentsingests untrusted input
  • zendesk_add_private_noteno sensitive capability
  • zendesk_add_public_noteno sensitive capability
  • zendesk_auth_statusno sensitive capability
  • zendesk_create_ticketno sensitive capability
  • zendesk_get_current_userno sensitive capability
  • zendesk_get_organizationno sensitive capability
  • zendesk_get_satisfaction_ratingno sensitive capability
  • zendesk_get_satisfaction_ratingsno sensitive capability
Show 16 more tools ↓
  • zendesk_get_ticketno sensitive capability
  • zendesk_get_ticket_detailsno sensitive capability
  • zendesk_get_ticket_metricsno sensitive capability
  • zendesk_get_userno sensitive capability
  • zendesk_get_view_countno sensitive capability
  • zendesk_get_view_ticketsno sensitive capability
  • zendesk_list_groupsno sensitive capability
  • zendesk_list_sla_policiesno sensitive capability
  • zendesk_list_tagsno sensitive capability
  • zendesk_list_ticket_metricsno sensitive capability
  • zendesk_list_viewsno sensitive capability
  • zendesk_query_storedno sensitive capability
  • zendesk_searchno sensitive capability
  • zendesk_search_organizationsno sensitive capability
  • zendesk_search_usersno sensitive capability
  • zendesk_update_ticketno sensitive capability

What this scan could not see

Versions 1

Scan 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.

VersionScoreFindingsEngineScanned
v1.3.3 latest A 93/100 3 1.13.0 2026-08-25

Embed this score

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.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/zd-cli/badge.svg)](https://mcptrustchecker.com/registry/zd-cli)
HTML
<a href="https://mcptrustchecker.com/registry/zd-cli"><img src="https://mcptrustchecker.com/registry/zd-cli/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/zd-cli/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

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 zd-cli --online --registry pypi

Use the free API → How scoring works

More in Business & CRM