Stuart MCP by usefulapi
REMOTE · STUART.USEFULAPI.IO
Quote, validate, book and track Stuart courier deliveries; cancel jobs and check zone coverage.
Available components
Last scanned (3 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 25 Oct 2026.
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 (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 91% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 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.
- 25 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.0.3 functional
- 24 Oct 26 62
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 25 Oct 2026 · Probed https://stuart.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 stuart.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690, 57355 | 8, 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://stuart.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://stuart.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://stuart.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://stuart.usefulapi.io/mcp |
| Authorisation server | https://stuart.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://stuart.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/stuart/ |
| http (plaintext) | http://stuart.usefulapi.io/mcp | Inconclusive | 302 | http://stuart.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 →
stuart_cancel_delivery Cancel one delivery ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | – | Details. |
| delivery_id | – | yes | Stuart delivery id. |
| public_reason_key | string | – | Reason for the cancellation. |
No output schema declared.
No examples provided.
stuart_cancel_job Cancel a delivery job ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | – | Details. |
| job_id | – | yes | Stuart job id. |
| public_reason_key | string | – | Reason for the cancellation. |
No output schema declared.
No examples provided.
stuart_create_job Create a delivery job (dispatches a courier) ~168
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.
| Name | Type | Req | Description |
|---|---|---|---|
| assignment_code | string | – | Invoicing reference shown on invoices. |
| dropoffs | array | yes | 1 to 8 dropoff points. |
| pickup | object | yes | The single pickup point. |
| pickup_at | string | – | ISO 8601 time the courier should arrive at the pickup. Omit to dispatch immediately. |
No output schema declared.
No examples provided.
stuart_estimate_dropoff_eta Estimate time to dropoff ~98
Estimated seconds to reach the destination address for a job (coordinates need the text address too). Nothing is booked. Stuart: POST /v2/jobs/cpt.
| Name | Type | Req | Description |
|---|---|---|---|
| dropoffs | array | yes | 1 to 8 dropoff points. |
| pickup | object | yes | The single pickup point. |
| pickup_at | string | – | ISO 8601 time the courier should arrive at the pickup. Omit to dispatch immediately. |
No output schema declared.
No examples provided.
stuart_estimate_pickup_eta Estimate courier arrival at pickup ~100
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dropoffs | array | yes | 1 to 8 dropoff points. |
| pickup | object | yes | The single pickup point. |
| pickup_at | string | – | ISO 8601 time the courier should arrive at the pickup. Omit to dispatch immediately. |
No output schema declared.
No examples provided.
stuart_estimate_price Get a delivery price quote ~107
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dropoffs | array | yes | 1 to 8 dropoff points. |
| pickup | object | yes | The single pickup point. |
| pickup_at | string | – | ISO 8601 time the courier should arrive at the pickup. Omit to dispatch immediately. |
No output schema declared.
No examples provided.
stuart_get_courier_phone Get the courier's anonymous phone number ~79
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.
| Name | Type | Req | Description |
|---|---|---|---|
| delivery_id | – | yes | Stuart delivery id (the id inside a job's deliveries, not the job id). |
No output schema declared.
No examples provided.
stuart_get_job Get a delivery job ~64
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | – | yes | Stuart job id. |
No output schema declared.
No examples provided.
stuart_get_zone_coverage Get a zone's coverage area ~73
GeoJSON of the picking or delivery area of an open Stuart zone (for example paris, london). Stuart: GET /v2/areas/{zone}.
| Name | Type | Req | Description |
|---|---|---|---|
| type | string | yes | Which area: pickup or dropoff. |
| zone | string | yes | Zone name, e.g. paris, london. |
No output schema declared.
No examples provided.
stuart_get_zone_schedule_slots Get a zone's scheduling slots ~103
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Date, YYYY-MM-DD. |
| type | string | yes | Slot type, e.g. pickup. |
| zone | string | yes | Zone name, e.g. paris, london. |
No output schema declared.
No examples provided.
stuart_list_jobs List delivery jobs ~149
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
stuart_mark_order_ready Signal that an order is ready for pickup ~134
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
stuart_update_job Update delivery details ~112
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| client_reference | string | – | – |
| delivery_id | – | yes | Delivery id inside the job. |
| dropoff | object | – | – |
| job_id | – | yes | Stuart job id. |
| package_description | string | – | – |
| pickup | object | – | – |
No output schema declared.
No examples provided.
stuart_validate_address Validate a pickup or dropoff address ~133
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | 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 | yes | picking = pickup address, delivering = dropoff address. |
No output schema declared.
No examples provided.
stuart_validate_job Validate a delivery job ~100
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dropoffs | array | yes | 1 to 8 dropoff points. |
| pickup | object | yes | The single pickup point. |
| pickup_at | string | – | ISO 8601 time the courier should arrive at the pickup. Omit to dispatch immediately. |
No output schema declared.
No examples provided.
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.
remote · stuart.usefulapi.io
claude mcp add --transport http io-usefulapi-stuart 'https://stuart.usefulapi.io/mcp'
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.