Lalamove MCP by usefulapi
REMOTE · LALAMOVE.USEFULAPI.IO
Read Lalamove cities, vehicles, quotations and orders; quote, place, tip and cancel deliveries.
Available components
Last scanned (2 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 25 Oct 2026.
Category E-commerce
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 Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1953 tokens (~195/item across 10 items; 10 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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://lalamove.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 lalamove.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://lalamove.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://lalamove.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://lalamove.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://lalamove.usefulapi.io/mcp |
| Authorisation server | https://lalamove.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://lalamove.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/lalamove/ |
| http (plaintext) | http://lalamove.usefulapi.io/mcp | Inconclusive | 302 | http://lalamove.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 →
lalamove_add_priority_fee Add priority fee (tip, charges the wallet) ~167
WRITE, SPENDS MONEY: add a priority fee (tip) to an order to attract a driver. Only possible before a driver accepts the order. The amount replaces the earlier fee and must be higher than it; the difference is charged to the wallet. Amount in the market's currency (see the order's priceBreakdown.currency). POST /v3/orders/{orderId}/priority-fee.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | The new total priority fee, e.g. "20". |
| confirm | boolean | yes | Must be true. Set it only after the user has explicitly confirmed this action. |
| order_id | string | yes | Lalamove order id (the orderId of an order, e.g. 107900701184 or a 19-digit id). |
No output schema declared.
No examples provided.
lalamove_cancel_order Cancel order ~143
WRITE, DESTRUCTIVE: cancel a delivery order. Lalamove only allows it while the order is ASSIGNING_DRIVER, or less than 5 minutes after a driver accepted it; otherwise it answers ERR_CANCELLATION_FORBIDDEN. A cancelled order cannot be revived, only re-placed from a new quotation. DELETE /v3/orders/{orderId}.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | yes | Must be true. Set it only after the user has explicitly confirmed this action. |
| order_id | string | yes | Lalamove order id (the orderId of an order, e.g. 107900701184 or a 19-digit id). |
No output schema declared.
No examples provided.
lalamove_change_driver Change driver ~179
WRITE: ask Lalamove to replace the driver of an order (no extra fee). Allowed 15 minutes after the driver was matched and before pickup; the order goes back to ASSIGNING_DRIVER and a new driver is looked for. Needs the current driver id from lalamove_get_order. DELETE /v3/orders/{orderId}/drivers/{driverId}.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | yes | Must be true. Set it only after the user has explicitly confirmed this action. |
| driver_id | string | yes | Lalamove driver id (the driverId of the order once a driver accepted it). |
| order_id | string | yes | Lalamove order id (the orderId of an order, e.g. 107900701184 or a 19-digit id). |
| reason | string | yes | Why the driver is changed. |
No output schema declared.
No examples provided.
lalamove_create_quotation Get a delivery quotation ~351
Price a delivery: 2-16 stops (the first is the pickup, the rest are drop-offs), a vehicle type and optional extras. Returns quotationId, per-stop stopId, the price breakdown and currency, distance and expiresAt (about 5 minutes). It creates a quotation only: nothing is ordered and nothing is charged. Get the vehicle keys from lalamove_list_cities. Show the price to the user before placing an order. POST /v3/quotations.
| Name | Type | Req | Description |
|---|---|---|---|
| item | object | – | Item information (only supported in Thailand, Vietnam and Hong Kong). |
| language | string | – | Address language key, e.g. en_HK or zh_HK. Default: English for the market. |
| priority_tier | boolean | – | Priority tier: faster matching, higher price. Default false (regular tier). |
| route_optimized | boolean | – | Let Lalamove reorder the drop-offs for the cheapest route (needs 3+ stops). |
| schedule_at | string | – | Pickup time in UTC (ISO 8601, ending in Z), up to 30 days ahead. Omit for an immediate delivery. Local 15:00 in Singapore (UTC+8) is 07:00Z. |
| service_type | string | yes | Vehicle key from lalamove_list_cities, e.g. MOTORCYCLE, CAR, VAN. |
| special_requests | array | – | Special request keys valid for the vehicle (lalamove_list_cities), e.g. COD, DOOR_TO_DOOR. |
| stops | array | yes | The stops in order: stop 1 = pickup, the others = drop-offs (2-16 stops). |
No output schema declared.
No examples provided.
lalamove_get_driver Get driver and location ~150
The driver of an order: name, phone, masked plate number, photo and last known coordinates (updated about every 10 seconds). Lalamove only shares this from 1 hour before the scheduled pickup (or the driver's arrival, whichever is earlier) until the order is completed; outside that window it answers 403. GET /v3/orders/{orderId}/drivers/{driverId}.
| Name | Type | Req | Description |
|---|---|---|---|
| driver_id | string | yes | Lalamove driver id (the driverId of the order once a driver accepted it). |
| order_id | string | yes | Lalamove order id (the orderId of an order, e.g. 107900701184 or a 19-digit id). |
No output schema declared.
No examples provided.
lalamove_get_order Get order ~119
One delivery order: status (ASSIGNING_DRIVER, ON_GOING, PICKED_UP, COMPLETED, CANCELED, REJECTED, EXPIRED), price breakdown, driver id, share link, distance, stops with proof of delivery and metadata. Only orders from the last 60 days can be read. GET /v3/orders/{orderId}.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | Lalamove order id (the orderId of an order, e.g. 107900701184 or a 19-digit id). |
No output schema declared.
No examples provided.
lalamove_get_quotation Get quotation ~79
A quotation by id: stops (with stopId), vehicle, price breakdown, currency, distance and expiresAt (a quotation can be ordered for 5 minutes). GET /v3/quotations/{quotationId}.
| Name | Type | Req | Description |
|---|---|---|---|
| quotation_id | string | yes | Lalamove quotation id (quotationId from lalamove_create_quotation). |
No output schema declared.
No examples provided.
lalamove_list_cities List cities, vehicles and special requests ~66
The cities of the connected market with the vehicle types (serviceType keys such as MOTORCYCLE or CAR), their size and load, and the special requests each vehicle accepts. Use these exact keys in lalamove_create_quotation. GET /v3/cities.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lalamove_place_order Place delivery order (charges the wallet) ~296
WRITE, SPENDS MONEY: order a delivery from a quotation. In production the total price is charged to the prepaid Lalamove wallet and a driver is dispatched; cancellation is only free within Lalamove's policy. Only call it after the user has seen the quotation price and said yes. confirm_total must equal the quotation total (it is checked against Lalamove, and an expired quotation is refused). The recipients are given in stop order and matched to the quotation's drop-off stops by the tool. The order is placed once: do not retry after an error without checking lalamove_get_order. POST /v3/orders.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | yes | Must be true. Set it only after the user has explicitly confirmed this action. |
| confirm_total | string | yes | The total price the user approved, exactly as in the quotation priceBreakdown.total (e.g. "124"). |
| metadata | object | – | Your own reference key/value pairs stored on the order (e.g. your order number). |
| proof_of_delivery | boolean | – | Ask the driver for a photo or signature at each stop. |
| quotation_id | string | yes | Lalamove quotation id (quotationId from lalamove_create_quotation). |
| recipients | array | yes | One contact per drop-off stop, in the same order as the quotation's stops after the pickup. |
| sender | object | yes | Contact at the pickup stop. |
No output schema declared.
No examples provided.
lalamove_track_order Track order ~131
Where is my delivery: the order status, stop-level proof of delivery and share link, plus (when a driver has the order and it is on its way) the driver's name and live coordinates. Two reads: GET /v3/orders/{orderId} and, if a driver is assigned and the order is ON_GOING or PICKED_UP, GET /v3/orders/{orderId}/drivers/{driverId}.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | Lalamove order id (the orderId of an order, e.g. 107900701184 or a 19-digit id). |
No output schema declared.
No examples provided.
How do I install the Lalamove MCP by usefulapi server?
Lalamove MCP by usefulapi is a hosted endpoint at https://lalamove.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 · lalamove.usefulapi.io
claude mcp add --transport http io-usefulapi-lalamove 'https://lalamove.usefulapi.io/mcp'
What is the Lalamove MCP by usefulapi server?
Lalamove MCP by usefulapi is listed in the public MCP registry as io.usefulapi/lalamove. Read Lalamove cities, vehicles, quotations and orders; quote, place, tip and cancel deliveries. This page covers its hosted endpoint (https://lalamove.usefulapi.io/mcp).
Is the Lalamove MCP by usefulapi server safe to use?
Lalamove 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 Lalamove MCP by usefulapi server expose?
Lalamove MCP by usefulapi exposes 10 tools: lalamove_list_cities, lalamove_get_quotation, lalamove_get_order, lalamove_get_driver, lalamove_track_order, and 5 more. Their descriptions and schemas cost roughly 1,681 tokens of context every time the server is loaded.
Does the Lalamove MCP by usefulapi server require authentication?
Yes. Lalamove 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 Lalamove MCP by usefulapi server still maintained?
Lalamove 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.