Skip to content

SupportBee MCP by usefulapi

io.usefulapi/supportbeeusefulapi.iostreamable-httpv1.27.4Scanned

Read SupportBee tickets, replies and reports; reply, comment, label, assign and archive tickets.

22 tools: 3 can delete or cancel things, 5 change things and 14 only read.

Tools: 3 delete, 0 irreversible, 5 write, 14 read.
  • Reads private data · 5
  • Reads text others write · 12
  • Can send data out · 2
  • 1 finding

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

Anlyon alternative

8 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 SupportBee MCP by usefulapi can do

The SupportBee MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 22 tools. It can delete or cancel things (3 tools: supportbee_reply_to_ticket, supportbee_add_comment and supportbee_remove_label) and create or change data (5 tools: supportbee_add_label, supportbee_assign_ticket, supportbee_unassign_ticket, supportbee_set_ticket_archived and 1 more). 14 tools only read.

5 tools read private data (supportbee_list_tickets, supportbee_get_ticket, supportbee_list_replies and 2 more); 12 tools bring in text other people can write (supportbee_list_tickets, supportbee_search_tickets, supportbee_get_ticket and 9 more); 2 tools can send data out of your system (supportbee_reply_to_ticket and supportbee_add_comment). 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 1 finding (annotation-conflict). Each one comes with the text it matched.

Last scanned Oct 25, 2026, version 1.27.4.

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.

22 tools

Deletes or cancels 3Claude Code: deny
  • supportbee_add_commentWRITE: adds an internal comment to a ticket.Can send data outNo findings

    Why it is in this group

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

    What it can reach

    • outboundThe name "supportbee_add_comment" says "add" and "comment": it writes something other people read.
    Description, as the server wrote it
    WRITE: adds an internal comment to a ticket. Comments are visible to your agents only and are never e-mailed to the customer. POST /tickets/{id}/comments.

    Annotations the server declares

    • title: Add an internal comment to a ticket
    • destructiveHint: true
  • supportbee_remove_labelWRITE: removes a label from a ticket (the label itself stays; 404 if the ticket does not have it).1 finding

    Why it is in this group

    • The name "supportbee_remove_label" says "remove": a word for removing or ending something.
    • The server marks it not destructive (destructiveHint: false), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "supportbee_remove_label" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".

      Matched text

      annotations: {"destructiveHint":false,"idempotentHint":true}; The name "supportbee_remove_label" says "remove": a word for removing or ending something.

      What this check looks for
    Description, as the server wrote it
    WRITE: removes a label from a ticket (the label itself stays; 404 if the ticket does not have it). DELETE /tickets/{id}/labels/{label}.

    Annotations the server declares

    • title: Remove a label from a ticket
    • idempotentHint: true
    • destructiveHint: false
  • supportbee_reply_to_ticketWRITE: SENDS AN E-MAIL to the customer.Can send data outNo findings

    Why it is in this group

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

    What it can reach

    • outboundThe name "supportbee_reply_to_ticket" says "reply": it sends or publishes something to other people.
    Description, as the server wrote it
    WRITE: SENDS AN E-MAIL to the customer. Posts a public reply on ONE ticket; SupportBee e-mails it to the ticket's requester and to the cc/bcc addresses you list (at most 10 addresses in total). It cannot be recalled. The reply comes from the token's user. For a note only your team sees, use supportbee_add_comment. POST /tickets/{id}/replies.

    Annotations the server declares

    • title: Reply to a ticket (sends an e-mail)
    • destructiveHint: true
Changes things 5Claude Code: ask
  • supportbee_add_labelWRITE: adds an existing label to a ticket (404 if the label does not exist; names come from supportbee_list_labels).No findings

    Why it is in this group

    • The name "supportbee_add_label" says "add": a word for a change.
    Description, as the server wrote it
    WRITE: adds an existing label to a ticket (404 if the label does not exist; names come from supportbee_list_labels). Safe to repeat. POST /tickets/{id}/labels/{label}.

    Annotations the server declares

    • title: Add a label to a ticket
    • idempotentHint: true
    • destructiveHint: false
  • supportbee_assign_ticketWRITE: assigns a ticket to ONE agent (user_id) or ONE team (team_id), not both.No findings

    Why it is in this group

    • The name "supportbee_assign_ticket" says "assign": a word for a change.
    Description, as the server wrote it
    WRITE: assigns a ticket to ONE agent (user_id) or ONE team (team_id), not both. A ticket that belongs to a team can only go to a member of that team; assigning to another team removes the user assignee. The customer is not e-mailed (SupportBee may notify the assigned agent). POST /tickets/{id}/user_assignment or /team_assignment.

    Annotations the server declares

    • title: Assign a ticket to a user or a team
    • idempotentHint: true
    • destructiveHint: false
  • supportbee_set_ticket_answeredWRITE: marks a ticket as answered (answered=true) or unanswered (answered=false) without sending anything.No findings

    Why it is in this group

    • The name "supportbee_set_ticket_answered" says "set": a word for a change.
    Description, as the server wrote it
    WRITE: marks a ticket as answered (answered=true) or unanswered (answered=false) without sending anything. POST/DELETE /tickets/{id}/answered.

    Annotations the server declares

    • title: Mark a ticket answered or unanswered
    • idempotentHint: true
    • destructiveHint: false
  • supportbee_set_ticket_archivedWRITE: archives a ticket (archived=true, it leaves the open inbox) or moves it back (archived=false).No findings

    Why it is in this group

    • The name "supportbee_set_ticket_archived" says "set": a word for a change.
    Description, as the server wrote it
    WRITE: archives a ticket (archived=true, it leaves the open inbox) or moves it back (archived=false). Nothing is deleted or sent. POST/DELETE /tickets/{id}/archive.

    Annotations the server declares

    • title: Archive or un-archive a ticket
    • idempotentHint: true
    • destructiveHint: false
  • supportbee_unassign_ticketWRITE: clears the user assignee or the team assignee of a ticket.No findings

    Why it is in this group

    • The name "supportbee_unassign_ticket" says "unassign": a word for a change.
    Description, as the server wrote it
    WRITE: clears the user assignee or the team assignee of a ticket. DELETE /tickets/{id}/user_assignment or /team_assignment.

    Annotations the server declares

    • title: Remove the user or team assignment of a ticket
    • idempotentHint: true
    • destructiveHint: false
Only reads 14Show 14 read-only tools
  • supportbee_get_replyOne reply of a ticket (text, replier, cc/bcc).Reads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe name "supportbee_get_reply" says "get" and "reply": it reads comments, which other people can write.
    • untrusted-inputThe description's first sentence says "reply": it reads comments, which other people can write.
    Description, as the server wrote it
    One reply of a ticket (text, replier, cc/bcc). GET /tickets/{ticket_id}/replies/{id}.

    Annotations the server declares

    • title: Get one reply of a ticket
    • readOnlyHint: true
  • supportbee_get_reportA report as time-series data points (value, timestamp): tickets_count, replies_count or avg_first_response_time, optionally for one agent, team or label.Reads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe description's first sentence says "ticket": it reads issues, which other people can write.
    Description, as the server wrote it
    A report as time-series data points (value, timestamp): tickets_count, replies_count or avg_first_response_time, optionally for one agent, team or label. Needs an admin token. GET /reports/{report}.

    Annotations the server declares

    • title: Get a report
    • readOnlyHint: true
  • supportbee_get_ticketOne ticket with subject, requester, labels, assignees, state and the first message text.Reads private dataReads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe description's first sentence says "message": it reads messages.
    • untrusted-inputThe name "supportbee_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 with subject, requester, labels, assignees, state and the first message text. Replies and comments are separate calls. GET /tickets/{id}.

    Annotations the server declares

    • title: Get a ticket
    • readOnlyHint: true
  • supportbee_get_ticket_auditWhat happened to a ticket and who did it (assignments, label changes, replies, archiving) with timestamps.Reads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe name "supportbee_get_ticket_audit" 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
    What happened to a ticket and who did it (assignments, label changes, replies, archiving) with timestamps. GET /tickets/{id}/audit.

    Annotations the server declares

    • title: Get the audit trail of a ticket
    • readOnlyHint: true
  • supportbee_get_userOne user or customer with role, teams, ticket counts and a few of their recent tickets.Reads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe description's first sentence says "ticket": it reads issues, which other people can write.
    Description, as the server wrote it
    One user or customer with role, teams, ticket counts and a few of their recent tickets. GET /users/{id}.

    Annotations the server declares

    • title: Get a user
    • readOnlyHint: true
  • supportbee_list_commentsThe internal comments (visible to agents only, never e-mailed) of a ticket, oldest first, as text.Reads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe name "supportbee_list_comments" says "list" and "comment": it reads comments, which other people can write.
    • untrusted-inputThe description's first sentence says "comment": it reads comments, which other people can write.
    Description, as the server wrote it
    The internal comments (visible to agents only, never e-mailed) of a ticket, oldest first, as text. GET /tickets/{id}/comments.

    Annotations the server declares

    • title: List the internal comments of a ticket
    • readOnlyHint: true
  • supportbee_list_forwarding_addressesThe support e-mail addresses (forwarding addresses) of the desk: id, name, the address tickets arrive at and the from address.Reads private dataReads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe description's first sentence says "mail": it reads mail.
    • untrusted-inputThe description's first sentence says "mail": it reads inbound email, which other people can write.
    Description, as the server wrote it
    The support e-mail addresses (forwarding addresses) of the desk: id, name, the address tickets arrive at and the from address. GET /emails.

    Annotations the server declares

    • title: List forwarding addresses
    • readOnlyHint: true
  • supportbee_list_labelsAll custom labels of the company (name and color).No findings

    Why it is in this group

    • The name "supportbee_list_labels" says "list": a word for reading.
    Description, as the server wrote it
    All custom labels of the company (name and color). Use a label name with supportbee_add_label or the label filter. GET /labels.

    Annotations the server declares

    • title: List labels
    • readOnlyHint: true
  • supportbee_list_repliesThe public replies (the conversation with the customer) of a ticket, oldest first, as text.Reads private dataReads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe description's first sentence says "conversation": it reads messages.
    • untrusted-inputThe name "supportbee_list_replies" says "list" and "reply": it reads comments, which other people can write.
    • untrusted-inputThe description's first sentence says "reply": it reads comments, which other people can write.
    Description, as the server wrote it
    The public replies (the conversation with the customer) of a ticket, oldest first, as text. GET /tickets/{id}/replies.

    Annotations the server declares

    • title: List the replies of a ticket
    • readOnlyHint: true
  • supportbee_list_snippetsThe canned replies (snippets) of the company: name, tags and text, to reuse in a reply.Reads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe description's first sentence says "reply": it reads comments, which other people can write.
    Description, as the server wrote it
    The canned replies (snippets) of the company: name, tags and text, to reuse in a reply. GET /snippets.

    Annotations the server declares

    • title: List snippets
    • readOnlyHint: true
  • supportbee_list_teamsThe teams of the company (id, name), optionally only those that have users in them, or only the token user's teams.No findings

    Why it is in this group

    • The name "supportbee_list_teams" says "list": a word for reading.
    Description, as the server wrote it
    The teams of the company (id, name), optionally only those that have users in them, or only the token user's teams. GET /teams.

    Annotations the server declares

    • title: List teams
    • readOnlyHint: true
  • supportbee_list_ticketsList tickets of the shared inbox, newest activity first, with filters (assignee, team, label, requester, dates, spam/trash/archived).Reads private dataReads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe description's first sentence says "list" and "inbox": it reads mail.
    • untrusted-inputThe name "supportbee_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 tickets of the shared inbox, newest activity first, with filters (assignee, team, label, requester, dates, spam/trash/archived). By default archived, spam and trashed tickets are left out. Each ticket has id, subject, labels, requester, assignee, replies_count, comments_count, unanswered, archived and the first message text (cut). With total_only=true only the number of matching tickets comes back. GET /tickets.

    Annotations the server declares

    • title: List tickets
    • readOnlyHint: true
  • supportbee_list_usersThe agents, admins and collaborators of the desk (id, name, e-mail, role, teams), or customer groups.Reads private dataReads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe description's first sentence says "mail": it reads mail.
    • untrusted-inputThe description's first sentence says "mail": it reads inbound email, which other people can write.
    Description, as the server wrote it
    The agents, admins and collaborators of the desk (id, name, e-mail, role, teams), or customer groups. Use the id as assigned_user or user_id. GET /users.

    Annotations the server declares

    • title: List users
    • readOnlyHint: true
  • supportbee_search_ticketsFull-text search over tickets (subject, body, requester) with SupportBee's search syntax, newest activity first.Reads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe name "supportbee_search_tickets" says "search" 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
    Full-text search over tickets (subject, body, requester) with SupportBee's search syntax, newest activity first. Spam and trash are excluded unless asked. GET /tickets/search.

    Annotations the server declares

    • title: Search tickets
    • readOnlyHint: 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.

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

Reads private data5
Reads files, mail, messages, databases, secrets, calendars or repositories.
Can send data out2
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__supportbee__supportbee_add_comment",
      "mcp__supportbee__supportbee_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:37 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: 8 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://supportbee.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://supportbee.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.

1 warn
  • The server marks "supportbee_remove_label" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".

    Matched text

    annotations: {"destructiveHint":false,"idempotentHint":true}; The name "supportbee_remove_label" says "remove": a word for removing or ending something.

    What this check looks for

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: 8 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://supportbee.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://supportbee.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.4. Values in angle brackets are yours to fill in.

claude mcp add --transport http supportbee https://supportbee.usefulapi.io/mcp
claude mcp add --transport http supportbee https://supportbee.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__supportbee__supportbee_list_tickets",
      "mcp__supportbee__supportbee_search_tickets",
      "mcp__supportbee__supportbee_get_ticket",
      "mcp__supportbee__supportbee_list_replies",
      "mcp__supportbee__supportbee_get_reply",
      "mcp__supportbee__supportbee_list_comments",
      "mcp__supportbee__supportbee_get_ticket_audit",
      "mcp__supportbee__supportbee_list_labels",
      "mcp__supportbee__supportbee_list_teams",
      "mcp__supportbee__supportbee_list_users",
      "mcp__supportbee__supportbee_get_user",
      "mcp__supportbee__supportbee_list_snippets",
      "mcp__supportbee__supportbee_list_forwarding_addresses",
      "mcp__supportbee__supportbee_get_report"
    ],
    "ask": [
      "mcp__supportbee__supportbee_add_label",
      "mcp__supportbee__supportbee_assign_ticket",
      "mcp__supportbee__supportbee_unassign_ticket",
      "mcp__supportbee__supportbee_set_ticket_archived",
      "mcp__supportbee__supportbee_set_ticket_answered"
    ],
    "deny": [
      "mcp__supportbee__supportbee_reply_to_ticket",
      "mcp__supportbee__supportbee_add_comment",
      "mcp__supportbee__supportbee_remove_label"
    ]
  }
}

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 supportbee. Review it before you use it.

Capability tags behind 14 rules
  • mcp__supportbee__supportbee_list_tickets private-data, untrusted-input
  • mcp__supportbee__supportbee_search_tickets untrusted-input
  • mcp__supportbee__supportbee_get_ticket private-data, untrusted-input
  • mcp__supportbee__supportbee_list_replies private-data, untrusted-input
  • mcp__supportbee__supportbee_get_reply untrusted-input
  • mcp__supportbee__supportbee_list_comments untrusted-input
  • mcp__supportbee__supportbee_get_ticket_audit untrusted-input
  • mcp__supportbee__supportbee_list_users private-data, untrusted-input
  • mcp__supportbee__supportbee_get_user untrusted-input
  • mcp__supportbee__supportbee_list_snippets untrusted-input
  • mcp__supportbee__supportbee_list_forwarding_addresses private-data, untrusted-input
  • mcp__supportbee__supportbee_get_report untrusted-input
  • mcp__supportbee__supportbee_reply_to_ticket outbound
  • mcp__supportbee__supportbee_add_comment outbound

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/supportbee/verify?hash=79d4ffc7b8eefe85d10d989500d86adaf3056f1c13707634a011cc572e51ee73" | jq -e '.changed == false'

Pinned hash 79d4ffc7b8ee, 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/supportbee/changes.xml

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

Badge

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

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

SupportBee MCP by usefulapi: questions and answers

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

Is the SupportBee MCP by usefulapi safe?

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

Can the SupportBee MCP by usefulapi delete data?

Yes. 3 tools can delete, cancel or revoke something: supportbee_reply_to_ticket, supportbee_add_comment and supportbee_remove_label.

Can the SupportBee 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 SupportBee MCP by usefulapi have?

22 tools: 3 destructive, 5 write, 14 read. supportbee_reply_to_ticket, supportbee_add_comment, supportbee_remove_label, supportbee_add_label, supportbee_assign_ticket, supportbee_unassign_ticket, supportbee_set_ticket_archived, supportbee_set_ticket_answered and 14 more.

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

Its remote endpoint did not answer the last anonymous look.

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

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): supportbee_reply_to_ticket and supportbee_add_comment.

Has the SupportBee MCP by usefulapi changed its tools?

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