Kuaidi100 launched China's first MCP-protocol-compatible logistics information service platform. The core API services of Kuaidi100's Baidiy
Locate2u 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.
What it does
Read stops, orders, trips and ratings; add notes to stops and shipments in Locate2u.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http locate2u-mcp-by-usefulapi https://locate2u.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# locate2u_get_me, locate2u_get_team, locate2u_list_team_members and 31 more
Locate2u 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.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
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.
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 locate2u-mcp-by-usefulapi https://locate2u.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
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.
34 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.
Get the user that owns the connected app: name, email, role, time zone. Locate2u API: GET /users/me.
No parameter schema on file.
Get the connected team with its settings and branding. Locate2u API: GET /team.
No parameter schema on file.
List the drivers and staff in the team, optionally with their current location. Locate2u API: GET /team-members.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| include_current_location | boolean | no | Include each member's last known location. |
| team_region_id | integer | no | Only members of this region (from locate2u_list_team_regions). |
Get one team member by public user id. Locate2u API: GET /team-members/{publicUserId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| public_user_id | string | yes | The member's publicUserId (from locate2u_list_team_members). |
List the regions of the team. Locate2u API: GET /team-regions.
No parameter schema on file.
List the team's warehouses. Locate2u API: GET /warehouses.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| team_region_id | integer | no | Only warehouses of this region. |
List all services the team offers. Locate2u API: GET /services.
No parameter schema on file.
List the team's customers. Locate2u API: GET /customers.
No parameter schema on file.
Search customers by text (name, company, email, phone). Locate2u API: GET /customers/search.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| search_text | string | yes | Text to search for. |
| page | integer | no | Page number (starts at 1). |
| per_page | integer | no | Results per page. |
Get one customer by id. Locate2u API: GET /customers/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | integer | yes | The customerId (from locate2u_list_customers). |
Search orders by order number, purchase order number, status, payment status, customer or date. Locate2u API: GET /orders/search.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_number | string | no | — |
| purchase_order_number | string | no | — |
| status | string | no | Order status. |
| payment_status | string | no | Payment status. |
| customer_id | integer | no | — |
| order_date | string | no | Order date yyyy-mm-dd. |
| page | integer | no | Page number (starts at 1). |
| per_page | integer | no | Results per page. |
Get one order by id. Locate2u API: GET /orders/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | integer | yes | The order id. |
Find a single order by its order number, or by a source and source reference pair. Locate2u API: GET /orders.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_number | string | no | — |
| source | string | no | — |
| source_reference | string | no | — |
List orders created between two dates, optionally with stops and items. Locate2u API: GET /orders/created.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from_date | string | yes | Start date yyyy-mm-dd. |
| to_date | string | yes | End date yyyy-mm-dd. |
| include_stops | boolean | no | — |
| include_order_items | boolean | no | — |
| include_stop_items | boolean | no | — |
| include_order_lines | boolean | no | — |
Get one stop (a delivery or pickup) with status, contact, address and time window. Locate2u API: GET /stops/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| stop_id | integer | yes | The stopId. |
| include_items | boolean | no | — |
| include_lines | boolean | no | — |
| include_tracking_link | boolean | no | — |
Find stops by the source reference that the integration stored on them. Locate2u API: GET /stops/search.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| source_reference | string | yes | — |
| include_items | boolean | no | — |
| include_lines | boolean | no | — |
| include_tracking_link | boolean | no | — |
List stops scheduled for a day (default: today in the team's zone), with paging. Locate2u API: GET /stops/scheduled.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| trip_date | string | no | Day yyyy-mm-dd. |
| team_region_id | integer | no | — |
| include_shipments | boolean | no | — |
| skip | integer | no | — |
| take | integer | no | — |
List stops that no driver has yet. Locate2u API: GET /stops/unassigned.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| trip_date | string | no | — |
| include_shipments | boolean | no | — |
| team_region_id | integer | no | — |
List all notes on a stop, with attachments. Locate2u API: GET /stops/{id}/notes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| stop_id | integer | yes | — |
Get the answers a driver gave to the proof-of-delivery questions on a stop. Locate2u API: GET /stops/{id}/podquestionanswers.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| stop_id | integer | yes | — |
Get a shipment with its pickup and drop stops and items. Locate2u API: GET /shipments/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| shipment_id | integer | yes | — |
| include_cost_and_charge_lines | boolean | no | — |
| include_tracking_link | boolean | no | — |
List shipments that no team member has yet. Locate2u API: GET /shipments/unassigned.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| trip_date | string | no | — |
| pickup_within_km_distance | number | no | — |
| team_region_id | integer | no | — |
List all notes on a shipment. Locate2u API: GET /shipments/{id}/notes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| shipment_id | integer | yes | — |
Summary of every trip in the team on a day: driver, distance, time, stop counts, status. Locate2u API: GET /team/trips/{tripDate}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| trip_date | string | yes | — |
All trips (assigned and unassigned) for a day, each with its driver and stops. Locate2u API: GET /trips/team/{tripDate}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| trip_date | string | yes | — |
Get the trip of one team member on a day, optionally filtered by status. Locate2u API: GET /trips/user/{publicUserId}/{tripDate}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| public_user_id | string | yes | — |
| trip_date | string | yes | — |
| status | string | no | — |
| include_lines | boolean | no | — |
Get one trip by id with its stops. Locate2u API: GET /trips/id/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| trip_id | integer | yes | — |
| include_lines | boolean | no | — |
List the runs scheduled for a day, optionally for one team member, customer or run number. Locate2u API: GET /runs/{tripDate}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| trip_date | string | yes | — |
| team_member | string | no | — |
| customer_id | integer | no | — |
| run_number | string | no | — |
Distance and time driven by the team's members and asset groups over a date range. Locate2u API: GET /team/reports/travel-statistics.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from_date | string | no | — |
| to_date | string | no | — |
| team_region_id | integer | no | — |
Delivery ratings that customers left for the team's stops over a date range. Locate2u API: GET /team/{teamId}/customer-ratings.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| team_id | integer | yes | The team id (from locate2u_get_team). |
| start_date | string | yes | — |
| end_date | string | yes | — |
| higher_ratings | boolean | no | — |
| lower_ratings | boolean | no | — |
Search inventory items by keyword, warehouse or status. Locate2u API: GET /items/search.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| keyword | string | no | — |
| warehouse_id | integer | no | — |
| item_status | string | no | — |
| location_status | string | no | — |
| page | integer | no | Page number (starts at 1). |
| per_page | integer | no | Results per page. |
Get one inventory item by id. Locate2u API: GET /items/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| item_id | integer | yes | — |
WRITE: add a text note to a stop. It is visible to the team and the driver. Each call adds a new note (do not retry blindly). Locate2u API: POST /stops/{id}/notes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| stop_id | integer | yes | — |
| note | string | yes | The note text. |
WRITE: add a text note to a shipment, optionally tied to one of its stops. Each call adds a new note (do not retry blindly). Locate2u API: POST /shipments/{id}/notes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| shipment_id | integer | yes | — |
| note | string | yes | The note text. |
| stop_id | integer | no | A stop of the shipment the note belongs to. |
- 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 Locate2u MCP by usefulapi or to call it, at any volume.
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.
| 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 |
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.
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 |
|---|---|---|
| locate2u_get_me | no tags | |
| locate2u_get_team | no tags | |
| locate2u_list_team_members | no tags | |
| locate2u_get_team_member | no tags | |
| locate2u_list_team_regions | no tags | |
| locate2u_list_warehouses | no tags | |
| locate2u_list_services | no tags | |
| locate2u_list_customers | no tags | |
| locate2u_search_customers | no tags | |
| locate2u_get_customer | no tags | |
| locate2u_search_orders | no tags | |
| locate2u_get_order | no tags | |
| locate2u_find_order | no tags | |
| locate2u_list_orders_created | no tags | |
| locate2u_get_stop | no tags | |
| locate2u_search_stops | no tags | |
| locate2u_list_scheduled_stops | no tags | |
| locate2u_list_unassigned_stops | no tags | |
| locate2u_list_stop_notes | no tags | |
| locate2u_get_stop_pod_answers | no tags | |
| locate2u_get_shipment | no tags | |
| locate2u_list_unassigned_shipments | no tags | |
| locate2u_list_shipment_notes | no tags | |
| locate2u_get_team_trips_summary | no tags | |
| locate2u_list_team_trips | no tags | |
| locate2u_get_driver_trip | no tags | |
| locate2u_get_trip | no tags | |
| locate2u_list_runs | no tags | |
| locate2u_team_travel_statistics | no tags | |
| locate2u_list_customer_ratings | no tags | |
| locate2u_search_items | no tags | |
| locate2u_get_item | no tags | |
| locate2u_add_stop_note | state-write | state-write: declares destructiveHint: true |
| locate2u_add_shipment_note | state-write | state-write: declares destructiveHint: 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.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
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.5.3.
No release note was published with this version.
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.
Any signed-in account that does not publish Locate2u 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.
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.