Zammad (Softoft-Orga) MCP Server

zammad-mcp-server PyPI v0.1.1

Published by softoft-orga — 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.

Production-ready Zammad MCP Server for Zammad 6.0+ and 7.x (tested on 7.1). Connect Claude, Cursor, and LLMs to your helpdesk via MCP.

Trust grade
A
99/100
Last scanned get badge →
Trust
A · 99/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
Minimal
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 = 99/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 − 1 = 99. 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
−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 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 27

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

  • create_articleno sensitive capability
  • create_groupno sensitive capability
  • create_organizationno sensitive capability
  • create_ticketno sensitive capability
  • create_userno sensitive capability
  • delete_organizationno sensitive capability
  • delete_ticketno sensitive capability
  • delete_userno sensitive capability
  • get_allowed_toolsno sensitive capability
  • get_current_userno sensitive capability
Show 17 more tools ↓
  • get_groupno sensitive capability
  • get_organizationno sensitive capability
  • get_prioritiesno sensitive capability
  • get_server_infono sensitive capability
  • get_ticketno sensitive capability
  • get_ticket_articlesno sensitive capability
  • get_ticket_statesno sensitive capability
  • get_ticket_statsno sensitive capability
  • get_userno sensitive capability
  • health_checkno sensitive capability
  • list_groupsno sensitive capability
  • search_organizationsno sensitive capability
  • search_ticketsno sensitive capability
  • search_usersno sensitive capability
  • update_organizationno sensitive capability
  • update_ticketno sensitive capability
  • update_userno 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
v0.1.1 latest A 99/100 0 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 · 99/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/zammad-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/zammad-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/zammad-mcp-server"><img src="https://mcptrustchecker.com/registry/zammad-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/zammad-mcp-server/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 zammad-mcp-server --online --registry pypi

Use the free API → How scoring works

Other implementations of Zammad 1

Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →

More in AI & Agents