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
Tookan 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.
15
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Read Tookan tasks, agents, teams and customers; create delivery tasks and assign agents.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http tookan-mcp-by-usefulapi https://tookan.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# get_account, list_tasks, get_tasks and 12 more
Tookan 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 334 servers
usefulapi334 servers
24 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 tookan-mcp-by-usefulapi https://tookan.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
15 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 connected Tookan account (admin user): user_id, email, name, company name and address. Good first call. POST /v2/get_user_details.
No parameter schema on file.
List tasks (Tookan calls them jobs) of one task type within a date range of the task date (at most 31 days, within the last 31 days). Paginated: one Tookan page per call (page, default 1). Filter by status, agent (fleet_id), team, customer, job ids or your order ids. Task status codes: 0 assigned, 1 started, 2 successful, 3 failed, 4 in progress/arrived, 6 unassigned, 7 accepted/acknowledged, 8 de
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job_type | yes | Task type: 0 = pickup, 1 = delivery, 2 = appointment, 3 = field workforce (FOS). | |
| start_date | string | yes | Start of the task-date range, YYYY-MM-DD. |
| end_date | string | yes | End of the task-date range, YYYY-MM-DD (at most 31 days after start_date). |
| job_status | no | Only tasks in this status. Task status codes: 0 assigned, 1 started, 2 successful, 3 failed, 4 in progress/arrived, 6 unassigned, 7 accepted/acknowledged, 8 declined, 9 cancelled, 10 deleted. | |
| fleet_id | integer | no | Only tasks of this agent (from list_agents). |
| team_id | integer | no | Only tasks of this team (from list_teams). |
| customer_id | integer | no | Only tasks of this customer (from list_customers). |
| job_ids | array | no | Only these task (job) ids. |
| order_ids | array | no | Only tasks with these order ids (your own reference). |
| custom_fields | boolean | no | Include the tasks' custom-field data. |
| page | integer | no | Page number (default 1). Tookan pages are a fixed size. |
Full details of up to 100 tasks by job id: customer, addresses, agent (fleet_id/fleet_name), status, timestamps (started/arrived/completed), tracking link, custom fields; optionally the status history. Task status codes: 0 assigned, 1 started, 2 successful, 3 failed, 4 in progress/arrived, 6 unassigned, 7 accepted/acknowledged, 8 declined, 9 cancelled, 10 deleted. POST /v2/get_job_details.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job_ids | array | yes | Task (job) ids, e.g. [5145]. |
| include_task_history | boolean | no | Include each task's status history. |
| include_additional_info | boolean | no | Include the job's additional info. |
Full details of the tasks carrying the given order ids (the reference you set when creating a task). POST /v2/get_job_details_by_order_id.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_ids | array | yes | Order ids, e.g. ["P000469"]. |
| include_task_history | boolean | no | Include each task's status history. |
Task counts per status (e.g. successful vs failed), optionally for one task type, one team and a date range. Task status codes: 0 assigned, 1 started, 2 successful, 3 failed, 4 in progress/arrived, 6 unassigned, 7 accepted/acknowledged, 8 declined, 9 cancelled, 10 deleted. POST /v2/user_task_stats.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job_status | array | no | Only these statuses, e.g. [2, 3]. |
| job_type | no | Task type: 0 = pickup, 1 = delivery, 2 = appointment, 3 = field workforce (FOS). | |
| start_date | string | no | Start date, YYYY-MM-DD. |
| end_date | string | no | End date, YYYY-MM-DD. |
| team_id | integer | no | Only tasks of this team. |
List agents (drivers / field workers; Tookan calls them fleets) with fleet_id, name, phone, tags, team and live status (0 available, 1 offline, 2 busy). Filter by name, tags, availability or fleet ids. The API returns the whole list; this tool returns a window (limit/offset, next_offset). POST /v2/get_all_fleets.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | no | Only agents whose name matches this text. |
| tags | string | no | Comma-separated agent tags, e.g. "mini,suv". |
| match_any_tag | boolean | no | With tags: true = agents having ANY of the tags, false = ALL of them. |
| status | no | 0 = only free agents, 1 = only busy agents. | |
| fleet_type | no | 1 = captive agents, 2 = freelancers. | |
| fleet_ids | array | no | Only these agent ids. |
| include_team_id | boolean | no | Include each agent's team id. |
| limit | integer | no | Max items to return (default 50, max 200). |
| offset | integer | no | Items to skip (use next_offset from the previous call). |
One agent's profile (name, email, phone, tags, transport, location, rating, active state) and current tasks. Only profile fields are returned; app tokens and password hashes never are. POST /v2/view_fleet_profile.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fleet_id | integer | yes | Agent id (fleet_id from list_agents). |
An agent's last known coordinates (latitude/longitude). POST /v2/get_fleet_location.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fleet_id | integer | yes | Agent id (fleet_id from list_agents). |
List teams (team_id, name, address, tags). With include_agents, each team also lists its agents. Returns a window (limit/offset, next_offset). POST /v2/view_all_team_only (or /v2/view_teams with agents).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| include_agents | boolean | no | Also return each team's agents (larger reply). |
| limit | integer | no | Max items to return (default 50, max 200). |
| offset | integer | no | Items to skip (use next_offset from the previous call). |
List customers (customer_id, name, phone, email, address), optionally searched by name or phone. Paginated: one Tookan page per call (page, default 1). POST /v2/get_all_customers.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | no | Search by customer name. |
| phone | string | no | Search by customer phone number. |
| page | integer | no | Page number (default 1). Tookan pages are a fixed size. |
Find customers by exact phone number. POST /v2/find_customer_with_phone.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| phone | string | yes | Phone number, e.g. "9897416008" or "+19897416008". |
One customer's profile (contact details, address, coordinates). POST /v2/view_customer_profile.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | integer | yes | Customer id (from list_customers). |
WRITE: create a delivery task (job) for a customer address, due by job_delivery_datetime in the given timezone. Optionally assign it to an agent (fleet_id) or team, or let Tookan auto-assign it within the team. Returns job_id and tracking link. Always uses the address given here, not one saved for the customer's phone (ignore_customer_lat_long 1). POST /v2/create_task (has_pickup 0, has_delivery 1
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_address | string | yes | Delivery address. |
| job_delivery_datetime | string | yes | Deliver before this local time, YYYY-MM-DD HH:MM:SS. |
| timezone | integer | yes | Minutes to ADD to local time to get UTC (Tookan's convention): IST = -330, CET = -60, EST = 300, PST = 480. |
| customer_username | string | no | Customer name. |
| customer_phone | string | no | Customer phone, e.g. "+12015555555". |
| customer_email | string | no | Customer email. |
| order_id | string | no | Your own reference for the task. |
| job_description | string | no | What is to be delivered. |
| latitude | string | no | Delivery latitude (else Tookan geocodes the address). |
| longitude | string | no | Delivery longitude. |
| team_id | integer | no | Team to put the task in (from list_teams). |
| fleet_id | integer | no | Agent to assign the task to (from list_agents). |
| auto_assignment | boolean | no | Let Tookan auto-assign the task to an agent of team_id. |
| tags | string | no | Comma-separated agent tags used by auto-assignment. |
| notify | boolean | no | Send the customer/agent notifications. |
WRITE: assign (or reassign) a task to an agent of a team; replaces any previous agent. Notifies the agent unless notify is false (so repeating the call notifies again). POST /v2/assign_fleet_to_task.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job_id | integer | yes | Task (job) id. |
| fleet_id | integer | yes | Agent id (from list_agents). |
| team_id | integer | yes | The agent's team id (from list_teams). |
| notify | boolean | no | Notify the agent (default true). |
WRITE (DESTRUCTIVE): force a task's status, overriding the agent app. Completing (2 successful, 3 failed) or cancelling (9) closes the task and notifies per the account's settings; confirm with the user first. Deleting (10) is not offered. Settable: 0 assigned, 1 started, 2 successful, 3 failed, 4 arrived, 6 unassigned, 7 accepted, 8 declined, 9 cancelled. POST /v2/update_task_status.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job_id | integer | yes | Task (job) id. |
| job_status | yes | New status code (0-4, 6-9; 10 deleted is not allowed). |
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 Tookan 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: —
—Grade not published
No rule-by-rule report on file for this release
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.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
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.2.1.
1.2.1
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 Tookan 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.