Ordoro MCP by usefulapi
REMOTE · ORDORO.USEFULAPI.IO
Read Ordoro orders, products, shipments, suppliers and purchase orders; tag and comment on orders.
Available components
Last scanned (1 hour ago)
Scores higher than 47% of remote servers
Reachable. Last reached 17 Oct 2026.
Category E-commerce
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 Usability81
- 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 2513 tokens (~139/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 Management23
- Stability observed for 7 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.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.
- 15 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.4.0 → 1.5.0 functional
- 12 Oct 26 +1
- Stability: unverified → 0.07 ▲ functional
- 10 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://ordoro.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 ordoro.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://ordoro.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://ordoro.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://ordoro.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://ordoro.usefulapi.io/mcp |
| Authorisation server | https://ordoro.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ordoro.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/ordoro/ |
| http (plaintext) | http://ordoro.usefulapi.io/mcp | Inconclusive | 302 | http://ordoro.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 →
ordoro_add_order_comment Add a comment to an order ~100
WRITE: add an internal comment to an order (visible to the team in Ordoro, not sent to the customer). Each call adds a new comment. Ordoro API: POST /v3/order/{order_number}/comment.
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | yes | The comment text. |
| order_number | string | yes | The Ordoro order number, including its sales-channel prefix (for example "1-1001"), from ordoro_list_orders. |
No output schema declared.
No examples provided.
ordoro_add_order_tag Tag an order ~119
WRITE: apply an existing order tag (by id, from ordoro_list_order_tags) to an order, for example to put it on hold or route it. Returns the order's tags. Ordoro API: POST /v3/order/{order_number}/tag/{tag_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| order_number | string | yes | The Ordoro order number, including its sales-channel prefix (for example "1-1001"), from ordoro_list_orders. |
| tag_id | integer | yes | The tag id (from ordoro_list_order_tags). |
No output schema declared.
No examples provided.
ordoro_get_order Get an order ~104
Get one order by order number: status, lines (SKU, quantity, price), shipping/billing address, warehouse, shipping_info (carrier, tracking number, ship date, cost), comments, tags, financials and dropship info. Ordoro API: GET /v3/order/{order_number}.
| Name | Type | Req | Description |
|---|---|---|---|
| order_number | string | yes | The Ordoro order number, including its sales-channel prefix (for example "1-1001"), from ordoro_list_orders. |
No output schema declared.
No examples provided.
ordoro_get_order_counts Get order counts by status ~56
Count orders per status: all, awaiting_fulfillment, shipped, unprinted_shipped, cancelled, dropshipment_requested. A quick fulfillment-backlog overview. Ordoro API: GET /v3/order/counts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ordoro_get_order_tracking Get an order's shipment tracking ~100
Get the shipment and tracking details of one order: carrier, shipping method, tracking number and tracking URL, ship date, estimated delivery, label cost, plus any return shipment and dropship info. Ordoro API: GET /v3/order/{order_number} (shipping_info).
| Name | Type | Req | Description |
|---|---|---|---|
| order_number | string | yes | The Ordoro order number, including its sales-channel prefix (for example "1-1001"), from ordoro_list_orders. |
No output schema declared.
No examples provided.
ordoro_get_product Get a product with stock per warehouse ~70
Get one product by SKU: price, cost, weight and dimensions, inventory totals, stock per warehouse (on hand, available, committed, location), suppliers, kit components and sales-channel links. Ordoro API: GET /product/{sku}/.
| Name | Type | Req | Description |
|---|---|---|---|
| sku | string | yes | The product SKU. |
No output schema declared.
No examples provided.
ordoro_get_purchase_order Get a purchase order ~79
Get one purchase order by its PO id: supplier, warehouse, status, lines (SKU, quantity ordered/received, unit price), shipping/payment method and dates. Ordoro API: GET /purchase_order/{po_id}/.
| Name | Type | Req | Description |
|---|---|---|---|
| po_id | string | yes | The purchase order id (po_id, from ordoro_list_purchase_orders). |
No output schema declared.
No examples provided.
ordoro_get_supplier Get a supplier ~58
Get one supplier by id, with address, contact details and dropship/PO settings. Ordoro API: GET /supplier/{supplier_id}/.
| Name | Type | Req | Description |
|---|---|---|---|
| supplier_id | integer | yes | The supplier id (from ordoro_list_suppliers). |
No output schema declared.
No examples provided.
ordoro_list_order_comments List an order's comments ~136
List the comments (internal notes and the order's activity log) of one order, with user and date. Paginated: returns { count, limit, offset, comment: [...] }; use offset for the next page. Ordoro API: GET /v3/order/{order_number}/comment.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results per page (default 10, max 100). |
| offset | integer | – | Number of results to skip (pagination). |
| order_number | string | yes | The Ordoro order number, including its sales-channel prefix (for example "1-1001"), from ordoro_list_orders. |
No output schema declared.
No examples provided.
ordoro_list_order_tags List order tags ~84
List the account's order tags (id, name, color). Use the id with ordoro_add_order_tag / ordoro_remove_order_tag. Ordoro API: GET /v3/order/tag.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results per page (default 10, max 100). |
| offset | integer | – | Number of results to skip (pagination). |
No output schema declared.
No examples provided.
ordoro_list_orders List orders ~349
List orders across all sales channels, newest first by default. Filter by status (awaiting_fulfillment, shipped, cancelled, dropshipment_requested, all), free-text search, SKU, tag, warehouse, and created/updated/shipped date ranges. Returns { count, limit, offset, order: [...] } with lines, addresses, shipping_info (tracking), tags and financials. Ordoro API: GET /v3/order.
| Name | Type | Req | Description |
|---|---|---|---|
| allocation_status | string | – | Inventory allocation status filter. |
| created_after | string | – | Created on/after this date (ISO 8601, e.g. 2026-10-01). |
| created_before | string | – | Created before this date (ISO 8601). |
| limit | integer | – | Max results per page (default 10, max 100). |
| offset | integer | – | Number of results to skip (pagination). |
| sales_channel | array | – | Only orders from these sales channel (cart) ids. |
| search | string | – | Free-text search. |
| shipped_after | string | – | Shipped on/after this date (ISO 8601). |
| shipped_before | string | – | Shipped before this date (ISO 8601). |
| sku | array | – | Only orders containing these SKUs. |
| sort | string | – | Sort field; prefix '-' for descending. |
| status | string | – | Order status filter (default: Ordoro's default view). |
| tag | array | – | Only orders with these tag names. |
| updated_after | string | – | Updated on/after this date (ISO 8601). |
| warehouse_id | array | – | Only orders assigned to these warehouse ids. |
No output schema declared.
No examples provided.
ordoro_list_products List products and inventory ~337
List products with inventory totals (total_on_hand, available_on_hand, total_committed, total_allocated, to_be_shipped, po_total_committed). Filter by search, active, low inventory, oversold, needs_sync, warehouse, supplier, tag, kit status and updated date. Returns { count, limit, offset, products: [...] }. Ordoro API: GET /product/.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | – | true = active products only, false = archived only. |
| category | string | – | Product category. |
| dropship | boolean | – | true = only dropshippable products. |
| kit | boolean | – | true = only kit parents. |
| limit | integer | – | Max results per page (default 10, max 100). |
| low_inventory_aoh | boolean | – | true = only products low on available-on-hand inventory. |
| needs_sync | boolean | – | true = only products whose inventory needs syncing to a sales channel. |
| offset | integer | – | Number of results to skip (pagination). |
| oversold | boolean | – | true = only oversold products. |
| search | string | – | Search by SKU or name. |
| sort | string | – | Sort field; prefix '-' for descending. |
| supplier | array | – | Only products from these supplier ids. |
| tag | array | – | Only products with these tag names. |
| to_be_shipped | boolean | – | true = only products with committed (to-be-shipped) inventory. |
| updated_after | string | – | Updated after this date (ISO 8601). |
| warehouse_id | array | – | Only products stocked in these warehouse ids. |
No output schema declared.
No examples provided.
ordoro_list_purchase_orders List purchase orders ~189
List purchase orders to suppliers with status (unsent, sent, partial, received, cancelled), supplier, lines and expected delivery. Filter by status, SKU, tag, search and updated date. Ordoro API: GET /purchase_order/.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results per page (default 10, max 100). |
| offset | integer | – | Number of results to skip (pagination). |
| search | string | – | Free-text search. |
| sku | array | – | Only POs containing these SKUs. |
| sort | string | – | Sort field; prefix '-' for descending. |
| status | string | – | Purchase order status filter. |
| tag | array | – | Only POs with these tag names. |
| updated_after | string | – | Updated after this date (ISO 8601). |
| updated_before | string | – | Updated before this date (ISO 8601). |
No output schema declared.
No examples provided.
ordoro_list_return_orders List return orders (RMAs) ~136
List return orders (RMAs) with reference id, status, original order, lines and return label info. Ordoro API: GET /v3/return_order.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results per page (default 10, max 100). |
| offset | integer | – | Number of results to skip (pagination). |
| search | string | – | Free-text search. |
| sort | string | – | Sort: (-)reference_id, (-)status, (-)warehouse_name, (-)created_date, (-)updated_date. |
| status | string | – | Return order status filter (e.g. all). |
No output schema declared.
No examples provided.
ordoro_list_shippers List shipping carrier accounts ~130
List the carrier accounts (shippers) connected to Ordoro: UPS, FedEx, USPS (Endicia/Pitney), DHL, Canada Post, Australia Post, Amazon, Sendle. Returns id, name, vendor, archive/created/updated dates and hidden shipping methods only (carrier credentials are never returned). Ordoro API: GET /shipper/.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | true = include archived carrier accounts. |
| limit | integer | – | Max results per page (default 10, max 100). |
| offset | integer | – | Number of results to skip (pagination). |
No output schema declared.
No examples provided.
ordoro_list_suppliers List suppliers ~83
List suppliers and dropshippers with id, company name, address, contact email and dropship settings. Ordoro API: GET /supplier/.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results per page (default 10, max 100). |
| offset | integer | – | Number of results to skip (pagination). |
| search | string | – | Free-text search. |
No output schema declared.
No examples provided.
ordoro_list_warehouses List warehouses ~83
List warehouses (ship-from locations) with id, name, address and whether each is the default. Ordoro API: GET /warehouse/.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results per page (default 10, max 100). |
| offset | integer | – | Number of results to skip (pagination). |
| search | string | – | Free-text search. |
No output schema declared.
No examples provided.
ordoro_remove_order_tag Remove a tag from an order ~99
WRITE: remove a tag (by id) from an order. The tag itself stays defined. Ordoro API: DELETE /v3/order/{order_number}/tag/{tag_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| order_number | string | yes | The Ordoro order number, including its sales-channel prefix (for example "1-1001"), from ordoro_list_orders. |
| tag_id | integer | yes | The tag id (from ordoro_list_order_tags). |
No output schema declared.
No examples provided.
How do I install the Ordoro MCP by usefulapi server?
Ordoro MCP by usefulapi is a hosted endpoint at https://ordoro.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 · ordoro.usefulapi.io
claude mcp add --transport http io-usefulapi-ordoro 'https://ordoro.usefulapi.io/mcp'
What is the Ordoro MCP by usefulapi server?
Ordoro MCP by usefulapi is listed in the public MCP registry as io.usefulapi/ordoro. Read Ordoro orders, products, shipments, suppliers and purchase orders; tag and comment on orders. This page covers its hosted endpoint (https://ordoro.usefulapi.io/mcp).
Is the Ordoro MCP by usefulapi server safe to use?
Ordoro 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 Ordoro MCP by usefulapi server expose?
Ordoro MCP by usefulapi exposes 18 tools: ordoro_list_orders, ordoro_get_order, ordoro_get_order_counts, ordoro_get_order_tracking, ordoro_list_order_comments, and 13 more. Their descriptions and schemas cost roughly 2,312 tokens of context every time the server is loaded.
Does the Ordoro MCP by usefulapi server require authentication?
Yes. Ordoro 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 Ordoro MCP by usefulapi server still maintained?
Ordoro 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.