Skip to content

Shipday MCP by usefulapi

io.usefulapi/shipdayusefulapi.iostreamable-httpv1.33.4Scanned

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

14 tools: 1 can delete or cancel things, 4 change things and 9 only read.

Tools: 1 delete, 0 irreversible, 4 write, 9 read.
  • Reads private data · 1
  • Reads text others write · 2
  • Can send data out · 0
  • No findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

5 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Shipday MCP by usefulapi can do

The Shipday MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 14 tools. It can delete or cancel things (1 tool: shipday_create_order) and create or change data (4 tools: shipday_check_on_demand_availability, shipday_assign_order_to_carrier, shipday_unassign_order and shipday_set_order_ready_to_pickup). 9 tools only read.

1 tool reads private data (shipday_list_carriers); 2 tools bring in text other people can write (shipday_list_carriers and shipday_get_on_demand_details).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its tools changed once since Anlyon Radar first saw them.

Last scanned Oct 25, 2026, version 1.33.4.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

14 tools

Deletes or cancels 1Claude Code: deny
  • shipday_create_orderWRITE: insert a new delivery order into Shipday (it appears on the dispatch board; it is not assigned to a driver).No findings

    Why it is in this group

    • The name "shipday_create_order" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Create a delivery order
    • readOnlyHint: false
    • destructiveHint: true
Changes things 4Claude Code: ask
  • shipday_assign_order_to_carrierWRITE: assign a delivery order to one of the account's own carriers (drivers); the driver is notified in the Shipday driver app.No findings

    Why it is in this group

    • The name "shipday_assign_order_to_carrier" says "assign": a word for a change.
    Description, as the server wrote it
    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}.

    Annotations the server declares

    • title: Assign an order to a driver
    • readOnlyHint: false
    • idempotentHint: true
  • shipday_check_on_demand_availabilityQuote 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.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check on-demand delivery availability
    • readOnlyHint: true
  • shipday_set_order_ready_to_pickupWRITE: set or clear an order's ready-to-pickup flag (tells the driver the order is ready at the pickup location).No findings

    Why it is in this group

    • The name "shipday_set_order_ready_to_pickup" says "set": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Mark an order ready for pickup
    • readOnlyHint: false
    • idempotentHint: true
  • shipday_unassign_orderWRITE: remove the driver from a delivery order (it goes back to unassigned).No findings

    Why it is in this group

    • The name "shipday_unassign_order" says "unassign": a word for a change.
    Description, as the server wrote it
    WRITE: remove the driver from a delivery order (it goes back to unassigned). Shipday: PUT /orders/unassign/{orderId}.

    Annotations the server declares

    • title: Unassign an order from its driver
    • readOnlyHint: false
    • idempotentHint: true
Only reads 9Show 9 read-only tools
  • shipday_get_delivery_progressReal-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.No findings

    Why it is in this group

    • The name "shipday_get_delivery_progress" says "get": a word for reading.
    Description, as the server wrote it
    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}.

    Annotations the server declares

    • title: Get delivery progress and ETA
    • readOnlyHint: true
  • shipday_get_on_demand_detailsDetails 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.Reads text others writeNo findings

    Why it is in this group

    • The name "shipday_get_on_demand_details" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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}.

    Annotations the server declares

    • title: Get on-demand delivery details
    • readOnlyHint: true
  • shipday_get_on_demand_estimateGet fee and time estimates from the third-party on-demand delivery services for an existing order (fee, pickup/delivery time, durations, per-service errors).No findings

    Why it is in this group

    • The name "shipday_get_on_demand_estimate" says "get": a word for reading.
    Description, as the server wrote it
    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}.

    Annotations the server declares

    • title: Get on-demand delivery estimates
    • readOnlyHint: true
  • shipday_get_orderGet the details of a delivery order by its order number (the merchant's reference, `orderNumber`).No findings

    Why it is in this group

    • The name "shipday_get_order" says "get": a word for reading.
    Description, as the server wrote it
    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}.

    Annotations the server declares

    • title: Get order by order number
    • readOnlyHint: true
  • shipday_get_pickup_orderGet a pickup (customer collects it) order by its numeric id, with restaurant, customer, items, costs, expected pickup date/time and status.No findings

    Why it is in this group

    • The name "shipday_get_pickup_order" says "get": a word for reading.
    Description, as the server wrote it
    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}.

    Annotations the server declares

    • title: Get a pickup order
    • readOnlyHint: true
  • shipday_list_active_ordersList the account's active (not yet completed) delivery orders with customer, pickup location (restaurant), assigned carrier/driver, timeline (activityLog), costs, payment method an…No findings

    Why it is in this group

    • The name "shipday_list_active_orders" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List active orders
    • readOnlyHint: true
  • shipday_list_carriersList the account's carriers (drivers) with id, name, phone, email, isOnShift, isActive and last known location.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "shipday_list_carriers" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "email": it reads mail.
    • untrusted-inputThe description's first sentence says "list" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    List the account's carriers (drivers) with id, name, phone, email, isOnShift, isActive and last known location. Use an id here with shipday_assign_order_to_carrier. Shipday: GET /carriers.

    Annotations the server declares

    • title: List carriers (drivers)
    • readOnlyHint: true
  • shipday_list_on_demand_servicesList the third-party on-demand delivery services (DoorDash, Uber, ...) available to the account and whether each is enabled.No findings

    Why it is in this group

    • The name "shipday_list_on_demand_services" says "list": a word for reading.
    Description, as the server wrote it
    List the third-party on-demand delivery services (DoorDash, Uber, ...) available to the account and whether each is enabled. Shipday: GET /on-demand/services.

    Annotations the server declares

    • title: List on-demand delivery services
    • readOnlyHint: true
  • shipday_query_ordersSearch delivery orders, including completed ones, by placement-time window and status, with row-based paging: start_cursor/end_cursor select rows (e.g.No findings

    Why it is in this group

    • The name "shipday_query_orders" says "query": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Search orders (history)
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:37 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 5 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://shipday.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://shipday.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 5 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://shipday.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://shipday.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed
  2. Tools14 added, 14 removed.+14 added−14 removedView diff

Install

Pinned to version 1.33.4. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__shipday__shipday_list_active_orders",
      "mcp__shipday__shipday_get_order",
      "mcp__shipday__shipday_query_orders",
      "mcp__shipday__shipday_get_pickup_order",
      "mcp__shipday__shipday_get_delivery_progress",
      "mcp__shipday__shipday_list_carriers",
      "mcp__shipday__shipday_list_on_demand_services",
      "mcp__shipday__shipday_get_on_demand_estimate",
      "mcp__shipday__shipday_get_on_demand_details"
    ],
    "ask": [
      "mcp__shipday__shipday_check_on_demand_availability",
      "mcp__shipday__shipday_assign_order_to_carrier",
      "mcp__shipday__shipday_unassign_order",
      "mcp__shipday__shipday_set_order_ready_to_pickup"
    ],
    "deny": [
      "mcp__shipday__shipday_create_order"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as shipday. Review it before you use it.

Capability tags behind 2 rules
  • mcp__shipday__shipday_list_carriers private-data, untrusted-input
  • mcp__shipday__shipday_get_on_demand_details untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/shipday/verify?hash=6955682e5f013bad23f9a2feeffaca847f668a95ba97afbda511be5282136ade" | jq -e '.changed == false'

Pinned hash 6955682e5f01, from Oct 25, 2026, 23:19 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.usefulapi/shipday/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.usefulapi/shipday
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/shipday.svg)](https://radar.anlyon.com/servers/io.usefulapi/shipday)

Source: MCP Registry · repository. Synced Nov 18, 2026, 11:19 UTC.

Shipday MCP by usefulapi: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Shipday MCP by usefulapi safe?

No scan can promise that. What its definitions show: 14 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Shipday MCP by usefulapi delete data?

Yes. 1 tool can delete, cancel or revoke something: shipday_create_order.

Can the Shipday MCP by usefulapi do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Shipday MCP by usefulapi have?

14 tools: 1 destructive, 4 write, 9 read. shipday_create_order, shipday_check_on_demand_availability, shipday_assign_order_to_carrier, shipday_unassign_order, shipday_set_order_ready_to_pickup, shipday_list_active_orders, shipday_get_order, shipday_query_orders and 6 more.

Does the Shipday MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Shipday MCP by usefulapi send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Shipday MCP by usefulapi changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Oct 23, 2026. Every change is on this page and in its Atom feed.