Skip to content

Enchant MCP by usefulapi

io.usefulapi/enchantusefulapi.iostreamable-httpv1.27.5Scanned

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

16 tools: 10 can delete or cancel things and 6 only read.

Tools: 10 delete, 0 irreversible, 0 write, 6 read.
  • Reads private data · 5
  • Reads text others write · 6
  • Can send data out · 1
  • No findings

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

Anlyon alternative

10 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 Enchant MCP by usefulapi can do

The Enchant MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 16 tools. It can delete or cancel things (10 tools: enchant_create_ticket, enchant_update_ticket, enchant_add_ticket_labels, enchant_remove_ticket_labels and 6 more). 6 tools only read.

5 tools read private data (enchant_list_tickets, enchant_list_users, enchant_list_customers and 2 more); 6 tools bring in text other people can write (enchant_list_tickets, enchant_get_ticket, enchant_list_users and 3 more); 1 tool can send data out of your system (enchant_reply_to_ticket). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Oct 25, 2026, version 1.27.5.

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.

16 tools

Deletes or cancels 10Claude Code: deny
  • enchant_add_customer_contactWRITE: add one contact (email, twitter or phone) to a customer.No findings

    Why it is in this group

    • The name "enchant_add_customer_contact" says "add": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    WRITE: add one contact (email, twitter or phone) to a customer. Enchant REST: POST /customers/{id}/contacts.

    Annotations the server declares

    • title: Add customer contact
    • destructiveHint: true
  • enchant_add_noteWRITE: add an internal note to a ticket (not sent to the customer).No findings

    Why it is in this group

    • The name "enchant_add_note" says "add": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    WRITE: add an internal note to a ticket (not sent to the customer). Enchant REST: POST /tickets/{id}/messages (type note).

    Annotations the server declares

    • title: Add internal note
    • destructiveHint: true
  • enchant_add_ticket_labelsWRITE: add one or more labels to a ticket without changing its other labels.No findings

    Why it is in this group

    • The name "enchant_add_ticket_labels" says "add": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    WRITE: add one or more labels to a ticket without changing its other labels. Enchant REST: PUT /tickets/{id}/labels/{label_ids}.

    Annotations the server declares

    • title: Add labels to ticket
    • destructiveHint: true
  • enchant_create_customerWRITE: create a customer with optional contacts (email, twitter, phone).No findings

    Why it is in this group

    • The name "enchant_create_customer" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    WRITE: create a customer with optional contacts (email, twitter, phone). Enchant REST: POST /customers.

    Annotations the server declares

    • title: Create customer
    • destructiveHint: true
  • enchant_create_ticketWRITE: create an email ticket.No findings

    Why it is in this group

    • The name "enchant_create_ticket" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Create ticket
    • destructiveHint: true
  • enchant_delete_customer_contactWRITE, DELETES DATA: remove one contact from a customer.No findings

    Why it is in this group

    • The name "enchant_delete_customer_contact" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    WRITE, DELETES DATA: remove one contact from a customer. Enchant REST: DELETE /customers/{id}/contacts/{contact_id}.

    Annotations the server declares

    • title: Delete customer contact
    • destructiveHint: true
  • enchant_remove_ticket_labelsWRITE: remove one or more labels from a ticket; its other labels stay.No findings

    Why it is in this group

    • The name "enchant_remove_ticket_labels" says "remove": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    WRITE: remove one or more labels from a ticket; its other labels stay. Enchant REST: DELETE /tickets/{id}/labels/{label_ids}.

    Annotations the server declares

    • title: Remove labels from ticket
    • destructiveHint: true
  • enchant_reply_to_ticketWRITE: send an outbound reply on a ticket.Can send data outNo findings

    Why it is in this group

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

    What it can reach

    • outboundThe name "enchant_reply_to_ticket" says "reply": it sends or publishes something to other people.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • title: Reply to customer
    • destructiveHint: true
  • enchant_update_customerWRITE: update a customer's name or summary.No findings

    Why it is in this group

    • The name "enchant_update_customer" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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}.

    Annotations the server declares

    • title: Update customer
    • destructiveHint: true
  • enchant_update_ticketWRITE: change a ticket: state (open, hold, closed), assignee, inbox, subject, spam or trash (not both true).No findings

    Why it is in this group

    • The name "enchant_update_ticket" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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}.

    Annotations the server declares

    • title: Update ticket
    • destructiveHint: true
Only reads 6Show 6 read-only tools
  • enchant_get_attachmentGet the metadata of an attachment (name, size, MIME type) by id; attachment ids appear in ticket messages.Reads private dataReads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe description's first sentence says "get" and "message": it reads messages.
    • untrusted-inputThe description's first sentence says "get" and "ticket": it reads issues, which other people can write.
    Description, as the server wrote it
    Get the metadata of an attachment (name, size, MIME type) by id; attachment ids appear in ticket messages. Enchant REST: GET /attachments/{id}.

    Annotations the server declares

    • title: Get attachment
    • readOnlyHint: true
  • enchant_get_customerGet one customer by id, with the contacts (emails, phones, Twitter names).Reads private dataReads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe description's first sentence says "get" and "contact": it reads contacts.
    • untrusted-inputThe description's first sentence says "get" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    Get one customer by id, with the contacts (emails, phones, Twitter names). Enchant REST: GET /customers/{id}.

    Annotations the server declares

    • title: Get customer
    • readOnlyHint: true
  • enchant_get_ticketGet one ticket by id.Reads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe name "enchant_get_ticket" says "get" and "ticket": it reads issues, which other people can write.
    • untrusted-inputThe description's first sentence says "get" and "ticket": it reads issues, which other people can write.
    Description, as the server wrote it
    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}.

    Annotations the server declares

    • title: Get ticket
    • readOnlyHint: true
  • enchant_list_customersList customers, or find one by contact: set contact_type and contact_value (for example email + an address).Reads private dataReads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe description's first sentence says "list" and "contact": it reads contacts.
    • untrusted-inputThe description's first sentence says "list" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    List customers, or find one by contact: set contact_type and contact_value (for example email + an address). Enchant REST: GET /customers.

    Annotations the server declares

    • title: List customers
    • readOnlyHint: true
  • enchant_list_ticketsList and filter tickets (newest first by default).Reads private dataReads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe input names an inbox (input.inbox_ids), and the tool reads: it reads mail.
    • untrusted-inputThe name "enchant_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 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.

    Annotations the server declares

    • title: List tickets
    • readOnlyHint: true
  • enchant_list_usersList the help desk users (agents): id, name, email.Reads private dataReads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe description's first sentence says "list" and "email": it reads mail.
    • untrusted-inputThe description's first sentence says "list" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List users (agents)
    • 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.

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

Reads private data5
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write6
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
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__enchant__enchant_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:35 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: 10 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://enchant.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://enchant.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.

No check matched anything in these tool definitions. That is not a safety guarantee.

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

claude mcp add --transport http enchant https://enchant.usefulapi.io/mcp
claude mcp add --transport http enchant https://enchant.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__enchant__enchant_list_tickets",
      "mcp__enchant__enchant_get_ticket",
      "mcp__enchant__enchant_list_users",
      "mcp__enchant__enchant_list_customers",
      "mcp__enchant__enchant_get_customer",
      "mcp__enchant__enchant_get_attachment"
    ],
    "ask": [],
    "deny": [
      "mcp__enchant__enchant_create_ticket",
      "mcp__enchant__enchant_update_ticket",
      "mcp__enchant__enchant_add_ticket_labels",
      "mcp__enchant__enchant_remove_ticket_labels",
      "mcp__enchant__enchant_reply_to_ticket",
      "mcp__enchant__enchant_add_note",
      "mcp__enchant__enchant_create_customer",
      "mcp__enchant__enchant_update_customer",
      "mcp__enchant__enchant_add_customer_contact",
      "mcp__enchant__enchant_delete_customer_contact"
    ]
  }
}

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

Capability tags behind 7 rules
  • mcp__enchant__enchant_list_tickets private-data, untrusted-input
  • mcp__enchant__enchant_get_ticket untrusted-input
  • mcp__enchant__enchant_list_users private-data, untrusted-input
  • mcp__enchant__enchant_list_customers private-data, untrusted-input
  • mcp__enchant__enchant_get_customer private-data, untrusted-input
  • mcp__enchant__enchant_get_attachment private-data, untrusted-input
  • mcp__enchant__enchant_reply_to_ticket 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/enchant/verify?hash=9b9ef1b7c26843267bce473bb914a7b237468a9e266d28fd810dc2047edaf230" | jq -e '.changed == false'

Pinned hash 9b9ef1b7c268, from Oct 25, 2026, 23:19 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.usefulapi/enchant/changes.xml

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

Badge

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

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

Enchant MCP by usefulapi: questions and answers

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

Is the Enchant MCP by usefulapi safe?

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

Can the Enchant MCP by usefulapi delete data?

Yes. 10 tools can delete, cancel or revoke something: enchant_create_ticket, enchant_update_ticket, enchant_add_ticket_labels, enchant_remove_ticket_labels, enchant_reply_to_ticket, enchant_add_note and 4 more.

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

16 tools: 10 destructive, 6 read. enchant_create_ticket, enchant_update_ticket, enchant_add_ticket_labels, enchant_remove_ticket_labels, enchant_reply_to_ticket, enchant_add_note, enchant_create_customer, enchant_update_customer and 8 more.

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

Its remote endpoint did not answer the last anonymous look.

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

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): enchant_reply_to_ticket.

Has the Enchant MCP by usefulapi changed its tools?

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