Skip to content

Zammad MCP by usefulapi

io.usefulapi/zammadusefulapi.iostreamable-httpv1.27.5Scanned

Search and read Zammad tickets, customers and organizations; add notes, replies and ticket updates.

19 tools: 4 can delete or cancel things and 15 only read.

Tools: 4 delete, 0 irreversible, 0 write, 15 read.
  • Reads private data · 5
  • Reads text others write · 19
  • Can send data out · 1
  • 2 findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

4 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Zammad MCP by usefulapi can do

The Zammad MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 19 tools. It can delete or cancel things (4 tools: zammad_add_internal_note, zammad_reply_to_ticket, zammad_update_ticket and zammad_create_ticket). 15 tools only read.

5 tools read private data (zammad_get_me, zammad_list_ticket_articles, zammad_search_users and 2 more); 19 tools bring in text other people can write (zammad_get_me, zammad_search_tickets, zammad_list_tickets and 16 more); 1 tool can send data out of your system (zammad_reply_to_ticket). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 2 findings (credentials-mention). Each one comes with the text it matched.

Last scanned Oct 25, 2026, version 1.27.5.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

19 tools

Deletes or cancels 4Claude Code: deny
  • zammad_add_internal_noteWRITE: add an INTERNAL note (visible to agents only, never e-mailed to the customer) to ONE ticket.Reads text others writeNo findings

    Why it is in this group

    • The name "zammad_add_internal_note" says "add": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    WRITE: add an INTERNAL note (visible to agents only, never e-mailed to the customer) to ONE ticket. Needs an agent's token (a customer's token is refused, because Zammad would make the note public). The ticket's other data is not changed. POST /api/v1/ticket_articles with type=note, internal=true.

    Annotations the server declares

    • title: Add internal note
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • zammad_create_ticketWRITE: create ONE new ticket for an EXISTING customer (by e-mail address or user id) in a group, with a first article recorded as written by the customer (type note or phone).Reads text others writeNo findings

    Why it is in this group

    • The name "zammad_create_ticket" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    WRITE: create ONE new ticket for an EXISTING customer (by e-mail address or user id) in a group, with a first article recorded as written by the customer (type note or phone). It does not send an e-mail by itself, but the instance's triggers may (for example an automatic confirmation to the customer). It never creates new users. POST /api/v1/tickets.

    Annotations the server declares

    • title: Create ticket
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • zammad_reply_to_ticketWRITE: send a customer-visible reply on ONE ticket.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "zammad_reply_to_ticket" says "reply": a word for sending, and what is sent cannot be taken back.
    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe name "zammad_reply_to_ticket" says "reply": it sends or publishes something to other people.
    Description, as the server wrote it
    WRITE: send a customer-visible reply on ONE ticket. THIS E-MAILS A REAL PERSON: the reply is delivered by e-mail to exactly ONE recipient and cannot be recalled. By default the recipient is the ticket's customer (looked up from the ticket); `to` may name one other single address. No cc, no bulk, no attachments. Needs an agent's token (a customer's token is refused). For an internal remark use zammad_add_internal_note. GET /api/v1/tickets/{id}, then POST /api/v1/ticket_articles with type=email, internal=false.

    Annotations the server declares

    • title: Reply to ticket (e-mails the customer)
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • zammad_update_ticketWRITE: change fields of ONE ticket: state, priority, owner (agent), group and/or title.Reads text others writeNo findings

    Why it is in this group

    • The name "zammad_update_ticket" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    WRITE: change fields of ONE ticket: state, priority, owner (agent), group and/or title. Use names from zammad_list_ticket_states / zammad_list_ticket_priorities / zammad_list_groups. Pending states need `pending_time`. Never deletes, removes or merges (those states are refused). The instance's own triggers still run, so closing or reassigning a ticket can send the customer or agent a notification e-mail. PUT /api/v1/tickets/{id}.

    Annotations the server declares

    • title: Update ticket
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
Only reads 15Show 15 read-only tools
  • zammad_get_meThe Zammad user this access token belongs to: id, name, e-mail, roles and groups.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "zammad_get_me" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "mail": it reads mail.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "mail": it reads inbound email, which other people can write.
    Description, as the server wrote it
    The Zammad user this access token belongs to: id, name, e-mail, roles and groups. Use it to confirm the connection and the token's permissions. GET /api/v1/users/me.

    Annotations the server declares

    • title: Get current user
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • zammad_get_organizationOne organization by id: name, domain, notes, VIP flag, member ids.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "zammad_get_organization" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "note": it reads notes.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    One organization by id: name, domain, notes, VIP flag, member ids. GET /api/v1/organizations/{id}.

    Annotations the server declares

    • title: Get organization
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • zammad_get_ticketOne ticket by its numeric id (not the ticket number): title, group, state, priority, owner, customer, organization, dates, escalation and article count.Reads text others writeNo findings

    Why it is in this group

    • The name "zammad_get_ticket" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe name "zammad_get_ticket" says "get" and "ticket": it reads issues, which other people can write.
    • untrusted-inputThe description's first sentence says "ticket": it reads issues, which other people can write.
    Description, as the server wrote it
    One ticket by its numeric id (not the ticket number): title, group, state, priority, owner, customer, organization, dates, escalation and article count. GET /api/v1/tickets/{id}?expand=true.

    Annotations the server declares

    • title: Get ticket
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • zammad_get_ticket_articleOne article by its id with its full body, headers and attachment names.Reads text others writeNo findings

    Why it is in this group

    • The name "zammad_get_ticket_article" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe name "zammad_get_ticket_article" says "get" and "ticket": it reads issues, which other people can write.
    Description, as the server wrote it
    One article by its id with its full body, headers and attachment names. GET /api/v1/ticket_articles/{id}.

    Annotations the server declares

    • title: Get ticket article
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • zammad_get_userOne user (customer or agent) by id: name, e-mail, phone, organization, roles, VIP flag and notes.Reads private dataReads text others write1 finding

    Why it is in this group

    • The name "zammad_get_user" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "mail": it reads mail.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "mail": it reads inbound email, which other people can write.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...nization, roles, VIP flag and notes. No credentials. GET /api/v1/users/{id}?expand=true."

      What this check looks for
    Description, as the server wrote it
    One user (customer or agent) by id: name, e-mail, phone, organization, roles, VIP flag and notes. No credentials. GET /api/v1/users/{id}?expand=true.

    Annotations the server declares

    • title: Get user
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • zammad_list_groupsThe ticket groups (queues) of the instance, with ids, names and agent ids.Reads text others writeNo findings

    Why it is in this group

    • The name "zammad_list_groups" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "ticket": it reads issues, which other people can write.
    Description, as the server wrote it
    The ticket groups (queues) of the instance, with ids, names and agent ids. Zammad requires the admin.group permission for this list; with an agent-only token it returns an authorization error. GET /api/v1/groups.

    Annotations the server declares

    • title: List groups
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • zammad_list_organizationsList customer organizations with domain, VIP flag and member ids.Reads text others writeNo findings

    Why it is in this group

    • The name "zammad_list_organizations" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    List customer organizations with domain, VIP flag and member ids. Needs an agent token. GET /api/v1/organizations.

    Annotations the server declares

    • title: List organizations
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • zammad_list_ticket_articlesAll articles (messages, internal notes, e-mails, phone notes) of one ticket in order, with sender, type, internal flag, from/to/cc, subject, body and attachment names (attachments …Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "zammad_list_ticket_articles" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "message": it reads messages.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe name "zammad_list_ticket_articles" says "list" and "ticket": it reads issues, which other people can write.
    • untrusted-inputThe description's first sentence says "message": it reads messages, which other people can write.
    Description, as the server wrote it
    All articles (messages, internal notes, e-mails, phone notes) of one ticket in order, with sender, type, internal flag, from/to/cc, subject, body and attachment names (attachments are not downloaded). Long bodies are cut at 6000 characters; use zammad_get_ticket_article for the full text. GET /api/v1/ticket_articles/by_ticket/{ticket_id}.

    Annotations the server declares

    • title: List ticket articles
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • zammad_list_ticket_prioritiesThe ticket priorities of the instance (e.g.Reads text others writeNo findings

    Why it is in this group

    • The name "zammad_list_ticket_priorities" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe name "zammad_list_ticket_priorities" says "list" and "ticket": it reads issues, which other people can write.
    • untrusted-inputThe description's first sentence says "ticket": it reads issues, which other people can write.
    Description, as the server wrote it
    The ticket priorities of the instance (e.g. '1 low', '2 normal', '3 high') with ids. Use the names in zammad_update_ticket. GET /api/v1/ticket_priorities.

    Annotations the server declares

    • title: List ticket priorities
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • zammad_list_ticket_statesThe ticket states of the instance (new, open, pending reminder, pending close, closed, ...) with ids and whether they are active.Reads text others writeNo findings

    Why it is in this group

    • The name "zammad_list_ticket_states" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe name "zammad_list_ticket_states" says "list" and "ticket": it reads issues, which other people can write.
    • untrusted-inputThe description's first sentence says "ticket": it reads issues, which other people can write.
    Description, as the server wrote it
    The ticket states of the instance (new, open, pending reminder, pending close, closed, ...) with ids and whether they are active. Use the names in zammad_update_ticket. GET /api/v1/ticket_states.

    Annotations the server declares

    • title: List ticket states
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • zammad_list_ticket_tagsThe tags on one ticket.Reads text others writeNo findings

    Why it is in this group

    • The name "zammad_list_ticket_tags" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe name "zammad_list_ticket_tags" says "list" and "ticket": it reads issues, which other people can write.
    • untrusted-inputThe description's first sentence says "ticket": it reads issues, which other people can write.
    Description, as the server wrote it
    The tags on one ticket. GET /api/v1/tags?object=Ticket&o_id={ticket_id}. Needs an agent token.

    Annotations the server declares

    • title: List ticket tags
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • zammad_list_ticketsList the tickets the token's user can see (an agent sees the tickets of their groups; a customer only their own).Reads text others writeNo findings

    Why it is in this group

    • The name "zammad_list_tickets" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe name "zammad_list_tickets" says "list" and "ticket": it reads issues, which other people can write.
    • untrusted-inputThe description's first sentence says "list" and "ticket": it reads issues, which other people can write.
    Description, as the server wrote it
    List the tickets the token's user can see (an agent sees the tickets of their groups; a customer only their own). For anything targeted use zammad_search_tickets. GET /api/v1/tickets?expand=true.

    Annotations the server declares

    • title: List tickets
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • zammad_search_organizationsSearch customer organizations by name or domain.Reads text others writeNo findings

    Why it is in this group

    • The name "zammad_search_organizations" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Search customer organizations by name or domain. Needs an agent token. GET /api/v1/organizations/search.

    Annotations the server declares

    • title: Search organizations
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • zammad_search_ticketsSearch tickets with Zammad's query syntax.Reads text others writeNo findings

    Why it is in this group

    • The name "zammad_search_tickets" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe name "zammad_search_tickets" says "search" and "ticket": it reads issues, which other people can write.
    • untrusted-inputThe description's first sentence says "search" and "ticket": it reads issues, which other people can write.
    Description, as the server wrote it
    Search tickets with Zammad's query syntax. With Elasticsearch on the instance you can use fields, e.g. `state.name:open AND group.name:Sales`, `customer.email:"a@b.com"`, `title:invoice`, `number:20001`; a plain word searches ticket text. Replies carry ids plus names (group, state, priority, owner, customer). GET /api/v1/tickets/search?expand=true.

    Annotations the server declares

    • title: Search tickets
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • zammad_search_usersSearch customers and agents by name, e-mail, login, phone or organization.Reads private dataReads text others write1 finding

    Why it is in this group

    • The name "zammad_search_users" says "search": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "search" and "mail": it reads mail.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "search" and "mail": it reads inbound email, which other people can write.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...rganization. Returns profile fields (no credentials). Needs an agent token. GET /api/v1/use..."

      What this check looks for
    Description, as the server wrote it
    Search customers and agents by name, e-mail, login, phone or organization. Returns profile fields (no credentials). Needs an agent token. GET /api/v1/users/search?expand=true.

    Annotations the server declares

    • title: Search users
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

95 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data5
Reads files, mail, messages, databases, secrets, calendars or repositories.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__zammad__zammad_reply_to_ticket"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:38 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 4 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://zammad.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://zammad.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

2 info

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 4 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://zammad.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://zammad.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

Pinned to version 1.27.5. Values in angle brackets are yours to fill in.

claude mcp add --transport http zammad https://zammad.usefulapi.io/mcp
claude mcp add --transport http zammad https://zammad.usefulapi.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__zammad__zammad_get_me",
      "mcp__zammad__zammad_search_tickets",
      "mcp__zammad__zammad_list_tickets",
      "mcp__zammad__zammad_get_ticket",
      "mcp__zammad__zammad_list_ticket_articles",
      "mcp__zammad__zammad_get_ticket_article",
      "mcp__zammad__zammad_list_ticket_tags",
      "mcp__zammad__zammad_list_ticket_states",
      "mcp__zammad__zammad_list_ticket_priorities",
      "mcp__zammad__zammad_list_groups",
      "mcp__zammad__zammad_search_users",
      "mcp__zammad__zammad_get_user",
      "mcp__zammad__zammad_search_organizations",
      "mcp__zammad__zammad_list_organizations",
      "mcp__zammad__zammad_get_organization"
    ],
    "ask": [],
    "deny": [
      "mcp__zammad__zammad_add_internal_note",
      "mcp__zammad__zammad_reply_to_ticket",
      "mcp__zammad__zammad_update_ticket",
      "mcp__zammad__zammad_create_ticket"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as zammad. Review it before you use it.

Capability tags behind 19 rules
  • mcp__zammad__zammad_get_me private-data, untrusted-input
  • mcp__zammad__zammad_search_tickets untrusted-input
  • mcp__zammad__zammad_list_tickets untrusted-input
  • mcp__zammad__zammad_get_ticket untrusted-input
  • mcp__zammad__zammad_list_ticket_articles private-data, untrusted-input
  • mcp__zammad__zammad_get_ticket_article untrusted-input
  • mcp__zammad__zammad_list_ticket_tags untrusted-input
  • mcp__zammad__zammad_list_ticket_states untrusted-input
  • mcp__zammad__zammad_list_ticket_priorities untrusted-input
  • mcp__zammad__zammad_list_groups untrusted-input
  • mcp__zammad__zammad_search_users private-data, untrusted-input
  • mcp__zammad__zammad_get_user private-data, untrusted-input
  • mcp__zammad__zammad_search_organizations untrusted-input
  • mcp__zammad__zammad_list_organizations untrusted-input
  • mcp__zammad__zammad_get_organization private-data, untrusted-input
  • mcp__zammad__zammad_add_internal_note untrusted-input
  • mcp__zammad__zammad_reply_to_ticket untrusted-input, outbound
  • mcp__zammad__zammad_update_ticket untrusted-input
  • mcp__zammad__zammad_create_ticket untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/zammad/verify?hash=a5954f2f4c32fe1f986e07f2a376de6bd24aeabcc104efb09e79f018bb070dca" | jq -e '.changed == false'

Pinned hash a5954f2f4c32, from Oct 25, 2026, 23:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.usefulapi/zammad/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.usefulapi/zammad
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/zammad.svg)](https://radar.anlyon.com/servers/io.usefulapi/zammad)

Source: MCP Registry · repository. Synced Nov 20, 2026, 20:18 UTC.

Zammad MCP by usefulapi: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Zammad MCP by usefulapi safe?

No scan can promise that. What its definitions show: 19 tools, 4 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Zammad MCP by usefulapi delete data?

Yes. 4 tools can delete, cancel or revoke something: zammad_add_internal_note, zammad_reply_to_ticket, zammad_update_ticket and zammad_create_ticket.

Can the Zammad MCP by usefulapi do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Zammad MCP by usefulapi have?

19 tools: 4 destructive, 15 read. zammad_add_internal_note, zammad_reply_to_ticket, zammad_update_ticket, zammad_create_ticket, zammad_get_me, zammad_search_tickets, zammad_list_tickets, zammad_get_ticket and 11 more.

Does the Zammad MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Zammad MCP by usefulapi send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): zammad_reply_to_ticket.

Has the Zammad MCP by usefulapi changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.