SupportBee MCP by usefulapi
REMOTE · SUPPORTBEE.USEFULAPI.IO
Read SupportBee tickets, replies and reports; reply, comment, label, assign and archive tickets.
Available components
Last scanned (10 hours ago)
Scores higher than 47% of remote servers
Reachable. Last reached 17 Oct 2026.
Category CRM and Sales
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. How we score → Why this is hard to score →
Endpoint Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 23 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Oct 26 +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.
- 14 Oct 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- 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 functional
- 13 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Probed https://supportbee.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of supportbee.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://supportbee.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://supportbee.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://supportbee.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://supportbee.usefulapi.io/mcp |
| Authorisation server | https://supportbee.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://supportbee.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/supportbee/ |
| http (plaintext) | http://supportbee.usefulapi.io/mcp | Inconclusive | 302 | http://supportbee.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
supportbee_add_comment Add an internal comment to a ticket ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | The comment text (plain text; blank lines separate paragraphs). |
| ticket_id | integer | yes | The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets). |
No output schema declared.
No examples provided.
supportbee_add_label Add a label to a ticket ~95
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| label | string | yes | The label name, exactly as in supportbee_list_labels. |
| ticket_id | integer | yes | The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets). |
No output schema declared.
No examples provided.
supportbee_assign_ticket Assign a ticket to a user or a team ~148
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.
| Name | Type | Req | Description |
|---|---|---|---|
| team_id | integer | – | The team id (supportbee_list_teams). |
| ticket_id | integer | yes | The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets). |
| user_id | integer | – | The agent id (supportbee_list_users). |
No output schema declared.
No examples provided.
supportbee_get_reply Get one reply of a ticket ~82
One reply of a ticket (text, replier, cc/bcc). GET /tickets/{ticket_id}/replies/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| reply_id | integer | yes | The reply id (from supportbee_list_replies). |
| ticket_id | integer | yes | The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets). |
No output schema declared.
No examples provided.
supportbee_get_report Get a report ~120
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| label | string | – | Only this label (name). |
| report | string | yes | 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). |
No output schema declared.
No examples provided.
supportbee_get_ticket Get a ticket ~70
One ticket with subject, requester, labels, assignees, state and the first message text. Replies and comments are separate calls. GET /tickets/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| ticket_id | integer | yes | The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets). |
No output schema declared.
No examples provided.
supportbee_get_ticket_audit Get the audit trail of a ticket ~71
What happened to a ticket and who did it (assignments, label changes, replies, archiving) with timestamps. GET /tickets/{id}/audit.
| Name | Type | Req | Description |
|---|---|---|---|
| ticket_id | integer | yes | The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets). |
No output schema declared.
No examples provided.
supportbee_get_user Get a user ~73
One user or customer with role, teams, ticket counts and a few of their recent tickets. GET /users/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| max_tickets | integer | – | How many of the user's tickets to include (default 5). |
| user_id | integer | yes | The user id (from supportbee_list_users). |
No output schema declared.
No examples provided.
supportbee_list_comments List the internal comments of a ticket ~69
The internal comments (visible to agents only, never e-mailed) of a ticket, oldest first, as text. GET /tickets/{id}/comments.
| Name | Type | Req | Description |
|---|---|---|---|
| ticket_id | integer | yes | The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets). |
No output schema declared.
No examples provided.
supportbee_list_forwarding_addresses List forwarding addresses ~44
The support e-mail addresses (forwarding addresses) of the desk: id, name, the address tickets arrive at and the from address. GET /emails.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
supportbee_list_labels List labels ~39
All custom labels of the company (name and color). Use a label name with supportbee_add_label or the label filter. GET /labels.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
supportbee_list_replies List the replies of a ticket ~67
The public replies (the conversation with the customer) of a ticket, oldest first, as text. GET /tickets/{id}/replies.
| Name | Type | Req | Description |
|---|---|---|---|
| ticket_id | integer | yes | The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets). |
No output schema declared.
No examples provided.
supportbee_list_snippets List snippets ~39
The canned replies (snippets) of the company: name, tags and text, to reuse in a reply. GET /snippets.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
supportbee_list_teams List teams ~89
The teams of the company (id, name), optionally only those that have users in them, or only the token user's teams. GET /teams.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
supportbee_list_tickets List tickets ~433
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
supportbee_list_users List users ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
supportbee_remove_label Remove a label from a ticket ~81
WRITE: removes a label from a ticket (the label itself stays; 404 if the ticket does not have it). DELETE /tickets/{id}/labels/{label}.
| Name | Type | Req | Description |
|---|---|---|---|
| label | string | yes | The label name. |
| ticket_id | integer | yes | The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets). |
No output schema declared.
No examples provided.
supportbee_reply_to_ticket Reply to a ticket (sends an e-mail) ~185
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The reply text (plain text; blank lines separate paragraphs). |
| ticket_id | integer | yes | The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets). |
No output schema declared.
No examples provided.
supportbee_search_tickets Search tickets ~133
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The search keywords or query. |
| spam | boolean | – | Include tickets marked as spam (default false). |
| trash | boolean | – | Include trashed tickets (default false). |
No output schema declared.
No examples provided.
supportbee_set_ticket_answered Mark a ticket answered or unanswered ~86
WRITE: marks a ticket as answered (answered=true) or unanswered (answered=false) without sending anything. POST/DELETE /tickets/{id}/answered.
| Name | Type | Req | Description |
|---|---|---|---|
| answered | boolean | yes | true = mark answered, false = mark unanswered. |
| ticket_id | integer | yes | The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets). |
No output schema declared.
No examples provided.
supportbee_set_ticket_archived Archive or un-archive a ticket ~98
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.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | boolean | yes | true = archive, false = move back to the inbox. |
| ticket_id | integer | yes | The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets). |
No output schema declared.
No examples provided.
supportbee_unassign_ticket Remove the user or team assignment of a ticket ~79
WRITE: clears the user assignee or the team assignee of a ticket. DELETE /tickets/{id}/user_assignment or /team_assignment.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee | string | yes | Which assignment to clear. |
| ticket_id | integer | yes | The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets). |
No output schema declared.
No examples provided.
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.
remote · supportbee.usefulapi.io
claude mcp add --transport http io-usefulapi-supportbee 'https://supportbee.usefulapi.io/mcp'
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.