# Stuart MCP by usefulapi (remote · stuart.usefulapi.io)

Quote, validate, book and track Stuart courier deliveries; cancel jobs and check zone coverage.

- Trust score: 62/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-25

## Components

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

## Channel facts

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

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

- **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**: 81/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1880 tokens (~125/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 91% 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 15 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 16 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 Stuart MCP by usefulapi server?

Stuart MCP by usefulapi is a hosted endpoint at https://stuart.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-stuart 'https://stuart.usefulapi.io/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-stuart": {
      "type": "http",
      "url": "https://stuart.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-25 (score 62, 0)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.0.0 → 1.0.3

### 2026-10-24 (score 62)

First indexed and scored.

## MCP tools (15)

### `stuart_list_jobs` (~149 tokens)

List delivery jobs

List the delivery jobs of the last 90 days, newest pickup first, with status, deliveries (tracking URLs, courier proof), driver and pricing. Filter by status, active or your client_reference. Paginated: when a page returns per_page rows, ask for the next page. Stuart: GET /v2/jobs.

Input parameters:

- `active` (boolean): true = only jobs still in progress.
- `client_reference` (string): Your own order reference.
- `page` (integer): Page number (default 1).
- `per_page` (integer): Rows per page (default 25).
- `status` (string): Job status filter, e.g. in_progress, finished, canceled.

### `stuart_get_job` (~64 tokens)

Get a delivery job

One job in full: status, each delivery with tracking URL, pickup/dropoff addresses and contacts, ETA, cancellation, proof of delivery, driver, distance and pricing. Stuart: GET /v2/jobs/{jobId}.

Input parameters:

- `job_id` (required): Stuart job id.

### `stuart_estimate_price` (~107 tokens)

Get a delivery price quote

Price of a job before you create it: amount excluding and including tax, and currency. Nothing is booked. Needs pickup address, dropoff address and package type. Stuart: POST /v2/jobs/pricing.

Input parameters:

- `dropoffs` (array, required): 1 to 8 dropoff points.
- `pickup` (object, required): The single pickup point.
- `pickup_at` (string): ISO 8601 time the courier should arrive at the pickup. Omit to dispatch immediately.

### `stuart_validate_job` (~100 tokens)

Validate a delivery job

Check that a job would be accepted (addresses geocode inside a covered zone, fields valid) without creating it. Returns {valid}. Stuart: POST /v2/jobs/validate.

Input parameters:

- `dropoffs` (array, required): 1 to 8 dropoff points.
- `pickup` (object, required): The single pickup point.
- `pickup_at` (string): ISO 8601 time the courier should arrive at the pickup. Omit to dispatch immediately.

### `stuart_estimate_pickup_eta` (~100 tokens)

Estimate courier arrival at pickup

Estimated seconds until a courier could arrive at the pickup address, for the same job body as create. Nothing is booked. Stuart: POST /v2/jobs/eta.

Input parameters:

- `dropoffs` (array, required): 1 to 8 dropoff points.
- `pickup` (object, required): The single pickup point.
- `pickup_at` (string): ISO 8601 time the courier should arrive at the pickup. Omit to dispatch immediately.

### `stuart_estimate_dropoff_eta` (~98 tokens)

Estimate time to dropoff

Estimated seconds to reach the destination address for a job (coordinates need the text address too). Nothing is booked. Stuart: POST /v2/jobs/cpt.

Input parameters:

- `dropoffs` (array, required): 1 to 8 dropoff points.
- `pickup` (object, required): The single pickup point.
- `pickup_at` (string): ISO 8601 time the courier should arrive at the pickup. Omit to dispatch immediately.

### `stuart_validate_address` (~133 tokens)

Validate a pickup or dropoff address

Check that an address can be geocoded and lies inside a Stuart zone, as a pickup (picking) or a dropoff (delivering). A phone number is needed when the address is approximate. Stuart: POST /v2/addresses/validate.

Input parameters:

- `address` (string, required): Full-text address.
- `coordinates` (object): Optional coordinates (up to 6 decimals). An address string is still required.
- `phone` (string): Contact phone (E.164); required when the address is not precise.
- `type` (string, required): picking = pickup address, delivering = dropoff address.

### `stuart_get_zone_coverage` (~73 tokens)

Get a zone's coverage area

GeoJSON of the picking or delivery area of an open Stuart zone (for example paris, london). Stuart: GET /v2/areas/{zone}.

Input parameters:

- `type` (string, required): Which area: pickup or dropoff.
- `zone` (string, required): Zone name, e.g. paris, london.

### `stuart_get_zone_schedule_slots` (~103 tokens)

Get a zone's scheduling slots

Available time slots (start and end, 15-minute steps) in a zone for a date, from the time of the request onward. Use a future date. Stuart: GET /v2/jobs/schedules/{zone}/{type}/{date}.

Input parameters:

- `date` (string, required): Date, YYYY-MM-DD.
- `type` (string, required): Slot type, e.g. pickup.
- `zone` (string, required): Zone name, e.g. paris, london.

### `stuart_get_courier_phone` (~79 tokens)

Get the courier's anonymous phone number

Anonymised phone number of the courier assigned to a delivery. Only works once a courier is assigned; expires when the delivery ends. Stuart: GET /v2/deliveries/{deliveryId}/phone_number.

Input parameters:

- `delivery_id` (required): Stuart delivery id (the id inside a job's deliveries, not the job id).

### `stuart_create_job` (~168 tokens)

Create a delivery job (dispatches a courier)

BOOKS A REAL, CHARGED DELIVERY: creates a job with one pickup and 1-8 dropoffs and starts looking for a courier right away (unless pickup_at schedules it: up to 4 days ahead, 30 for corporate accounts). Get a quote with stuart_estimate_price and check with stuart_validate_job first, and confirm with the user. Use the sandbox environment for tests. Stuart: POST /v2/jobs.

Input parameters:

- `assignment_code` (string): Invoicing reference shown on invoices.
- `dropoffs` (array, required): 1 to 8 dropoff points.
- `pickup` (object, required): The single pickup point.
- `pickup_at` (string): ISO 8601 time the courier should arrive at the pickup. Omit to dispatch immediately.

### `stuart_update_job` (~112 tokens)

Update delivery details

Change allowed details of a delivery in a job: client_reference, package_description, and the pickup/dropoff comment and contact (what is editable depends on the delivery status: once delivered only client_reference). Stuart: PATCH /v2/jobs/{jobId}.

Input parameters:

- `client_reference` (string)
- `delivery_id` (required): Delivery id inside the job.
- `dropoff` (object)
- `job_id` (required): Stuart job id.
- `package_description` (string)
- `pickup` (object)

### `stuart_cancel_job` (~90 tokens)

Cancel a delivery job

Cancels a whole job and all its deliveries. Stuart may charge a cancellation fee once a courier is on the way; confirm with the user first. Give a reason key for reporting. Stuart: POST /v2/jobs/{jobId}/cancel.

Input parameters:

- `comment` (string): Details.
- `job_id` (required): Stuart job id.
- `public_reason_key` (string): Reason for the cancellation.

### `stuart_cancel_delivery` (~84 tokens)

Cancel one delivery

Cancels a single delivery (one dropoff) of a multi-drop job. A cancellation fee may apply; confirm with the user first. Stuart: POST /v2/deliveries/{deliveryId}/cancel.

Input parameters:

- `comment` (string): Details.
- `delivery_id` (required): Stuart delivery id.
- `public_reason_key` (string): Reason for the cancellation.

### `stuart_mark_order_ready` (~134 tokens)

Signal that an order is ready for pickup

Tell Stuart the order is packed and ready for the courier to collect. Pass exactly one of job_id (all orders of the job) or delivery_id (one order). Send it only when the order is really ready. Stuart: POST /v2/jobs/{jobId}/order_ready or /v2/deliveries/{deliveryId}/order_ready.

Input parameters:

- `delivery_id`: Stuart delivery id (one order).
- `job_id`: Stuart job id (all orders under the job).
- `order_ready_at` (string): ISO 8601 time it became ready; default = now (server time).

## Diagnostics

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

## Score history

- 2026-10-25: 62
- 2026-10-24: 62

## Common questions

### What is the Stuart MCP by usefulapi server?

Stuart MCP by usefulapi is listed in the public MCP registry as io.usefulapi/stuart. Quote, validate, book and track Stuart courier deliveries; cancel jobs and check zone coverage. This page covers its hosted endpoint (https://stuart.usefulapi.io/mcp).

### Is the Stuart MCP by usefulapi server safe to use?

Stuart MCP by usefulapi scores 62 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 Stuart MCP by usefulapi server expose?

Stuart MCP by usefulapi exposes 15 tools: stuart_list_jobs, stuart_get_job, stuart_estimate_price, stuart_validate_job, stuart_estimate_pickup_eta, and 10 more. Their descriptions and schemas cost roughly 1,594 tokens of context every time the server is loaded.

### Does the Stuart MCP by usefulapi server require authentication?

Yes. Stuart 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 Stuart MCP by usefulapi server still maintained?

Stuart MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 25 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://stuart.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/stuart/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-stuart/stuart.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-stuart/stuart.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-stuart/stuart