# SupportBee MCP by usefulapi (remote · supportbee.usefulapi.io)

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

- Trust score: 65/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `supportbee.usefulapi.io`: 65/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-supportbee/supportbee.md), [page](https://verifymcp.io/servers/io-usefulapi-supportbee/supportbee)

## Channel facts

- Endpoint: `https://supportbee.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-17.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 84/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2503 tokens (~113/item across 22 items; 22 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 23 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the SupportBee MCP by usefulapi server?

SupportBee MCP by usefulapi is a hosted endpoint at https://supportbee.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http io-usefulapi-supportbee 'https://supportbee.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-supportbee": {
      "url": "https://supportbee.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-supportbee": {
      "type": "http",
      "url": "https://supportbee.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-supportbee]
url = "https://supportbee.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-supportbee": {
      "type": "remote",
      "url": "https://supportbee.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-supportbee --url 'https://supportbee.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-supportbee:
    url: "https://supportbee.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-supportbee": {
      "Transport": "http",
      "Url": "https://supportbee.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-supportbee -t streamable-http -u 'https://supportbee.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-supportbee": {
      "type": "http",
      "url": "https://supportbee.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-16 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-14 (score 64, +2)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] The server now declares the “prompts” capability
- [functional] First check of Schema quality: 100
- [functional] New prompt “getting_started”
- [functional] Server version: 1.0.0 → 1.1.0

### 2026-10-13 (score 62, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-12 (score 61)

First indexed and scored.

## MCP tools (22)

### `supportbee_list_tickets` (~433 tokens)

List tickets

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.

Input parameters:

- `archived` (string): true = only archived tickets, false = no archived tickets (default), any = both.
- `assigned_team` (string): mine = assigned to the user's teams, a team id (from supportbee_list_teams), none = no team.
- `assigned_user` (string): me = assigned to the token's user, an agent id (from supportbee_list_users), any = assigned to someone, none = unassigned.
- `has_replies` (boolean): true = only tickets that have replies, false = only tickets without replies.
- `label` (string): Only tickets with this label name (supportbee_list_labels).
- `max_replies` (integer): Only tickets with this number of replies (not with has_replies=false).
- `page` (integer): Page number, 1-based (default 1). Use next_page from the previous reply.
- `per_page` (integer): Tickets per page, 1-99 (default 15).
- `requester_emails` (array): Only tickets from these requester e-mail addresses (max 10).
- `since` (string): Only tickets with last activity after this time (date, ISO date-time or Unix timestamp).
- `sort_by` (string): Sort order (default last_activity).
- `spam` (boolean): Include tickets marked as spam (default false).
- `total_only` (boolean): Return only the total number of matching tickets.
- `trash` (boolean): Include trashed tickets (default false).
- `until` (string): Only tickets with last activity before this time (date, ISO date-time or Unix timestamp).

### `supportbee_search_tickets` (~133 tokens)

Search tickets

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.

Input parameters:

- `page` (integer): Page number, 1-based (default 1). Use next_page from the previous reply.
- `per_page` (integer): Tickets per page, 1-99 (default 15).
- `query` (string, required): The search keywords or query.
- `spam` (boolean): Include tickets marked as spam (default false).
- `trash` (boolean): Include trashed tickets (default false).

### `supportbee_get_ticket` (~70 tokens)

Get a ticket

One ticket with subject, requester, labels, assignees, state and the first message text. Replies and comments are separate calls. GET /tickets/{id}.

Input parameters:

- `ticket_id` (integer, required): The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets).

### `supportbee_list_replies` (~67 tokens)

List the replies of a ticket

The public replies (the conversation with the customer) of a ticket, oldest first, as text. GET /tickets/{id}/replies.

Input parameters:

- `ticket_id` (integer, required): The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets).

### `supportbee_get_reply` (~82 tokens)

Get one reply of a ticket

One reply of a ticket (text, replier, cc/bcc). GET /tickets/{ticket_id}/replies/{id}.

Input parameters:

- `reply_id` (integer, required): The reply id (from supportbee_list_replies).
- `ticket_id` (integer, required): The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets).

### `supportbee_list_comments` (~69 tokens)

List the internal comments of a ticket

The internal comments (visible to agents only, never e-mailed) of a ticket, oldest first, as text. GET /tickets/{id}/comments.

Input parameters:

- `ticket_id` (integer, required): The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets).

### `supportbee_get_ticket_audit` (~71 tokens)

Get the audit trail of a ticket

What happened to a ticket and who did it (assignments, label changes, replies, archiving) with timestamps. GET /tickets/{id}/audit.

Input parameters:

- `ticket_id` (integer, required): The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets).

### `supportbee_list_labels` (~39 tokens)

List labels

All custom labels of the company (name and color). Use a label name with supportbee_add_label or the label filter. GET /labels.

### `supportbee_list_teams` (~89 tokens)

List teams

The teams of the company (id, name), optionally only those that have users in them, or only the token user's teams. GET /teams.

Input parameters:

- `mine_only` (boolean): Only the teams of the user who owns the token.
- `with_users` (boolean): Only teams that have users in them (SupportBee's with_users filter; it does not add the member list).

### `supportbee_list_users` (~103 tokens)

List users

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.

Input parameters:

- `type` (string): user (default) or customer_group.
- `with_invited` (boolean): Include users who were invited but have not joined yet (default false).
- `with_roles` (array): Roles to include (default admin, agent, collaborator).

### `supportbee_get_user` (~73 tokens)

Get a user

One user or customer with role, teams, ticket counts and a few of their recent tickets. GET /users/{id}.

Input parameters:

- `max_tickets` (integer): How many of the user's tickets to include (default 5).
- `user_id` (integer, required): The user id (from supportbee_list_users).

### `supportbee_list_snippets` (~39 tokens)

List snippets

The canned replies (snippets) of the company: name, tags and text, to reuse in a reply. GET /snippets.

### `supportbee_list_forwarding_addresses` (~44 tokens)

List forwarding addresses

The support e-mail addresses (forwarding addresses) of the desk: id, name, the address tickets arrive at and the from address. GET /emails.

### `supportbee_get_report` (~120 tokens)

Get a report

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

Input parameters:

- `label` (string): Only this label (name).
- `report` (string, required): Which report.
- `since` (string): Start of the period (date, ISO date-time or Unix timestamp).
- `team` (integer): Only this team (team id).
- `user` (integer): Only this agent (user id).

### `supportbee_reply_to_ticket` (~185 tokens)

Reply to a ticket (sends an e-mail)

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.

Input parameters:

- `bcc` (array): Extra recipients in bcc (cc + bcc together at most 10).
- `cc` (array): Extra recipients in cc (cc + bcc together at most 10).
- `text` (string, required): The reply text (plain text; blank lines separate paragraphs).
- `ticket_id` (integer, required): The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets).

### `supportbee_add_comment` (~90 tokens)

Add an internal comment to a ticket

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.

Input parameters:

- `text` (string, required): The comment text (plain text; blank lines separate paragraphs).
- `ticket_id` (integer, required): The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets).

### `supportbee_add_label` (~95 tokens)

Add a label to a ticket

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

Input parameters:

- `label` (string, required): The label name, exactly as in supportbee_list_labels.
- `ticket_id` (integer, required): The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets).

### `supportbee_remove_label` (~81 tokens)

Remove a label from a ticket

WRITE: removes a label from a ticket (the label itself stays; 404 if the ticket does not have it). DELETE /tickets/{id}/labels/{label}.

Input parameters:

- `label` (string, required): The label name.
- `ticket_id` (integer, required): The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets).

### `supportbee_assign_ticket` (~148 tokens)

Assign a ticket to a user or a team

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.

Input parameters:

- `team_id` (integer): The team id (supportbee_list_teams).
- `ticket_id` (integer, required): The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets).
- `user_id` (integer): The agent id (supportbee_list_users).

### `supportbee_unassign_ticket` (~79 tokens)

Remove the user or team assignment of a ticket

WRITE: clears the user assignee or the team assignee of a ticket. DELETE /tickets/{id}/user_assignment or /team_assignment.

Input parameters:

- `assignee` (string, required): Which assignment to clear.
- `ticket_id` (integer, required): The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets).

### `supportbee_set_ticket_archived` (~98 tokens)

Archive or un-archive a ticket

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.

Input parameters:

- `archived` (boolean, required): true = archive, false = move back to the inbox.
- `ticket_id` (integer, required): The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets).

### `supportbee_set_ticket_answered` (~86 tokens)

Mark a ticket answered or unanswered

WRITE: marks a ticket as answered (answered=true) or unanswered (answered=false) without sending anything. POST/DELETE /tickets/{id}/answered.

Input parameters:

- `answered` (boolean, required): true = mark answered, false = mark unanswered.
- `ticket_id` (integer, required): The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-supportbee/supportbee#diagnostics

## Score history

- 2026-10-17: 65
- 2026-10-16: 65
- 2026-10-15: 64
- 2026-10-14: 64
- 2026-10-13: 62
- 2026-10-12: 61

## Common questions

### What is the SupportBee MCP by usefulapi server?

SupportBee MCP by usefulapi is listed in the public MCP registry as io.usefulapi/supportbee. Read SupportBee tickets, replies and reports; reply, comment, label, assign and archive tickets. This page covers its hosted endpoint (https://supportbee.usefulapi.io/mcp).

### Is the SupportBee MCP by usefulapi server safe to use?

SupportBee MCP by usefulapi scores 65 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the SupportBee MCP by usefulapi server expose?

SupportBee MCP by usefulapi exposes 22 tools: supportbee_list_tickets, supportbee_search_tickets, supportbee_get_ticket, supportbee_list_replies, supportbee_get_reply, and 17 more. Their descriptions and schemas cost roughly 2,294 tokens of context every time the server is loaded.

### Does the SupportBee MCP by usefulapi server require authentication?

Yes. SupportBee MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the SupportBee MCP by usefulapi server still maintained?

SupportBee MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://supportbee.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/supportbee/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-supportbee/supportbee.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-supportbee/supportbee.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-supportbee/supportbee