eDesk MCP by usefulapi
REMOTE · EDESK.USEFULAPI.IO
Work with eDesk support tickets, replies, internal notes, contacts and sales orders.
Available components
Last scanned (53 minutes 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 Usability83
- 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 2208 tokens (~122/item across 18 items; 18 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
- We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 19 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.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 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://edesk.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 edesk.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://edesk.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://edesk.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://edesk.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://edesk.usefulapi.io/mcp |
| Authorisation server | https://edesk.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://edesk.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/edesk/ |
| http (plaintext) | http://edesk.usefulapi.io/mcp | Inconclusive | 302 | http://edesk.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 →
edesk_add_order_note Add order note ~58
WRITE: add an internal note to a sales order (never sent to the customer). POST /order-notes.
| Name | Type | Req | Description |
|---|---|---|---|
| sales_order_id | integer | yes | eDesk sales order id. |
| text | string | yes | The note text. |
No output schema declared.
No examples provided.
edesk_add_ticket_note Add internal ticket note ~65
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.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | The note text. |
| ticket_id | integer | yes | eDesk ticket id. |
No output schema declared.
No examples provided.
edesk_get_message Get message ~58
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| message_id | integer | yes | eDesk message id. |
No output schema declared.
No examples provided.
edesk_get_sales_order Get sales order ~72
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| sales_order_id | integer | yes | eDesk sales order id (the sales_order_id on a ticket). |
No output schema declared.
No examples provided.
edesk_get_template Get reply template ~34
One reply template by id. GET /templates/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| template_id | integer | yes | eDesk template id. |
No output schema declared.
No examples provided.
edesk_get_ticket Get ticket ~61
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| ticket_id | integer | yes | eDesk ticket id. |
No output schema declared.
No examples provided.
edesk_list_channels List channels ~99
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.
| Name | Type | Req | Description |
|---|---|---|---|
| items_per_page | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
edesk_list_contacts List contacts ~151
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.
| Name | Type | Req | Description |
|---|---|---|---|
| consumer_id | integer | – | Filter by consumer id. |
| string | – | Filter by email. | |
| items_per_page | integer | – | Results per page, 1-100 (default 25). |
| name | string | – | Filter by full name. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| phone_number | string | – | Filter by phone number. |
| query | string | – | Free-text search. |
No output schema declared.
No examples provided.
edesk_list_order_notes List order notes ~84
List the internal notes attached to sales orders (id, sales order id, author, text, attachments). GET /order-notes.
| Name | Type | Req | Description |
|---|---|---|---|
| items_per_page | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
edesk_list_sales_orders List sales orders ~308
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.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | integer | – | Only orders from this channel. |
| contact_id | integer | – | Only orders of this contact. |
| created_after | string | – | Only orders created on or after this date, yyyy-mm-dd. |
| created_before | string | – | Only orders created on or before this date, yyyy-mm-dd. |
| id_from | integer | – | Only orders with an eDesk id greater than or equal to this. |
| id_to | integer | – | Only orders with an eDesk id less than or equal to this. |
| items_per_page | integer | – | Results per page, 1-100 (default 25). |
| order_by | string | – | Sort field. |
| order_direction | string | – | Sort direction. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| seller_order_id | string | – | Only the order with this marketplace order id. |
| status | string | – | Only orders with this status. |
| updated_after | string | – | Only orders last updated on or after this date, yyyy-mm-dd. |
| updated_before | string | – | Only orders last updated on or before this date, yyyy-mm-dd. |
No output schema declared.
No examples provided.
edesk_list_tag_groups List tag groups ~72
List the tag groups that organize ticket tags. GET /tag-groups.
| Name | Type | Req | Description |
|---|---|---|---|
| items_per_page | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
edesk_list_tags List tags ~89
List ticket tags with id, name, color, active flag and tag group id. Use the ids in edesk_update_ticket (tag_ids). GET /tags.
| Name | Type | Req | Description |
|---|---|---|---|
| items_per_page | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
edesk_list_templates List reply templates ~78
List saved reply templates (id, name, subject, body text, channels, usage). GET /templates.
| Name | Type | Req | Description |
|---|---|---|---|
| items_per_page | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
edesk_list_tickets List tickets ~301
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.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | integer | – | Only tickets on this channel (see edesk_list_channels). |
| contact_id | integer | – | Only tickets of this contact (customer). |
| items_per_page | integer | – | Results per page, 1-100 (default 25). |
| order_by | string | – | Sort field. |
| order_direction | string | – | Sort direction. |
| owner_user_id | integer | – | Only tickets assigned to this user. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| sales_order_id | integer | – | Only tickets linked to this eDesk sales order id. |
| seller_order_id | string | – | Only tickets for this marketplace order id (the id the marketplace shows). |
| status | string | – | Only tickets with this status. |
| type | string | – | Only tickets of this type. |
| updated_after | string | – | Only tickets last updated on or after this date, yyyy-mm-dd. |
| updated_before | string | – | Only tickets last updated on or before this date, yyyy-mm-dd. |
No output schema declared.
No examples provided.
edesk_list_users List users (agents) ~90
List the eDesk users (support agents) with id, name, email, username, role and active flag. Use the ids as ticket owners. GET /users.
| Name | Type | Req | Description |
|---|---|---|---|
| items_per_page | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
edesk_reply_to_ticket Reply to customer ~191
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.
| Name | Type | Req | Description |
|---|---|---|---|
| subject | string | – | Subject, for channels that use one (such as email). |
| text | string | yes | The reply text the customer will receive. |
| ticket_id | integer | yes | eDesk ticket id. |
No output schema declared.
No examples provided.
edesk_update_ticket Update ticket ~150
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| owner_user_id | integer | – | User id to assign the ticket to (see edesk_list_users). |
| status | string | – | New status, e.g. Open, Pending or Closed. |
| subject | string | – | New subject. |
| tag_ids | array | – | Tag ids for the ticket (see edesk_list_tags). |
| ticket_id | integer | yes | eDesk ticket id. |
No output schema declared.
No examples provided.
edesk_whoami Who am I ~39
The eDesk user the API token belongs to: id, name, email, username, role and active flag. GET /whoami.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the eDesk MCP by usefulapi server?
eDesk MCP by usefulapi is a hosted endpoint at https://edesk.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 · edesk.usefulapi.io
claude mcp add --transport http io-usefulapi-edesk 'https://edesk.usefulapi.io/mcp'
What is the eDesk MCP by usefulapi server?
eDesk MCP by usefulapi is listed in the public MCP registry as io.usefulapi/edesk. Work with eDesk support tickets, replies, internal notes, contacts and sales orders. This page covers its hosted endpoint (https://edesk.usefulapi.io/mcp).
Is the eDesk MCP by usefulapi server safe to use?
eDesk 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 eDesk MCP by usefulapi server expose?
eDesk MCP by usefulapi exposes 18 tools: edesk_whoami, edesk_list_users, edesk_list_channels, edesk_list_tag_groups, edesk_list_tags, and 13 more. Their descriptions and schemas cost roughly 2,000 tokens of context every time the server is loaded.
Does the eDesk MCP by usefulapi server require authentication?
Yes. eDesk 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 eDesk MCP by usefulapi server still maintained?
eDesk 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.