Delopt delivery dispatch
REMOTE · API.DELOPT.TRANSOPT.IO · 2 COMPONENTS
AI dispatch for food & local delivery: assigns orders to drivers, sequences stops, times departures.
Available components
Last scanned (17 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 24 Oct 2026.
Category Maps and Location
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 Security77
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- 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 1243 tokens (~155/item across 8 items; 5 tools + 3 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 Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 71% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 24 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 23 Oct 26 72
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 24 Oct 2026 · Probed https://api.delopt.transopt.io/mcp/demo
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.delopt.transopt.io | CN=WR3,O=Google Trust Services,C=US | 23 Sept 2026 | 22 Dec 2026 | RSA 2048 | SHA256-RSA | 26a34172bd0ab1ac0ae69595f48ad635 |
| SANs: api.delopt.transopt.io | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of api.delopt.transopt.io. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690, 57355 | 8, 8 | Verified |
| transopt.io. | present | 56041 | 8 | Verified |
| api.delopt.transopt.io. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.delopt.transopt.io/mcp/demo | Verified | 200 | |
| http (plaintext) | http://api.delopt.transopt.io/mcp/demo | HTTPS enforced | 302 | https://api.delopt.transopt.io/mcp/demo |
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 →
geocode_address Look up an address ~58
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Free-text address |
| Name | Type | Req | Description |
|---|---|---|---|
| address | – | yes | – |
| lat | number | yes | – |
| lon | number | yes | – |
| precise | boolean | yes | False when only a town or street was matched, so lat/lon is an approximate area centre rather than the address itself |
No examples provided.
get_account_status Check account status ~74
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| address_lookups | – | yes | – |
| channel | string | yes | full (web app, REST API and MCP) or mcp (AI assistants only) |
| free_trial_available | boolean | yes | True when the account can still start a free trial |
| max_vehicles | integer | yes | Vehicles allowed in one plan |
| notice | – | – | Something to pass on to the user, e.g. a trial that ended |
| plan | string | yes | free, basic, advanced, pro, enterprise or demo |
| rate_limit | string | yes | Tool calls allowed, e.g. 30/minute |
| subscription_status | – | yes | – |
| trial | – | – | The free trial, while one is running |
| upgrade_url | string | yes | – |
No examples provided.
plan_deliveries Plan fleet deliveries ~584
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| vehicles | array | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| avg_wait_minutes | number | yes | – |
| deliveries | array | yes | – |
| max_wait_minutes | number | yes | – |
| notice | – | – | Account notice to pass on to the user, e.g. a trial ending soon |
| orders_over_target | integer | yes | – |
| orders_planned | integer | yes | – |
| unplanned_order_ids | array | yes | Orders the plan does not cover, if any |
| vehicles_used | integer | yes | – |
| warnings | array | – | Things to tell the user about how this plan was made |
No examples provided.
plan_vehicle_departure Plan a driver's departure ~113
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| vehicle | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| depart_at | string | yes | – |
| notice | – | – | Account notice to pass on to the user, e.g. a trial ending soon |
| return_at | string | yes | – |
| stops | array | yes | In visiting order |
| vehicle_id | string | yes | – |
No examples provided.
request_more_vehicles Request more vehicles ~115
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.
| Name | Type | Req | Description |
|---|---|---|---|
| note | – | – | Optional: what the fleet is, or anything else the team should know |
| vehicles_needed | integer | yes | How many vehicles one plan should be able to cover |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | What to tell the user |
| recorded | boolean | yes | True when the request was passed to the Delopt team |
| vehicles_requested | integer | yes | – |
No examples provided.
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.
remote · api.delopt.transopt.io
claude mcp add --transport http io-transopt-delopt-api-mcp 'https://api.delopt.transopt.io/mcp/demo'
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.