Kuaidi100 launched China's first MCP-protocol-compatible logistics information service platform. The core API services of Kuaidi100's Baidiy
Nothing to run from here
Lalamove MCP by usefulapi is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
10
tools declared
remote
at its publisher
—
calls last 7d
What it does
Read Lalamove cities, vehicles, quotations and orders; quote, place, tip and cancel deliveries.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http lalamove-mcp-by-usefulapi https://lalamove.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# lalamove_list_cities, lalamove_get_quotation, lalamove_get_order and 7 more
Lalamove MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 578 servers
usefulapi578 servers
25 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http lalamove-mcp-by-usefulapi https://lalamove.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
10 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
No parameter schema on file.
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| quotation_id | string | yes | Lalamove quotation id (quotationId from lalamove_create_quotation). |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | string | yes | Lalamove order id (the orderId of an order, e.g. 107900701184 or a 19-digit id). |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | string | yes | Lalamove order id (the orderId of an order, e.g. 107900701184 or a 19-digit id). |
| driver_id | string | yes | Lalamove driver id (the driverId of the order once a driver accepted it). |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | string | yes | Lalamove order id (the orderId of an order, e.g. 107900701184 or a 19-digit id). |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| service_type | string | yes | Vehicle key from lalamove_list_cities, e.g. MOTORCYCLE, CAR, VAN. |
| stops | array | yes | The stops in order: stop 1 = pickup, the others = drop-offs (2-16 stops). |
| schedule_at | string | no | 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. |
| special_requests | array | no | Special request keys valid for the vehicle (lalamove_list_cities), e.g. COD, DOOR_TO_DOOR. |
| language | string | no | Address language key, e.g. en_HK or zh_HK. Default: English for the market. |
| route_optimized | boolean | no | Let Lalamove reorder the drop-offs for the cheapest route (needs 3+ stops). |
| priority_tier | boolean | no | Priority tier: faster matching, higher price. Default false (regular tier). |
| item | object | no | Item information (only supported in Thailand, Vietnam and Hong Kong). |
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 r
| Parameter | Type | Required | Notes |
|---|---|---|---|
| quotation_id | string | yes | Lalamove quotation id (quotationId from lalamove_create_quotation). |
| sender | object | yes | Contact at the pickup stop. |
| recipients | array | yes | One contact per drop-off stop, in the same order as the quotation's stops after the pickup. |
| proof_of_delivery | boolean | no | Ask the driver for a photo or signature at each stop. |
| metadata | object | no | Your own reference key/value pairs stored on the order (e.g. your order number). |
| confirm_total | string | yes | The total price the user approved, exactly as in the quotation priceBreakdown.total (e.g. "124"). |
| confirm | boolean | yes | Must be true. Set it only after the user has explicitly confirmed this action. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | string | yes | Lalamove order id (the orderId of an order, e.g. 107900701184 or a 19-digit id). |
| 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. |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | string | yes | Lalamove order id (the orderId of an order, e.g. 107900701184 or a 19-digit id). |
| confirm | boolean | yes | Must be true. Set it only after the user has explicitly confirmed this action. |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | string | yes | Lalamove order id (the orderId of an order, e.g. 107900701184 or a 19-digit id). |
| driver_id | string | yes | Lalamove driver id (the driverId of the order once a driver accepted it). |
| reason | string | yes | Why the driver is changed. |
| confirm | boolean | yes | Must be true. Set it only after the user has explicitly confirmed this action. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Lalamove MCP by usefulapi or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.14.3 · scanned 6 Nov 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 1 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digestd0a26916d05dce0437c68939f7659d035933b1eb6d6c1bb7e7f47b65ca3face9
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| lalamove_list_cities | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| lalamove_get_quotation | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| lalamove_get_order | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| lalamove_get_driver | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| lalamove_track_order | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| lalamove_create_quotation | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| lalamove_place_order | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| lalamove_add_priority_fee | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| lalamove_cancel_order | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| lalamove_change_driver | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digestd0a26916d05dce04
Scanned2026-11-06
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.14.3.
1.14.3
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Lalamove MCP by usefulapi can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.