Skip to content

eDesk MCP by usefulapi

io.usefulapi/edeskusefulapi.iostreamable-httpv1.29.0Scanned

Work with eDesk support tickets, replies, internal notes, contacts and sales orders.

18 tools: 4 can delete or cancel things and 14 only read.

Tools: 4 delete, 0 irreversible, 0 write, 14 read.
  • Reads private data · 9
  • Reads text others write · 18
  • Can send data out · 1
  • No findings

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

Anlyon alternative

4 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 eDesk MCP by usefulapi can do

The eDesk MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 18 tools. It can delete or cancel things (4 tools: edesk_update_ticket, edesk_add_ticket_note, edesk_reply_to_ticket and edesk_add_order_note). 14 tools only read.

9 tools read private data (edesk_whoami, edesk_list_users, edesk_list_channels and 6 more); 18 tools bring in text other people can write (edesk_whoami, edesk_list_users, edesk_list_channels and 15 more); 1 tool can send data out of your system (edesk_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.29.0.

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.

18 tools

Deletes or cancels 4Claude Code: deny
  • edesk_add_order_noteWRITE: add an internal note to a sales order (never sent to the customer).Reads text others writeNo findings

    Why it is in this group

    • The name "edesk_add_order_note" says "add": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    WRITE: add an internal note to a sales order (never sent to the customer). POST /order-notes.

    Annotations the server declares

    • title: Add order note
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • edesk_add_ticket_noteWRITE: add an internal note to a ticket.Reads text others writeNo findings

    Why it is in this group

    • The name "edesk_add_ticket_note" says "add": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    WRITE: add an internal note to a ticket. The note is for the team only and is never sent to the customer. POST /messages with type Note.

    Annotations the server declares

    • title: Add internal ticket note
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • edesk_reply_to_ticketWRITE, CUSTOMER-VISIBLE: send a reply on a ticket.Reads text others writeCan send data outNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe name "edesk_reply_to_ticket" says "reply": it sends or publishes something to other people.
    Description, as the server wrote it
    WRITE, CUSTOMER-VISIBLE: send a reply on a ticket. eDesk queues it for delivery to the marketplace or email channel, so it cannot be recalled once queued. The audience is the channel's default: on a Mirakl channel it is the channel's "Default messages recipients" setting (customer, operator or both), and this API cannot choose recipients (use the eDesk reply box when they matter). Only call this when the user has approved the exact text and audience. If the call fails in transit, the reply may still be queued: check the ticket before retrying. Use edesk_add_ticket_note for an internal note. POST /messages with type Message.

    Annotations the server declares

    • title: Reply to customer
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • edesk_update_ticketWRITE: change a ticket's status, owner (assignee), tags or subject.Reads text others writeNo findings

    Why it is in this group

    • The name "edesk_update_ticket" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    WRITE: change a ticket's status, owner (assignee), tags or subject. Only the fields you pass are sent. tag_ids is sent as given: read the ticket first (tags_ids) and include the tags to keep. Nothing is sent to the customer. PUT /tickets/{id}.

    Annotations the server declares

    • title: Update ticket
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
Only reads 14Show 14 read-only tools
  • edesk_get_messageOne ticket message or internal note by id (from a ticket's message ids): body, direction, type (Message or Note), author and attachments.Reads private dataReads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe name "edesk_get_message" says "get" and "message": it reads messages.
    • private-dataThe description's first sentence says "message": it reads messages.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe name "edesk_get_message" says "get" and "message": it reads messages, which other people can write.
    • untrusted-inputThe description's first sentence says "ticket": it reads issues, which other people can write.
    Description, as the server wrote it
    One ticket message or internal note by id (from a ticket's message ids): body, direction, type (Message or Note), author and attachments. GET /messages/{id}.

    Annotations the server declares

    • title: Get message
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • edesk_get_sales_orderOne sales order by id with items, amounts, ship-to and bill-to addresses, tracking codes, delivery dates, the linked ticket id and order note ids.Reads private dataReads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe description's first sentence says "note": it reads notes.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "ticket": it reads issues, which other people can write.
    Description, as the server wrote it
    One sales order by id with items, amounts, ship-to and bill-to addresses, tracking codes, delivery dates, the linked ticket id and order note ids. GET /sales-orders/{id}.

    Annotations the server declares

    • title: Get sales order
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • edesk_get_templateOne reply template by id.Reads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "reply": it reads comments, which other people can write.
    Description, as the server wrote it
    One reply template by id. GET /templates/{id}.

    Annotations the server declares

    • title: Get template
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • edesk_get_ticketOne ticket by id with its status, owner, tags, custom fields, linked sales order and the ids of its messages (read each with edesk_get_message).Reads private dataReads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe description's first sentence says "message": it reads messages.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe name "edesk_get_ticket" says "get" and "ticket": it reads issues, which other people can write.
    • untrusted-inputThe description's first sentence says "ticket": it reads issues, which other people can write.
    Description, as the server wrote it
    One ticket by id with its status, owner, tags, custom fields, linked sales order and the ids of its messages (read each with edesk_get_message). GET /tickets/{id}.

    Annotations the server declares

    • title: Get ticket
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • edesk_list_channelsList the sales channels connected to eDesk (Amazon, eBay, Shopify, email, ...) with id, type, name, country and currency.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "edesk_list_channels" 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 server marks it openWorldHint: true: it reaches things outside the server's own data.
    • 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 sales channels connected to eDesk (Amazon, eBay, Shopify, email, ...) with id, type, name, country and currency. Use the ids to filter tickets and orders. GET /channels.

    Annotations the server declares

    • title: List channels
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • edesk_list_contactsSearch the contacts (customers) of the helpdesk by free text, email, name, phone number or consumer id.Reads private dataReads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe name "edesk_list_contacts" says "list" and "contact": it reads contacts.
    • private-dataThe description's first sentence says "search" and "contact": it reads contacts.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "search" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    Search the contacts (customers) of the helpdesk by free text, email, name, phone number or consumer id. Returns id, channel, full name, email and phone. GET /contacts.

    Annotations the server declares

    • title: List contacts
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • edesk_list_order_notesList the internal notes attached to sales orders (id, sales order id, author, text, attachments).Reads private dataReads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe name "edesk_list_order_notes" says "list" and "note": it reads notes.
    • private-dataThe description's first sentence says "list" and "note": it reads notes.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    List the internal notes attached to sales orders (id, sales order id, author, text, attachments). GET /order-notes.

    Annotations the server declares

    • title: List order notes
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • edesk_list_sales_ordersList the marketplace/store orders that eDesk holds, with status, items, amounts, addresses, tracking codes and the linked ticket id.Reads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • 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 the marketplace/store orders that eDesk holds, with status, items, amounts, addresses, tracking codes and the linked ticket id. Filter by status, channel, contact, marketplace order id, id range and created/updated dates. GET /sales-orders.

    Annotations the server declares

    • title: List sales orders
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • edesk_list_tag_groupsList the tag groups that organize ticket tags.Reads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • 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 the tag groups that organize ticket tags. GET /tag-groups.

    Annotations the server declares

    • title: List tag groups
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • edesk_list_tagsList ticket tags with id, name, color, active flag and tag group id.Reads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • 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 ticket tags with id, name, color, active flag and tag group id. Use the ids in edesk_update_ticket (tag_ids). GET /tags.

    Annotations the server declares

    • title: List tags
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • edesk_list_templatesList saved reply templates (id, name, subject, body text, channels, usage).Reads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "list" and "reply": it reads comments, which other people can write.
    Description, as the server wrote it
    List saved reply templates (id, name, subject, body text, channels, usage). GET /templates.

    Annotations the server declares

    • title: List templates
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • edesk_list_ticketsList support tickets from all channels with subject, type, status, channel, owner, contact, linked sales order id, tag ids, message ids, reply count and AI classification.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "edesk_list_tickets" 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 server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe name "edesk_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 support tickets from all channels with subject, type, status, channel, owner, contact, linked sales order id, tag ids, message ids, reply count and AI classification. Filter by status, type, channel, contact, owner, sales order, seller (marketplace) order id and last-updated date. GET /tickets.

    Annotations the server declares

    • title: List tickets
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • edesk_list_usersList the eDesk users (support agents) with id, name, email, username, role and active flag.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "edesk_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 server marks it openWorldHint: true: it reaches things outside the server's own data.
    • 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 eDesk users (support agents) with id, name, email, username, role and active flag. Use the ids as ticket owners. GET /users.

    Annotations the server declares

    • title: List users
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • edesk_whoamiThe eDesk user the API token belongs to: id, name, email, username, role and active flag.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "edesk_whoami" says "whoami": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "email": it reads mail.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    The eDesk user the API token belongs to: id, name, email, username, role and active flag. GET /whoami.

    Annotations the server declares

    • title: Who am I
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: 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.

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

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__edesk__edesk_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: 4 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://edesk.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://edesk.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: 4 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://edesk.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://edesk.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

Pinned to version 1.29.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http edesk https://edesk.usefulapi.io/mcp
claude mcp add --transport http edesk https://edesk.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__edesk__edesk_whoami",
      "mcp__edesk__edesk_list_users",
      "mcp__edesk__edesk_list_channels",
      "mcp__edesk__edesk_list_tag_groups",
      "mcp__edesk__edesk_list_tags",
      "mcp__edesk__edesk_list_templates",
      "mcp__edesk__edesk_get_template",
      "mcp__edesk__edesk_list_tickets",
      "mcp__edesk__edesk_get_ticket",
      "mcp__edesk__edesk_get_message",
      "mcp__edesk__edesk_list_contacts",
      "mcp__edesk__edesk_list_sales_orders",
      "mcp__edesk__edesk_get_sales_order",
      "mcp__edesk__edesk_list_order_notes"
    ],
    "ask": [],
    "deny": [
      "mcp__edesk__edesk_update_ticket",
      "mcp__edesk__edesk_add_ticket_note",
      "mcp__edesk__edesk_reply_to_ticket",
      "mcp__edesk__edesk_add_order_note"
    ]
  }
}

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

Capability tags behind 18 rules
  • mcp__edesk__edesk_whoami private-data, untrusted-input
  • mcp__edesk__edesk_list_users private-data, untrusted-input
  • mcp__edesk__edesk_list_channels private-data, untrusted-input
  • mcp__edesk__edesk_list_tag_groups untrusted-input
  • mcp__edesk__edesk_list_tags untrusted-input
  • mcp__edesk__edesk_list_templates untrusted-input
  • mcp__edesk__edesk_get_template untrusted-input
  • mcp__edesk__edesk_list_tickets private-data, untrusted-input
  • mcp__edesk__edesk_get_ticket private-data, untrusted-input
  • mcp__edesk__edesk_get_message private-data, untrusted-input
  • mcp__edesk__edesk_list_contacts private-data, untrusted-input
  • mcp__edesk__edesk_list_sales_orders untrusted-input
  • mcp__edesk__edesk_get_sales_order private-data, untrusted-input
  • mcp__edesk__edesk_list_order_notes private-data, untrusted-input
  • mcp__edesk__edesk_update_ticket untrusted-input
  • mcp__edesk__edesk_add_ticket_note untrusted-input
  • mcp__edesk__edesk_reply_to_ticket untrusted-input, outbound
  • mcp__edesk__edesk_add_order_note untrusted-input

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/edesk/verify?hash=ac27ad260ea8f96400c1f0d486bc0ad78d52ff76f67237e124be2a47dfdcb0cc" | jq -e '.changed == false'

Pinned hash ac27ad260ea8, from Oct 25, 2026, 23:18 UTC.

Watch

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

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

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

Badge

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

Source: MCP Registry · repository. Synced Nov 21, 2026, 12:17 UTC.

eDesk MCP by usefulapi: questions and answers

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

Is the eDesk MCP by usefulapi safe?

No scan can promise that. What its definitions show: 18 tools, 4 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 eDesk MCP by usefulapi delete data?

Yes. 4 tools can delete, cancel or revoke something: edesk_update_ticket, edesk_add_ticket_note, edesk_reply_to_ticket and edesk_add_order_note.

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

18 tools: 4 destructive, 14 read. edesk_update_ticket, edesk_add_ticket_note, edesk_reply_to_ticket, edesk_add_order_note, edesk_whoami, edesk_list_users, edesk_list_channels, edesk_list_tag_groups and 10 more.

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

Its remote endpoint did not answer the last anonymous look.

Does the eDesk 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): edesk_reply_to_ticket.

Has the eDesk MCP by usefulapi changed its tools?

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