Name: Order Desk MCP by usefulapi
Author: usefulapi

Order Desk MCP by usefulapi

Search Order Desk orders and inventory; read order items and shipments; create or update orders.

Tool-list grade A Remote · Streamable HTTP No auth needed 15 tools v1.20.2 MIT

No reviews yet by usefulapiGitHub The publisher’s own endpoint — this marketplace is not in the path

93/100

tool-list score

tools declared

remote

at its publisher

—

calls last 7d

What it does

Search Order Desk orders and inventory; read order items and shipments; create or update orders.

Quickstart

# 1 — add it to Claude Code
claude mcp add --scope user --transport http order-desk-mcp-by-usefulapi https://order-desk.usefulapi.io/mcp

# 2 — ask your agent for something these tools do
#   orderdesk_get_store, orderdesk_list_orders, orderdesk_get_order and 12 more

Order Desk MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.

Publishernot claimed

usefulapi598 servers

25 categories

All 598 servers

Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.

Tool surface

What the model actually sees. Descriptions are diffed on every release — see version history.

Only tools that write or reach the network

The store's name, id, FOLDERS (id -> name; orders live in exactly one folder, and folder ids are needed to filter and move orders) and key settings (timezone, locale, stock behavior, shipping methods). The API key and mail credentials are never returned. GET /store.

No parameter schema on file.

Search orders, newest first, with items, addresses, totals, payment and shipments. Filters combine with AND. Prefer a date range: Order Desk asks clients to avoid open-ended queries. Page with limit and offset (next_offset). GET /orders.

Parameter	Type	Required	Notes
folder_id	string	no	Folder id, or several separated by commas (see orderdesk_get_store).
folder_name	string	no	The folder's exact name instead of its id.
source_id	string	no	Your original order id from the cart or marketplace.
source_name	string	no	Order source name (cart or marketplace).
added_from	string	no	Orders added on or after this time (a date means the start of that UTC day).
added_to	string	no	Orders added on or before this time (a date means the end of that UTC day).
modified_from	string	no	Orders modified on or after this time.
modified_to	string	no	Orders modified on or before this time.
email	string	no	Customer e-mail address.
customer_id	string	no	Customer id in the originating system.
customer_last_name	string	no	—
customer_first_name	string	no	—
shipping_last_name	string	no	—
shipping_first_name	string	no	—
include_history	boolean	no	Include each order's history (slow; use with a small limit).
order_by	string	no	Order field to sort by (default date_added).
order	string	no	Sort direction (default DESC).
limit	integer	no	How many records to return, 1-100 (default 20).
offset	integer	no	Records to skip (default 0). Pass the previous reply's next_offset.

One order by Order Desk's internal id: addresses, items, totals, payment, notes, discounts, checkout data and shipments. To find an order by your own id, use orderdesk_list_orders with source_id. GET /orders/{order_id}.

Parameter	Type	Required	Notes
order_id	integer	yes	Order Desk's internal order id (not the cart's order number).

The line items of one order (name, SKU, price, quantity, weight, delivery type, variations). GET /orders/{order_id}/order-items.

Parameter	Type	Required	Notes
order_id	integer	yes	Order Desk's internal order id.

The shipments recorded against an order: carrier, tracking number and URL, method, weight, cost, dates. GET /orders/{order_id}/shipments.

Parameter	Type	Required	Notes
order_id	integer	yes	Order Desk's internal order id.

WRITE: add a new order to the store. Needs at least one item, and a name or company in the shipping or customer address (if only one address is given the other is copied from it). Omit folder_id to land in the first folder. Order Desk rejects an order it recognizes as a duplicate and names the existing order id. POST /orders.

Parameter	Type	Required	Notes
order_items	array	yes	Line items (at least one).
shipping	object	no	Shipping address.
customer	object	no	Customer (billing) address.
email	string	no	Customer e-mail address.
source_id	string	no	Your own order id (the order's Order Desk id is used when blank).
source_name	string	no	Order source / cart name (default Order Desk).
folder_id	integer	no	Folder to put the order in (see orderdesk_get_store).
shipping_method	string	no	—
shipping_total	number	no	—
handling_total	number	no	—
tax_total	number	no	—
payment_type	string	no	Visa, MasterCard, PayPal, ...
payment_status	string	no	Defaults to Captured.
checkout_data	object	no	Editable extra order details (max 3,500 characters as JSON).
order_metadata	object	no	Hidden extra order details (max 2,000 characters as JSON).

WRITE: change fields of an existing order. Order Desk's PUT replaces the whole record, so this reads the order, applies only the fields you pass (shipping/customer address fields and checkout_data/order_metadata keys are merged into what is there, other values replaced) and sends the complete record back, items included. The order keeps its folder; use orderdesk_move_orders to move it. PUT /orders

Parameter	Type	Required	Notes
order_id	integer	yes	Order Desk's internal order id.
email	string	no	—
shipping_method	string	no	—
shipping_total	number	no	—
handling_total	number	no	—
tax_total	number	no	—
payment_status	string	no	—
shipping	object	no	Shipping address fields to change (others are kept).
customer	object	no	Customer address fields to change (others are kept).
checkout_data	object	no	Checkout data keys to set (other keys are kept).
order_metadata	object	no	Order metadata keys to set (other keys are kept).

WRITE: add one line item to an existing order; Order Desk recalculates the totals. POST /orders/{order_id}/order-items.

Parameter	Type	Required	Notes
order_id	integer	yes	Order Desk's internal order id.
item	object	yes	The line item to add (name, code, price, quantity...).

WRITE: append an entry to an order's history. History is append-only (entries cannot be edited or removed) and an order holds at most 250 entries, so do not use it for routine polling. POST /orders/{order_id}/order-history.

Parameter	Type	Required	Notes
order_id	integer	yes	Order Desk's internal order id.
note	string	yes	The note text.
source_name	string	no	What wrote the entry (default API).

WRITE: record a shipment (carrier and tracking number) against an order. One shipment per parcel; several shipments represent a partial fulfillment. Use "n/a" when there is no tracking number. If tracking_url is omitted Order Desk derives it. POST /orders/{order_id}/shipments.

Parameter	Type	Required	Notes
order_id	integer	yes	Order Desk's internal order id.
tracking_number	string	yes	Carrier tracking number, or "n/a".
carrier_code	string	no	Carrier code such as USPS or FedEx.
shipment_method	string	no	Shipping service name, e.g. First Class International.
weight	number	no	Final shipment weight.
cost	number	no	Your cost to send the shipment.
tracking_url	string	no	—

WRITE: move one or more orders to another folder. Moving runs the rules attached to the destination folder (which can send e-mail, call fulfillment services, etc.) and writes a history entry. Pass exactly one of destination_folder_id or destination_folder_name (see orderdesk_get_store). Returns each order's previous folder. POST /move-orders.

Parameter	Type	Required	Notes
order_ids	array	yes	Order Desk's internal order ids.
destination_folder_id	integer	no	Folder id to move to.
destination_folder_name	string	no	Exact folder name to move to.

Search the store's inventory (SKU, name, price, cost, weight, stock, location). Order Desk returns every match with no paging, so narrow with search/code/name; limit and offset slice the result here. GET /inventory-items.

Parameter	Type	Required	Notes
search	string	no	Matches name, code and metadata together.
code	string	no	Exact SKU.
name	string	no	Product name.
manufacturer_sku	string	no	—
location	string	no	Warehouse or fulfillment method.
updated_from	string	no	Items updated on or after this time.
limit	integer	no	How many items to return, 1-200 (default 50).
offset	integer	no	Records to skip (default 0). Pass the previous reply's next_offset.

One inventory item by Order Desk's internal id. GET /inventory-items/{inventory_item_id}.

Parameter	Type	Required	Notes
inventory_item_id	integer	yes	Order Desk's internal inventory item id (see orderdesk_list_inventory_items).

WRITE: add an inventory item. The code (SKU) must match the code your orders arrive with. POST /inventory-items.

Parameter	Type	Required	Notes
name	string	yes	Product name.
code	string	yes	Unique SKU.
price	number	no	—
cost	number	no	Item cost.
weight	number	no	Shipping weight.
stock	integer	no	Units available.
manufacturer_sku	string	no	—
location	string	no	Warehouse or fulfillment method.
variation_list	object	no	—
metadata	object	no	—

WRITE: change fields of an inventory item, for example its stock count. Order Desk's PUT replaces the whole record, so this reads the item, applies only the fields you pass (metadata and variation keys are merged) and sends the complete record back. PUT /inventory-items/{inventory_item_id}.

Parameter	Type	Required	Notes
inventory_item_id	integer	yes	Order Desk's internal inventory item id.
name	string	no	—
code	string	no	SKU.
price	number	no	—
cost	number	no	—
weight	number	no	—
stock	integer	no	The new units-available count (replaces the old one).
manufacturer_sku	string	no	—
location	string	no	—
variation_list	object	no	Variation keys to set (others are kept).
metadata	object	no	Metadata keys to set (others are kept).

Free

$0 forever

Every tool — any call limit is its publisher’s, not ours
No card, and mcprush charges nothing for it
Runs at its publisher’s own address — this marketplace is not in the path
Nothing to cap, because mcprush bills nothing

Nothing here is billable: mcprush charges nothing to install Order Desk MCP by usefulapi or to call it, at any volume.

ATool-list grade · score 93 / 100

Release 1.20.2 · scanned 7 Nov 2026

Graded from the tools this server lists, not from its source code.

Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.

Threat score100

Client score93

Findings0 threat · 2 capability

Capabilitymoderate

Coveragemanifest

Verificationnot in this report

Surface digestc60c17f07c6d091d7d06aeb59063f28ca7db1430e83d80429006fe0c277b15cb

Score vectorthreat 100 → client 93

Term	Level	What it prices	Points
capability-exposure	moderate	capability blast radius (moderate) — client exposure if the model is manipulated	−3
coverage-honesty	manifest	inspection depth (manifest) — how much of the target the scan could see	−4

score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.

What the scan could actually read

A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.

The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.

Tool surfaceread

Implementation sourcenot available

Package metadatanot available

Live transportnot available

The implementation source was not read — this reflects the declared tool metadata only.

Capability — what it could do if the model were manipulated

Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.

Tool	Capability tags	Why the tag was assigned
orderdesk_get_store	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
orderdesk_list_orders	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
orderdesk_get_order	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
orderdesk_list_order_items	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
orderdesk_list_order_shipments	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
orderdesk_create_order	external-sink	external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true
orderdesk_update_order	external-sink	external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true
orderdesk_add_order_item	external-sink	external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true
orderdesk_add_order_note	external-sink	external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true
orderdesk_add_shipment	external-sink	external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true
orderdesk_move_orders	external-sink	external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true
orderdesk_list_inventory_items	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
orderdesk_get_inventory_item	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
orderdesk_create_inventory_item	external-sink	external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true
orderdesk_update_inventory_item	external-sink	external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true

Toxic-flow graph

The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.

flow-1

Untrusted input can drive an external action even though no sensitive source is exposed.

Supply chain and provenance

Integrityfirst-seen

Surface digestc60c17f07c6d091d

Scanned2026-11-07

This is the first scan of this surface here, so there is nothing yet to compare it against.

Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.

Where are you running it?

Tool surface

Release history

Order Desk MCP by usefulapi

What it does

Quickstart

Where are you running it?

Tool surface

What counts against your monthly calls

What the scan could actually read

Capability — what it could do if the model were manipulated

Toxic-flow graph

Supply chain and provenance

Release history

See also