# Tookan MCP by usefulapi (remote · tookan.usefulapi.io)

Read Tookan tasks, agents, teams and customers; create delivery tasks and assign agents.

- Trust score: 65/100 (medium)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `tookan.usefulapi.io`: 65/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-tookan/tookan.md), [page](https://verifymcp.io/servers/io-usefulapi-tookan/tookan)

## Channel facts

- Endpoint: `https://tookan.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.2.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-17.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 78/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2397 tokens (~159/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Tookan MCP by usefulapi server?

Tookan MCP by usefulapi is a hosted endpoint at https://tookan.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.

### Claude

```bash
claude mcp add --transport http io-usefulapi-tookan 'https://tookan.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-tookan": {
      "url": "https://tookan.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-tookan": {
      "type": "http",
      "url": "https://tookan.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-tookan]
url = "https://tookan.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-tookan": {
      "type": "remote",
      "url": "https://tookan.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-tookan --url 'https://tookan.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-tookan:
    url: "https://tookan.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-tookan": {
      "Transport": "http",
      "Url": "https://tookan.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-tookan -t streamable-http -u 'https://tookan.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-tookan": {
      "type": "http",
      "url": "https://tookan.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-17 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-15 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-14 (score 63, +2)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] The server now declares the “prompts” capability
- [functional] First check of Schema quality: 100
- [functional] New prompt “getting_started”
- [functional] Server version: 1.4.0 → 1.5.0

### 2026-10-13 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-12 (score 60, +1)

- [functional improvement] Stability: unverified → 0.07

### 2026-10-10 (score 59)

First indexed and scored.

## MCP tools (15)

### `get_account` (~41 tokens)

Get account

The connected Tookan account (admin user): user_id, email, name, company name and address. Good first call. POST /v2/get_user_details.

### `list_tasks` (~404 tokens)

List tasks

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 declined, 9 cancelled, 10 deleted. POST /v2/get_all_tasks.

Input parameters:

- `custom_fields` (boolean): Include the tasks' custom-field data.
- `customer_id` (integer): Only tasks of this customer (from list_customers).
- `end_date` (string, required): End of the task-date range, YYYY-MM-DD (at most 31 days after start_date).
- `fleet_id` (integer): Only tasks of this agent (from list_agents).
- `job_ids` (array): Only these task (job) ids.
- `job_status`: 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.
- `job_type` (required): Task type: 0 = pickup, 1 = delivery, 2 = appointment, 3 = field workforce (FOS).
- `order_ids` (array): Only tasks with these order ids (your own reference).
- `page` (integer): Page number (default 1). Tookan pages are a fixed size.
- `start_date` (string, required): Start of the task-date range, YYYY-MM-DD.
- `team_id` (integer): Only tasks of this team (from list_teams).

### `get_tasks` (~166 tokens)

Get task details

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.

Input parameters:

- `include_additional_info` (boolean): Include the job's additional info.
- `include_task_history` (boolean): Include each task's status history.
- `job_ids` (array, required): Task (job) ids, e.g. [5145].

### `get_tasks_by_order_id` (~76 tokens)

Get tasks by order id

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.

Input parameters:

- `include_task_history` (boolean): Include each task's status history.
- `order_ids` (array, required): Order ids, e.g. ["P000469"].

### `get_task_stats` (~188 tokens)

Task statistics

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.

Input parameters:

- `end_date` (string): End date, YYYY-MM-DD.
- `job_status` (array): Only these statuses, e.g. [2, 3].
- `job_type`: Task type: 0 = pickup, 1 = delivery, 2 = appointment, 3 = field workforce (FOS).
- `start_date` (string): Start date, YYYY-MM-DD.
- `team_id` (integer): Only tasks of this team.

### `list_agents` (~247 tokens)

List agents

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.

Input parameters:

- `fleet_ids` (array): Only these agent ids.
- `fleet_type`: 1 = captive agents, 2 = freelancers.
- `include_team_id` (boolean): Include each agent's team id.
- `limit` (integer): Max items to return (default 50, max 200).
- `match_any_tag` (boolean): With tags: true = agents having ANY of the tags, false = ALL of them.
- `name` (string): Only agents whose name matches this text.
- `offset` (integer): Items to skip (use next_offset from the previous call).
- `status`: 0 = only free agents, 1 = only busy agents.
- `tags` (string): Comma-separated agent tags, e.g. "mini,suv".

### `get_agent` (~73 tokens)

Get agent profile

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.

Input parameters:

- `fleet_id` (integer, required): Agent id (fleet_id from list_agents).

### `get_agent_location` (~45 tokens)

Get agent location

An agent's last known coordinates (latitude/longitude). POST /v2/get_fleet_location.

Input parameters:

- `fleet_id` (integer, required): Agent id (fleet_id from list_agents).

### `list_teams` (~116 tokens)

List teams

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).

Input parameters:

- `include_agents` (boolean): Also return each team's agents (larger reply).
- `limit` (integer): Max items to return (default 50, max 200).
- `offset` (integer): Items to skip (use next_offset from the previous call).

### `list_customers` (~99 tokens)

List customers

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.

Input parameters:

- `name` (string): Search by customer name.
- `page` (integer): Page number (default 1). Tookan pages are a fixed size.
- `phone` (string): Search by customer phone number.

### `find_customer_by_phone` (~51 tokens)

Find customer by phone

Find customers by exact phone number. POST /v2/find_customer_with_phone.

Input parameters:

- `phone` (string, required): Phone number, e.g. "9897416008" or "+19897416008".

### `get_customer` (~42 tokens)

Get customer profile

One customer's profile (contact details, address, coordinates). POST /v2/view_customer_profile.

Input parameters:

- `customer_id` (integer, required): Customer id (from list_customers).

### `create_delivery_task` (~368 tokens)

Create a delivery task

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, layout_type 0).

Input parameters:

- `auto_assignment` (boolean): Let Tookan auto-assign the task to an agent of team_id.
- `customer_address` (string, required): Delivery address.
- `customer_email` (string): Customer email.
- `customer_phone` (string): Customer phone, e.g. "+12015555555".
- `customer_username` (string): Customer name.
- `fleet_id` (integer): Agent to assign the task to (from list_agents).
- `job_delivery_datetime` (string, required): Deliver before this local time, YYYY-MM-DD HH:MM:SS.
- `job_description` (string): What is to be delivered.
- `latitude` (string): Delivery latitude (else Tookan geocodes the address).
- `longitude` (string): Delivery longitude.
- `notify` (boolean): Send the customer/agent notifications.
- `order_id` (string): Your own reference for the task.
- `tags` (string): Comma-separated agent tags used by auto-assignment.
- `team_id` (integer): Team to put the task in (from list_teams).
- `timezone` (integer, required): Minutes to ADD to local time to get UTC (Tookan's convention): IST = -330, CET = -60, EST = 300, PST = 480.

### `assign_agent_to_task` (~118 tokens)

Assign an agent to a task

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.

Input parameters:

- `fleet_id` (integer, required): Agent id (from list_agents).
- `job_id` (integer, required): Task (job) id.
- `notify` (boolean): Notify the agent (default true).
- `team_id` (integer, required): The agent's team id (from list_teams).

### `update_task_status` (~153 tokens)

Update task status

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.

Input parameters:

- `job_id` (integer, required): Task (job) id.
- `job_status` (required): New status code (0-4, 6-9; 10 deleted is not allowed).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-tookan/tookan#diagnostics

## Score history

- 2026-10-17: 65
- 2026-10-16: 64
- 2026-10-15: 64
- 2026-10-14: 63
- 2026-10-13: 61
- 2026-10-12: 60
- 2026-10-10: 59

## Common questions

### What is the Tookan MCP by usefulapi server?

Tookan MCP by usefulapi is listed in the public MCP registry as io.usefulapi/tookan. Read Tookan tasks, agents, teams and customers; create delivery tasks and assign agents. This page covers its hosted endpoint (https://tookan.usefulapi.io/mcp).

### Is the Tookan MCP by usefulapi server safe to use?

Tookan MCP by usefulapi scores 65 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 Tookan MCP by usefulapi server expose?

Tookan MCP by usefulapi exposes 15 tools: get_account, list_tasks, get_tasks, get_tasks_by_order_id, get_task_stats, and 10 more. Their descriptions and schemas cost roughly 2,187 tokens of context every time the server is loaded.

### Does the Tookan MCP by usefulapi server require authentication?

Yes. Tookan 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 Tookan MCP by usefulapi server still maintained?

Tookan MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://tookan.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/tookan/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-tookan/tookan.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-tookan/tookan.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-tookan/tookan