# Shipday MCP by usefulapi (remote · shipday.usefulapi.io)

Read Shipday orders, carriers and delivery status; create orders and assign drivers.

- Trust score: 66/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `shipday.usefulapi.io`: 66/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-shipday/shipday.md), [page](https://verifymcp.io/servers/io-usefulapi-shipday/shipday)

## Channel facts

- Endpoint: `https://shipday.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.2.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-17.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 83/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http io-usefulapi-shipday 'https://shipday.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-shipday": {
      "url": "https://shipday.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-shipday": {
      "type": "http",
      "url": "https://shipday.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-shipday]
url = "https://shipday.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-shipday": {
      "type": "remote",
      "url": "https://shipday.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-shipday --url 'https://shipday.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-shipday:
    url: "https://shipday.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-shipday": {
      "Transport": "http",
      "Url": "https://shipday.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-shipday -t streamable-http -u 'https://shipday.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-shipday": {
      "type": "http",
      "url": "https://shipday.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-17 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-15 (score 65, +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.

### 2026-10-13 (score 64, +2)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] 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

### 2026-10-12 (score 62, +1)

- [functional improvement] Stability: unverified → 0.07

### 2026-10-10 (score 61)

First indexed and scored.

## MCP tools (14)

### `list_active_orders` (~60 tokens)

List active orders

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.

### `get_order` (~96 tokens)

Get order by order number

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}.

Input parameters:

- `order_number` (string, required): The order number (orderNumber) of the order, e.g. "75637".

### `query_orders` (~214 tokens)

Search orders (history)

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.

Input parameters:

- `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.

### `get_pickup_order` (~65 tokens)

Get a pickup order

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}.

Input parameters:

- `order_id` (integer, required): Numeric id of the pickup order.

### `get_delivery_progress` (~131 tokens)

Get delivery progress and ETA

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}.

Input parameters:

- `include_static_data` (boolean): true = also return fixed details (customer, restaurant, carrier). Default false.
- `tracking_id` (string, required): The order's tracking id (from its trackingLink).

### `list_carriers` (~56 tokens)

List carriers (drivers)

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.

### `list_on_demand_services` (~45 tokens)

List on-demand delivery services

List the third-party on-demand delivery services (DoorDash, Uber, ...) available to the account and whether each is enabled. Shipday: GET /on-demand/services.

### `get_on_demand_estimate` (~90 tokens)

Get on-demand delivery estimates

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}.

Input parameters:

- `order_id` (integer, required): Shipday's internal numeric order id (the `orderId` field, not the order number).

### `get_on_demand_details` (~84 tokens)

Get on-demand delivery details

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}.

Input parameters:

- `order_id` (integer, required): Shipday's internal numeric order id (the `orderId` field, not the order number).

### `check_on_demand_availability` (~115 tokens)

Check on-demand delivery availability

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.

Input parameters:

- `delivery_address` (string, required): Full delivery address.
- `delivery_time` (string): Expected delivery time, ISO 8601 UTC.
- `pickup_address` (string, required): Full pickup address.
- `pickup_time` (string): Expected pickup time, ISO 8601 UTC.

### `create_order` (~384 tokens)

Create a delivery order

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.

Input parameters:

- `additional_id` (string): An extra reference id.
- `customer_address` (string, required): Delivery address.
- `customer_email` (string): Customer email.
- `customer_name` (string, required): Customer name.
- `customer_phone_number` (string, required): 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, required): 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, required): Pickup address.
- `restaurant_name` (string, required): 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.

### `assign_order_to_carrier` (~110 tokens)

Assign an order to a driver

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}.

Input parameters:

- `carrier_id` (integer, required): Numeric carrier (driver) id from list_carriers.
- `order_id` (integer, required): Shipday's internal numeric order id (the `orderId` field, not the order number).

### `unassign_order` (~65 tokens)

Unassign an order from its driver

WRITE: remove the driver from a delivery order (it goes back to unassigned). Shipday: PUT /orders/unassign/{orderId}.

Input parameters:

- `order_id` (integer, required): Shipday's internal numeric order id (the `orderId` field, not the order number).

### `set_order_ready_to_pickup` (~99 tokens)

Mark an order ready for pickup

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.

Input parameters:

- `order_id` (integer, required): Shipday's internal numeric order id (the `orderId` field, not the order number).
- `ready_to_pickup` (boolean): true = ready (default), false = not ready.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-shipday/shipday#diagnostics

## Score history

- 2026-10-17: 66
- 2026-10-16: 65
- 2026-10-15: 65
- 2026-10-14: 64
- 2026-10-13: 64
- 2026-10-12: 62
- 2026-10-10: 61

## Common questions

### 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 66 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 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://shipday.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/shipday/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-shipday/shipday.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-shipday/shipday.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-shipday/shipday