Enchant MCP by usefulapi
REMOTE · ENCHANT.USEFULAPI.IO
Work with Enchant help desk tickets: list, read, reply, add notes and labels, manage customers.
Available components
Last scanned (5 hours ago)
Scores higher than 46% 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 Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2067 tokens (~129/item across 16 items; 16 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 Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 94% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 17 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 60
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://enchant.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 enchant.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://enchant.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://enchant.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://enchant.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://enchant.usefulapi.io/mcp |
| Authorisation server | https://enchant.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://enchant.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/enchant/ |
| http (plaintext) | http://enchant.usefulapi.io/mcp | Inconclusive | 302 | http://enchant.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 →
enchant_add_customer_contact Add customer contact ~72
WRITE: add one contact (email, twitter or phone) to a customer. Enchant REST: POST /customers/{id}/contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Customer id. |
| type | string | yes | Contact type. |
| value | string | yes | Email address, Twitter screen name or phone number. |
No output schema declared.
No examples provided.
enchant_add_note Add internal note ~114
WRITE: add an internal note to a ticket (not sent to the customer). Enchant REST: POST /tickets/{id}/messages (type note).
| Name | Type | Req | Description |
|---|---|---|---|
| attachment_ids | array | – | Ids of attachments already uploaded. |
| body | string | yes | Note body. |
| html | boolean | – | True if body is HTML (default false: plain text). |
| id | string | yes | Ticket id. |
| user_id | string | yes | Id of the user (agent) the note is from; see enchant_list_users. |
No output schema declared.
No examples provided.
enchant_add_ticket_labels Add labels to ticket ~62
WRITE: add one or more labels to a ticket without changing its other labels. Enchant REST: PUT /tickets/{id}/labels/{label_ids}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Ticket id. |
| label_ids | array | yes | Label ids to add. |
No output schema declared.
No examples provided.
enchant_create_customer Create customer ~75
WRITE: create a customer with optional contacts (email, twitter, phone). Enchant REST: POST /customers.
| Name | Type | Req | Description |
|---|---|---|---|
| contacts | array | – | Contacts of the customer. |
| first_name | string | – | – |
| last_name | string | – | – |
| summary | string | – | Short free-text summary shown on the customer profile. |
No output schema declared.
No examples provided.
enchant_create_ticket Create ticket ~145
WRITE: create an email ticket. Give customer_id, or a customer (matched by contact email, created if new). Optionally add the customer's first message with body (needs the customer's email). Enchant REST: POST /tickets.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | First inbound message from the customer (plain text). |
| customer | object | – | Customer to find or create, instead of customer_id. |
| customer_id | string | – | Existing customer id. Give this or customer. |
| inbox_id | string | – | Inbox id (the default inbox if omitted). |
| subject | string | yes | Ticket subject. |
| user_id | string | – | User id to assign the ticket to. |
No output schema declared.
No examples provided.
enchant_delete_customer_contact Delete customer contact ~63
WRITE, DELETES DATA: remove one contact from a customer. Enchant REST: DELETE /customers/{id}/contacts/{contact_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | string | yes | Contact id (from the customer's contacts). |
| id | string | yes | Customer id. |
No output schema declared.
No examples provided.
enchant_get_attachment Get attachment ~52
Get the metadata of an attachment (name, size, MIME type) by id; attachment ids appear in ticket messages. Enchant REST: GET /attachments/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Attachment id. |
No output schema declared.
No examples provided.
enchant_get_customer Get customer ~45
Get one customer by id, with the contacts (emails, phones, Twitter names). Enchant REST: GET /customers/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Customer id. |
No output schema declared.
No examples provided.
enchant_get_ticket Get ticket ~90
Get one ticket by id. Embed related data with `embed`: messages (the conversation: replies and notes), customer, user, inbox, labels. Each embedded type costs 1 extra rate-limit credit. Enchant REST: GET /tickets/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| embed | array | – | Related resources to embed. |
| id | string | yes | Ticket id (the string id, not the friendly ticket number). |
No output schema declared.
No examples provided.
enchant_list_customers List customers ~182
List customers, or find one by contact: set contact_type and contact_value (for example email + an address). Enchant REST: GET /customers.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_type | string | – | Contact type to match (use with contact_value). |
| contact_value | string | – | Email address or Twitter screen name to match (use with contact_type). |
| count | boolean | – | If true, also return the total number of matching results (costs 1 extra rate-limit credit). |
| page | integer | – | Page number (1-based). Past 10,000 results, filter by since_created_at instead. |
| per_page | integer | – | Results per page (0-100, default 10). Use 0 with count to get only the total. |
| since_created_at | string | – | Only customers created since this UTC ISO 8601 time. |
No output schema declared.
No examples provided.
enchant_list_tickets List tickets ~352
List and filter tickets (newest first by default). Enchant REST: GET /tickets. Use user_ids ["null"] for unassigned tickets. Each result has a short summary; use enchant_get_ticket for messages.
| Name | Type | Req | Description |
|---|---|---|---|
| count | boolean | – | If true, also return the total number of matching results (costs 1 extra rate-limit credit). |
| ids | array | – | Only these ticket ids. |
| inbox_ids | array | – | Only tickets in these inbox ids. |
| label_ids | array | – | Only tickets with these label ids. |
| page | integer | – | Page number (1-based). Past 10,000 results, filter by since_created_at instead. |
| per_page | integer | – | Results per page (0-100, default 10). Use 0 with count to get only the total. |
| since_created_at | string | – | Only tickets created since this UTC ISO 8601 time, e.g. 2026-01-31T13:41:10Z. |
| since_updated_at | string | – | Only tickets updated since this UTC ISO 8601 time. |
| sort | string | – | Sort order; a leading - means descending. |
| spam | boolean | – | Only spam (true) or only non-spam (false) tickets. |
| states | array | – | Only tickets in these states. |
| trash | boolean | – | Only trashed (true) or only non-trashed (false) tickets. |
| types | array | – | Ticket types, e.g. email, chat, sms, phone, web, twitter, whatsapp. |
| user_ids | array | – | Only tickets assigned to these user ids ("null" = unassigned). |
No output schema declared.
No examples provided.
enchant_list_users List users (agents) ~100
List the help desk users (agents): id, name, email. Use the ids to assign tickets and to author replies and notes. Enchant REST: GET /users.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (1-based). Past 10,000 results, filter by since_created_at instead. |
| per_page | integer | – | Results per page (0-100, default 10). Use 0 with count to get only the total. |
No output schema declared.
No examples provided.
enchant_remove_ticket_labels Remove labels from ticket ~62
WRITE: remove one or more labels from a ticket; its other labels stay. Enchant REST: DELETE /tickets/{id}/labels/{label_ids}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Ticket id. |
| label_ids | array | yes | Label ids to remove. |
No output schema declared.
No examples provided.
enchant_reply_to_ticket Reply to customer ~150
WRITE: send an outbound reply on a ticket. This SENDS A REAL EMAIL to the customer address in `to`. Use enchant_add_note for an internal note. Enchant REST: POST /tickets/{id}/messages (type reply, direction out).
| Name | Type | Req | Description |
|---|---|---|---|
| attachment_ids | array | – | Ids of attachments already uploaded. |
| body | string | yes | Reply body. |
| html | boolean | – | True if body is HTML (default false: plain text). |
| id | string | yes | Ticket id. |
| to | string | yes | Recipient address, normally the customer's email. |
| user_id | string | yes | Id of the user (agent) the reply is sent as; see enchant_list_users. |
No output schema declared.
No examples provided.
enchant_update_customer Update customer ~111
WRITE: update a customer's name or summary. If `contacts` is given, it REPLACES the contact list; use enchant_add_customer_contact to add one. Enchant REST: PATCH /customers/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| contacts | array | – | The full new contact list (replaces the existing one). |
| first_name | string | – | – |
| id | string | yes | Customer id. |
| last_name | string | – | – |
| summary | string | – | Short free-text summary shown on the customer profile. |
No output schema declared.
No examples provided.
enchant_update_ticket Update ticket ~186
WRITE: change a ticket: state (open, hold, closed), assignee, inbox, subject, spam or trash (not both true). label_ids REPLACES all labels (empty array clears them); use enchant_add_ticket_labels to keep existing ones. Enchant REST: PATCH /tickets/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Ticket id. |
| inbox_id | string | – | Move to this inbox id. |
| label_ids | array | – | The full new set of label ids (replaces existing labels). |
| spam | boolean | – | Mark as spam. Cannot be true together with trash. |
| state | string | – | New state. |
| subject | string | – | New subject. |
| trash | boolean | – | Send to trash. Cannot be true together with spam. |
| user_id | string|null | – | Assign to this user id; null unassigns the ticket. |
No output schema declared.
No examples provided.
How do I install the Enchant MCP by usefulapi server?
Enchant MCP by usefulapi is a hosted endpoint at https://enchant.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 · enchant.usefulapi.io
claude mcp add --transport http io-usefulapi-enchant 'https://enchant.usefulapi.io/mcp'
What is the Enchant MCP by usefulapi server?
Enchant MCP by usefulapi is listed in the public MCP registry as io.usefulapi/enchant. Work with Enchant help desk tickets: list, read, reply, add notes and labels, manage customers. This page covers its hosted endpoint (https://enchant.usefulapi.io/mcp).
Is the Enchant MCP by usefulapi server safe to use?
Enchant MCP by usefulapi scores 64 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 Enchant MCP by usefulapi server expose?
Enchant MCP by usefulapi exposes 16 tools: enchant_list_tickets, enchant_get_ticket, enchant_list_users, enchant_list_customers, enchant_get_customer, and 11 more. Their descriptions and schemas cost roughly 1,861 tokens of context every time the server is loaded.
Does the Enchant MCP by usefulapi server require authentication?
Yes. Enchant 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 Enchant MCP by usefulapi server still maintained?
Enchant 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.