# Delopt delivery dispatch (remote · api.delopt.transopt.io)

AI dispatch for food & local delivery: assigns orders to drivers, sequences stops, times departures.

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

## Components

- remote · `api.delopt.transopt.io`: 0/100, [markdown](https://verifymcp.io/servers/io-transopt-delopt-api-mcp/api.md), [page](https://verifymcp.io/servers/io-transopt-delopt-api-mcp/api)
- remote · `api.delopt.transopt.io`: 72/100 (this document), [markdown](https://verifymcp.io/servers/io-transopt-delopt-api-mcp/mcp-demo.md), [page](https://verifymcp.io/servers/io-transopt-delopt-api-mcp/mcp-demo)

## Channel facts

- Endpoint: `https://api.delopt.transopt.io/mcp/demo`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.5`

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

- **Endpoint Security**: 77/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/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 1243 tokens (~155/item across 8 items; 5 tools + 3 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**: 92/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 71% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Delopt delivery dispatch MCP server?

Delopt delivery dispatch is a hosted endpoint at https://api.delopt.transopt.io/mcp/demo, 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-transopt-delopt-api-mcp 'https://api.delopt.transopt.io/mcp/demo'
```

### Cursor

```json
{
  "mcpServers": {
    "io-transopt-delopt-api-mcp": {
      "url": "https://api.delopt.transopt.io/mcp/demo"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-transopt-delopt-api-mcp": {
      "type": "http",
      "url": "https://api.delopt.transopt.io/mcp/demo"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-transopt-delopt-api-mcp]
url = "https://api.delopt.transopt.io/mcp/demo"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-transopt-delopt-api-mcp": {
      "type": "remote",
      "url": "https://api.delopt.transopt.io/mcp/demo",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-transopt-delopt-api-mcp --url 'https://api.delopt.transopt.io/mcp/demo' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-transopt-delopt-api-mcp:
    url: "https://api.delopt.transopt.io/mcp/demo"
```

### Netclaw

```json
{
  "McpServers": {
    "io-transopt-delopt-api-mcp": {
      "Transport": "http",
      "Url": "https://api.delopt.transopt.io/mcp/demo"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-transopt-delopt-api-mcp -t streamable-http -u 'https://api.delopt.transopt.io/mcp/demo'
```

### Other

```json
{
  "mcpServers": {
    "io-transopt-delopt-api-mcp": {
      "type": "http",
      "url": "https://api.delopt.transopt.io/mcp/demo"
    }
  }
}
```

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-24 (score 72, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-23 (score 72)

First indexed and scored.

## MCP tools (5)

### `plan_deliveries` (~584 tokens)

Plan fleet deliveries

Plan which vehicle delivers which orders, in what order, and when each
vehicle leaves the depot, minimising customer waiting time.

Built for live dispatch through a busy shift, where orders keep arriving
and each driver goes out many times. Call it again whenever new orders
come in or a driver returns, with every order not yet sent out. Dispatch
only each vehicle's first run: later runs are a look-ahead the next call
revises.

Every order is assigned, so the vehicles' combined capacity (times
max_deliveries_per_vehicle) must cover all orders. Returns per-vehicle
stop lists with ETAs and each order's wait versus its target, plus
headline KPIs. The plan is a recommendation: nothing is stored or sent
to drivers.

The plan minimises how long customers wait, with an extra cost per minute
an order is late. Far orders get a little more time than their wait
target (distance_grace_minutes in the result). Set freshness to the
user's kind of goods (hot meals, iced coffee, ...) to keep sensitive
orders' rides short. The defaults suit same-day food delivery.

Input parameters:

- `depot`: Where the vehicles start from. Omit only if your API key is bound to a depot, in which case the server supplies it.
- `factor_wait` (number): Cost per minute of every order's wait, from received_at to arrival (default 1). Only its ratio to factor_wait_excess matters; leave the default unless the user asks for something specific.
- `factor_wait_excess` (number): Lateness weight: extra cost per minute an order is late, beyond its wait_target_minutes plus distance grace (default 10), so 40 minutes late costs far more than 5. Values from 1 to 100 give similar p…
- `freshness`: Freshness class for orders that don't give their own, usually the shop's kind of goods: hot (hot meals), cold (iced coffee, cold drinks), crispy (fries, delicate food), frozen, or robust (not modelle…
- `max_deliveries_per_vehicle` (integer): How many consecutive delivery runs to plan per vehicle. Only the first run of each vehicle needs dispatching now: plan again when a vehicle returns.
- `optimization_seconds` (integer): Solver time budget in seconds; more can give slightly better plans. Below 5 the plan is returned with a warning, as priority orders may not be sent out first.
- `orders` (array, required)
- `vehicles` (array, required)

Output parameters:

- `avg_wait_minutes` (number)
- `deliveries` (array)
- `max_wait_minutes` (number)
- `notice`: Account notice to pass on to the user, e.g. a trial ending soon
- `orders_over_target` (integer)
- `orders_planned` (integer)
- `unplanned_order_ids` (array): Orders the plan does not cover, if any
- `vehicles_used` (integer)
- `warnings` (array): Things to tell the user about how this plan was made

### `plan_vehicle_departure` (~113 tokens)

Plan a driver's departure

A driver is leaving the depot now with these orders: find the best
visiting sequence and each order's ETA.

The orders must fit the vehicle's capacity. To decide which orders a
driver should take, use plan_deliveries instead. Nothing is stored or
sent to the driver.

Input parameters:

- `depot`: Where the vehicles start from. Omit only if your API key is bound to a depot, in which case the server supplies it.
- `orders` (array, required)
- `vehicle` (required)

Output parameters:

- `depart_at` (string)
- `notice`: Account notice to pass on to the user, e.g. a trial ending soon
- `return_at` (string)
- `stops` (array): In visiting order
- `vehicle_id` (string)

### `geocode_address` (~58 tokens)

Look up an address

Look up coordinates and a short street address for a free-text address.

Check `precise`: when false, only a town or street was matched and the
coordinates are an approximate area centre.

Input parameters:

- `query` (string, required): Free-text address

Output parameters:

- `address`
- `lat` (number)
- `lon` (number)
- `precise` (boolean): False when only a town or street was matched, so lat/lon is an approximate area centre rather than the address itself

### `get_account_status` (~74 tokens)

Check account status

The caller's Delopt plan and what is left of it: vehicle and rate limits,
today's address lookups, the free trial and how to upgrade.

Use it when a plan is refused for a limit, or when the user asks about their
plan, trial or remaining lookups. It spends no lookups.

Output parameters:

- `address_lookups`
- `channel` (string): full (web app, REST API and MCP) or mcp (AI assistants only)
- `free_trial_available` (boolean): True when the account can still start a free trial
- `max_vehicles` (integer): Vehicles allowed in one plan
- `notice`: Something to pass on to the user, e.g. a trial that ended
- `plan` (string): free, basic, advanced, pro, enterprise or demo
- `rate_limit` (string): Tool calls allowed, e.g. 30/minute
- `subscription_status`
- `trial`: The free trial, while one is running
- `upgrade_url` (string)

### `request_more_vehicles` (~115 tokens)

Request more vehicles

Ask the Delopt team for a plan with more vehicles than the largest
self-serve plan allows (8).

For up to 8 vehicles, upgrading the plan is enough, so nothing is sent: the
answer says which plan fits. Asking again updates the open request. The
team follows up with the account's email address.

Input parameters:

- `note`: Optional: what the fleet is, or anything else the team should know
- `vehicles_needed` (integer, required): How many vehicles one plan should be able to cover

Output parameters:

- `message` (string): What to tell the user
- `recorded` (boolean): True when the request was passed to the Delopt team
- `vehicles_requested` (integer)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-transopt-delopt-api-mcp/mcp-demo#diagnostics

## Score history

- 2026-10-24: 72
- 2026-10-23: 72

## Common questions

### What is the Delopt delivery dispatch MCP server?

Delopt delivery dispatch is an MCP server listed in the public MCP registry as io.transopt.delopt.api/mcp. AI dispatch for food & local delivery: assigns orders to drivers, sequences stops, times departures. This page covers its hosted endpoint (https://api.delopt.transopt.io/mcp/demo).

### Is the Delopt delivery dispatch MCP server safe to use?

Delopt delivery dispatch scores 72 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 Delopt delivery dispatch MCP server expose?

Delopt delivery dispatch exposes 5 tools: plan_deliveries, plan_vehicle_departure, geocode_address, get_account_status, request_more_vehicles. Their descriptions and schemas cost roughly 944 tokens of context every time the server is loaded.

### Does the Delopt delivery dispatch MCP server require authentication?

No. We connected to Delopt delivery dispatch without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Delopt delivery dispatch MCP server still maintained?

Delopt delivery dispatch is still listed as active in the MCP registry. We last reached this channel on 24 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://api.delopt.transopt.io/mcp/demo
- Website: https://delopt.transopt.io/
- Changelog RSS feed: https://verifymcp.io/servers/io-transopt-delopt-api-mcp/mcp-demo.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-transopt-delopt-api-mcp/mcp-demo.json
- HTML version of this page: https://verifymcp.io/servers/io-transopt-delopt-api-mcp/mcp-demo