# Enchant MCP by usefulapi (remote · enchant.usefulapi.io)

Work with Enchant help desk tickets: list, read, reply, add notes and labels, manage customers.

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

## Components

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

## Channel facts

- Endpoint: `https://enchant.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**: 81/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - 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.
  - 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**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 94% 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 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 17 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 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.

### Claude

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-enchant": {
      "type": "http",
      "url": "https://enchant.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 64, +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 63, +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 61, +1)

- [functional improvement] Stability: unverified → 0.03

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

First indexed and scored.

## MCP tools (16)

### `enchant_list_tickets` (~352 tokens)

List tickets

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.

Input parameters:

- `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).

### `enchant_get_ticket` (~90 tokens)

Get ticket

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

Input parameters:

- `embed` (array): Related resources to embed.
- `id` (string, required): Ticket id (the string id, not the friendly ticket number).

### `enchant_list_users` (~100 tokens)

List users (agents)

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.

Input parameters:

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

### `enchant_list_customers` (~182 tokens)

List customers

List customers, or find one by contact: set contact_type and contact_value (for example email + an address). Enchant REST: GET /customers.

Input parameters:

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

### `enchant_get_customer` (~45 tokens)

Get customer

Get one customer by id, with the contacts (emails, phones, Twitter names). Enchant REST: GET /customers/{id}.

Input parameters:

- `id` (string, required): Customer id.

### `enchant_get_attachment` (~52 tokens)

Get attachment

Get the metadata of an attachment (name, size, MIME type) by id; attachment ids appear in ticket messages. Enchant REST: GET /attachments/{id}.

Input parameters:

- `id` (string, required): Attachment id.

### `enchant_create_ticket` (~145 tokens)

Create ticket

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.

Input parameters:

- `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, required): Ticket subject.
- `user_id` (string): User id to assign the ticket to.

### `enchant_update_ticket` (~186 tokens)

Update ticket

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

Input parameters:

- `id` (string, required): 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.

### `enchant_add_ticket_labels` (~62 tokens)

Add labels to ticket

WRITE: add one or more labels to a ticket without changing its other labels. Enchant REST: PUT /tickets/{id}/labels/{label_ids}.

Input parameters:

- `id` (string, required): Ticket id.
- `label_ids` (array, required): Label ids to add.

### `enchant_remove_ticket_labels` (~62 tokens)

Remove labels from ticket

WRITE: remove one or more labels from a ticket; its other labels stay. Enchant REST: DELETE /tickets/{id}/labels/{label_ids}.

Input parameters:

- `id` (string, required): Ticket id.
- `label_ids` (array, required): Label ids to remove.

### `enchant_reply_to_ticket` (~150 tokens)

Reply to customer

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

Input parameters:

- `attachment_ids` (array): Ids of attachments already uploaded.
- `body` (string, required): Reply body.
- `html` (boolean): True if body is HTML (default false: plain text).
- `id` (string, required): Ticket id.
- `to` (string, required): Recipient address, normally the customer's email.
- `user_id` (string, required): Id of the user (agent) the reply is sent as; see enchant_list_users.

### `enchant_add_note` (~114 tokens)

Add internal note

WRITE: add an internal note to a ticket (not sent to the customer). Enchant REST: POST /tickets/{id}/messages (type note).

Input parameters:

- `attachment_ids` (array): Ids of attachments already uploaded.
- `body` (string, required): Note body.
- `html` (boolean): True if body is HTML (default false: plain text).
- `id` (string, required): Ticket id.
- `user_id` (string, required): Id of the user (agent) the note is from; see enchant_list_users.

### `enchant_create_customer` (~75 tokens)

Create customer

WRITE: create a customer with optional contacts (email, twitter, phone). Enchant REST: POST /customers.

Input parameters:

- `contacts` (array): Contacts of the customer.
- `first_name` (string)
- `last_name` (string)
- `summary` (string): Short free-text summary shown on the customer profile.

### `enchant_update_customer` (~111 tokens)

Update customer

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

Input parameters:

- `contacts` (array): The full new contact list (replaces the existing one).
- `first_name` (string)
- `id` (string, required): Customer id.
- `last_name` (string)
- `summary` (string): Short free-text summary shown on the customer profile.

### `enchant_add_customer_contact` (~72 tokens)

Add customer contact

WRITE: add one contact (email, twitter or phone) to a customer. Enchant REST: POST /customers/{id}/contacts.

Input parameters:

- `id` (string, required): Customer id.
- `type` (string, required): Contact type.
- `value` (string, required): Email address, Twitter screen name or phone number.

### `enchant_delete_customer_contact` (~63 tokens)

Delete customer contact

WRITE, DELETES DATA: remove one contact from a customer. Enchant REST: DELETE /customers/{id}/contacts/{contact_id}.

Input parameters:

- `contact_id` (string, required): Contact id (from the customer's contacts).
- `id` (string, required): Customer id.

## Diagnostics

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

## Score history

- 2026-10-17: 64
- 2026-10-16: 64
- 2026-10-15: 63
- 2026-10-14: 63
- 2026-10-13: 61
- 2026-10-12: 60

## Common questions

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

## Links

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