Shipday MCP by usefulapi
REMOTE · SHIPDAY.USEFULAPI.IO
Read Shipday orders, carriers and delivery status; create orders and assign drivers.
Available components
Last scanned (23 hours ago)
Scores higher than 47% of remote servers
Reachable. Last reached 16 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 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 1817 tokens (~129/item across 14 items; 14 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 Management20
- Stability observed for 6 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 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 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.
- 13 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 16 Oct 2026 · Probed https://shipday.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 shipday.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://shipday.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://shipday.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://shipday.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://shipday.usefulapi.io/mcp |
| Authorisation server | https://shipday.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://shipday.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/shipday/ |
| http (plaintext) | http://shipday.usefulapi.io/mcp | Inconclusive | 302 | http://shipday.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 →
assign_order_to_carrier Assign an order to a driver ~110
WRITE: assign a delivery order to one of the account's own carriers (drivers); the driver is notified in the Shipday driver app. Re-assigning to the same driver changes nothing. Shipday: PUT /orders/assign/{orderId}/{carrierId}.
| Name | Type | Req | Description |
|---|---|---|---|
| carrier_id | integer | yes | Numeric carrier (driver) id from list_carriers. |
| order_id | integer | yes | Shipday's internal numeric order id (the `orderId` field, not the order number). |
No output schema declared.
No examples provided.
check_on_demand_availability Check on-demand delivery availability ~115
Quote third-party on-demand delivery for a pickup and delivery address before creating an order: which services can deliver, their fee and pickup/delivery times. Read only: nothing is booked. Shipday: POST /on-demand/availability.
| Name | Type | Req | Description |
|---|---|---|---|
| delivery_address | string | yes | Full delivery address. |
| delivery_time | string | – | Expected delivery time, ISO 8601 UTC. |
| pickup_address | string | yes | Full pickup address. |
| pickup_time | string | – | Expected pickup time, ISO 8601 UTC. |
No output schema declared.
No examples provided.
create_order Create a delivery order ~384
WRITE: insert a new delivery order into Shipday (it appears on the dispatch board; it is not assigned to a driver). Returns the new orderId. Times are UTC. Shipday: POST /orders.
| Name | Type | Req | Description |
|---|---|---|---|
| additional_id | string | – | An extra reference id. |
| customer_address | string | yes | Delivery address. |
| customer_email | string | – | Customer email. |
| customer_name | string | yes | Customer name. |
| customer_phone_number | string | yes | Customer phone number with country code, e.g. +14155550100. |
| delivery_fee | number | – | Delivery fee. |
| delivery_instruction | string | – | Instructions for the driver at delivery. |
| delivery_latitude | number | – | Delivery latitude. |
| delivery_longitude | number | – | Delivery longitude. |
| discount_amount | number | – | Discount amount. |
| expected_delivery_date | string | – | Expected delivery date, yyyy-mm-dd (UTC). |
| expected_delivery_time | string | – | Expected delivery time, hh:mm:ss (UTC). |
| expected_pickup_time | string | – | Expected pickup time, hh:mm:ss (UTC). |
| order_items | array | – | Items in the order. |
| order_number | string | yes | Your reference for the order (orderNumber). |
| order_source | string | – | Where the order came from (free text). |
| payment_method | string | – | Payment method. |
| pickup_instruction | string | – | Instructions for the pickup. |
| pickup_latitude | number | – | Pickup latitude. |
| pickup_longitude | number | – | Pickup longitude. |
| restaurant_address | string | yes | Pickup address. |
| restaurant_name | string | yes | Pickup location / store name. |
| restaurant_phone_number | string | – | Pickup location phone with country code. |
| tax | number | – | Tax amount. |
| tips | number | – | Tip amount. |
| total_order_cost | number | – | Total order cost. |
No output schema declared.
No examples provided.
get_delivery_progress Get delivery progress and ETA ~131
Real-time delivery progress of an order by its tracking id: status (STARTED, PICKED_UP, ...), timestamps, the driver's current location and the ETA in minutes. The tracking id is the last part of the order's trackingLink. Shipday's Business Advanced plan only; at most 3 requests per minute per tracking id. Shipday: GET /order/progress/{trackingId}.
| Name | Type | Req | Description |
|---|---|---|---|
| include_static_data | boolean | – | true = also return fixed details (customer, restaurant, carrier). Default false. |
| tracking_id | string | yes | The order's tracking id (from its trackingLink). |
No output schema declared.
No examples provided.
get_on_demand_details Get on-demand delivery details ~84
Details of the third-party on-demand delivery booked for an order: provider, reference id, third-party fee, Shipday charge, total billable amount and tracking URL. Shipday: GET /on-demand/details/{orderId}.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | integer | yes | Shipday's internal numeric order id (the `orderId` field, not the order number). |
No output schema declared.
No examples provided.
get_on_demand_estimate Get on-demand delivery estimates ~90
Get fee and time estimates from the third-party on-demand delivery services for an existing order (fee, pickup/delivery time, durations, per-service errors). Read only: nothing is booked. Shipday: GET /on-demand/estimate/{orderId}.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | integer | yes | Shipday's internal numeric order id (the `orderId` field, not the order number). |
No output schema declared.
No examples provided.
get_order Get order by order number ~96
Get the details of a delivery order by its order number (the merchant's reference, `orderNumber`). Returns an array, since several orders can share one order number. Includes the numeric orderId needed by the write tools, the carrier, tracking link and status. Shipday: GET /orders/{orderNumber}.
| Name | Type | Req | Description |
|---|---|---|---|
| order_number | string | yes | The order number (orderNumber) of the order, e.g. "75637". |
No output schema declared.
No examples provided.
get_pickup_order Get a pickup order ~65
Get a pickup (customer collects it) order by its numeric id, with restaurant, customer, items, costs, expected pickup date/time and status. Shipday: GET /pickup-orders/{orderId}.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | integer | yes | Numeric id of the pickup order. |
No output schema declared.
No examples provided.
list_active_orders List active orders ~60
List the account's active (not yet completed) delivery orders with customer, pickup location (restaurant), assigned carrier/driver, timeline (activityLog), costs, payment method and orderStatus.orderState. Good first call. Shipday: GET /orders.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_carriers List carriers (drivers) ~56
List the account's carriers (drivers) with id, name, phone, email, isOnShift, isActive and last known location. Use an id here with assign_order_to_carrier. Shipday: GET /carriers.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_on_demand_services List on-demand delivery services ~45
List the third-party on-demand delivery services (DoorDash, Uber, ...) available to the account and whether each is enabled. Shipday: GET /on-demand/services.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
query_orders Search orders (history) ~214
Search delivery orders, including completed ones, by placement-time window and status, with row-based paging: start_cursor/end_cursor select rows (e.g. 1–100, then 101–200; at most 100 per call) sorted newest first. Each row has timestamps (placement, assigned, picked up, delivered, failed), totals, driver payment, distance and carrier. Shipday: POST /orders/query.
| Name | Type | Req | Description |
|---|---|---|---|
| end_cursor | integer | – | Last row to return (default start_cursor + 99). At most 100 rows per call. |
| end_time | string | – | Only orders placed at/before this ISO 8601 time (UTC). |
| order_status | string | – | Only orders in this status. |
| start_cursor | integer | – | First row to return (1-based, default 1). |
| start_time | string | – | Only orders placed at/after this ISO 8601 time (UTC), e.g. 2026-10-01T00:00:00Z. |
No output schema declared.
No examples provided.
set_order_ready_to_pickup Mark an order ready for pickup ~99
WRITE: set or clear an order's ready-to-pickup flag (tells the driver the order is ready at the pickup location). Shipday: PUT /orders/{orderId}/meta.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | integer | yes | Shipday's internal numeric order id (the `orderId` field, not the order number). |
| ready_to_pickup | boolean | – | true = ready (default), false = not ready. |
No output schema declared.
No examples provided.
unassign_order Unassign an order from its driver ~65
WRITE: remove the driver from a delivery order (it goes back to unassigned). Shipday: PUT /orders/unassign/{orderId}.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | integer | yes | Shipday's internal numeric order id (the `orderId` field, not the order number). |
No output schema declared.
No examples provided.
How do I install the Shipday MCP by usefulapi server?
Shipday MCP by usefulapi is a hosted endpoint at https://shipday.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 · shipday.usefulapi.io
claude mcp add --transport http io-usefulapi-shipday 'https://shipday.usefulapi.io/mcp'
What is the Shipday MCP by usefulapi server?
Shipday MCP by usefulapi is listed in the public MCP registry as io.usefulapi/shipday. Read Shipday orders, carriers and delivery status; create orders and assign drivers. This page covers its hosted endpoint (https://shipday.usefulapi.io/mcp).
Is the Shipday MCP by usefulapi server safe to use?
Shipday 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 Shipday MCP by usefulapi server expose?
Shipday MCP by usefulapi exposes 14 tools: list_active_orders, get_order, query_orders, get_pickup_order, get_delivery_progress, and 9 more. Their descriptions and schemas cost roughly 1,614 tokens of context every time the server is loaded.
Does the Shipday MCP by usefulapi server require authentication?
Yes. Shipday 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 Shipday MCP by usefulapi server still maintained?
Shipday MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.