Remote MCP · Endpoint

Delopt delivery dispatch MCP server

No. Delopt delivery dispatch answered an MCP handshake 37 minutes ago.

UpLast checked 37 minutes ago

Server URL

https://api.delopt.transopt.io/mcp/demo

The last check completed an MCP handshake.

Registry name
io.transopt.delopt.api/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
140 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
AI dispatch for food & local delivery: assigns orders to drivers, sequences stops, times departures.
Listing
From the official MCP registry (active).
Recent checks of Delopt delivery dispatch
CheckedResultHandshake
37 minutes agoHandshake completed140 ms
4 days agoHandshake completed133 ms
7 days agoHandshake completed138 ms
16 days agoHandshake completed291 ms
16 days agoHandshake completed129 ms
18 days agoHandshake completed166 ms
19 days agoHandshake completed151 ms
20 days agoHandshake completed149 ms
21 days agoHandshake completed155 ms
22 days agoHandshake completed151 ms
23 days agoHandshake completed142 ms
26 days agoHandshake completed148 ms
29 days agoHandshake completed142 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 13.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Delopt delivery dispatch and makes no claim about it beyond what these checks measured.