Skills/PyPI/zammad-mcp-server

zammad-mcp-server@0.2.2

VERIFIED· not started

Publisher claims: "Production-ready Zammad MCP Server for Zammad 6.0+ and 7.x, including 7.2. Connect Claude, Cursor, and LLMs to your helpdesk via MCP." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher softoft-orga · publishing for 186 daysInstalls 420Last detonated 3 h ago
$claude mcp add zammad-mcp-server -- uvx zammad-mcp-server
WatchReport an issue

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
the dependency install step · every file read, file written and host contacted by what ran
Not tested
server startup · the tool list · tool behavior

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
ZAMMAD_HTTP_TOKENZAMMAD_OAUTH2_TOKENZAMMAD_PASSWORD or --client-secretConfiguration, not credentials: MCP_ALLOWED_CATEGORIES, MCP_ALLOWED_GROUPS, MCP_ALLOWED_ORGANIZATIONS, MCP_AUDIT_LOG_PATH, MCP_DEFAULT_PERMISSION, MCP_DENIED_TOOLS, MCP_RATE_LIMIT_PER_MINUTE, MCP_SERVER_HOST, MCP_SERVER_PATH, MCP_SERVER_PORT, MCP_STRIP_HTML, MCP_TRANSPORT, ZAMMAD_URL, ZAMMAD_USERNAME
Where it talks to
no vendor host named in the code
What we saw when it ran
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Connect it with a scoped credential, under the guard. It asks for ZAMMAD_HTTP_TOKEN, ZAMMAD_OAUTH2_TOKEN, ZAMMAD_PASSWORD and talks to its vendor. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.

$vet-skills run --net declared -- uvx zammad-mcp-server

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-21 and scored it 88/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.1sprocessdependency install exit 1 ·
0.1sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.1sprocessscript backend runs setup only
0.1sprocessno install scripts to re-run

Static findings

LOW
Authorization escalation languagedocs/DEPLOYMENT.md:619 · Authorization escalation language · informational: not an instruction file# Admin access: Allow everything (use with caution)Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.
AST01
MEDIUM
File permission modification commandDockerfile:26 · File permission modification command — agent changes file ownership/permissionsRUN useradd -m -u 1000 appuser && chown -R appuser:appuser /appFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.
AST05
MEDIUM
MCP server using network transport (SSE/HTTP)Dockerfile:35 · MCP server using network transport (SSE/HTTP) — data sent over networkCMD ["zammad-mcp-server", "--transport", "http", "--host", "0.0.0.0", "--port", "8000"]Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
MEDIUM
MCP server using network transport (SSE/HTTP)tests/test_transport_cli.py:7 · MCP server using network transport (SSE/HTTP) — data sent over networkfrom zammad_mcp_server.cli import default_http_path, parse_server_args, run_serverFix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
MEDIUM
Destructive file system command detectedDockerfile:19 · Destructive file system command detected&& rm -rf /var/lib/apt/lists/*Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05

Cost to the agent

Instructions loaded
≈72 tok
1 file · 44 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

No advisories in OSV for zammad-mcp-server@0.2.2 as of 3 h ago. This is the package itself, not its dependencies.