Skip to content

Tookan MCP by usefulapi

io.usefulapi/tookanusefulapi.iostreamable-httpv1.32.5Scanned

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

15 tools: 3 can delete or cancel things and 12 only read.

Tools: 3 delete, 0 irreversible, 0 write, 12 read.
  • Reads private data · 4
  • Reads text others write · 3
  • Can send data out · 0
  • No findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

3 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Tookan MCP by usefulapi can do

The Tookan MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 15 tools. It can delete or cancel things (3 tools: tookan_create_delivery_task, tookan_assign_agent_to_task and tookan_update_task_status). 12 tools only read.

4 tools read private data (tookan_get_account, tookan_get_agent, tookan_list_customers and 1 more); 3 tools bring in text other people can write (tookan_get_account, tookan_get_agent and tookan_list_customers).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its tools changed once since Anlyon Radar first saw them.

Last scanned Oct 25, 2026, version 1.32.5.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

15 tools

Deletes or cancels 3Claude Code: deny
  • tookan_assign_agent_to_taskWRITE: assign (or reassign) a task to an agent of a team; replaces any previous agent.No findings

    Why it is in this group

    • The name "tookan_assign_agent_to_task" says "assign": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Assign an agent to a task
    • destructiveHint: true
    • idempotentHint: false
  • tookan_create_delivery_taskWRITE: create a delivery task (job) for a customer address, due by job_delivery_datetime in the given timezone.No findings

    Why it is in this group

    • The name "tookan_create_delivery_task" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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).

    Annotations the server declares

    • title: Create a delivery task
    • destructiveHint: true
  • tookan_update_task_statusWRITE (DESTRUCTIVE): force a task's status, overriding the agent app.No findings

    Why it is in this group

    • The name "tookan_update_task_status" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Update task status
    • destructiveHint: true
Only reads 12Show 12 read-only tools
  • tookan_find_customer_by_phoneFind customers by exact phone number.No findings

    Why it is in this group

    • The name "tookan_find_customer_by_phone" says "find": a word for reading.
    Description, as the server wrote it
    Find customers by exact phone number. POST /v2/find_customer_with_phone.

    Annotations the server declares

    • title: Find customer by phone
    • readOnlyHint: true
  • tookan_get_accountThe connected Tookan account (admin user): user_id, email, name, company name and address.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "tookan_get_account" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "email": it reads mail.
    • untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    The connected Tookan account (admin user): user_id, email, name, company name and address. Good first call. POST /v2/get_user_details.

    Annotations the server declares

    • title: Get account
    • readOnlyHint: true
  • tookan_get_agentOne agent's profile (name, email, phone, tags, transport, location, rating, active state) and current tasks.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "tookan_get_agent" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "email": it reads mail.
    • untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get agent profile
    • readOnlyHint: true
  • tookan_get_agent_locationAn agent's last known coordinates (latitude/longitude).No findings

    Why it is in this group

    • The name "tookan_get_agent_location" says "get": a word for reading.
    Description, as the server wrote it
    An agent's last known coordinates (latitude/longitude). POST /v2/get_fleet_location.

    Annotations the server declares

    • title: Get agent location
    • readOnlyHint: true
  • tookan_get_customerOne customer's profile (contact details, address, coordinates).Reads private dataNo findings

    Why it is in this group

    • The name "tookan_get_customer" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "contact": it reads contacts.
    Description, as the server wrote it
    One customer's profile (contact details, address, coordinates). POST /v2/view_customer_profile.

    Annotations the server declares

    • title: Get customer profile
    • readOnlyHint: true
  • tookan_get_task_statsTask counts per status (e.g.No findings

    Why it is in this group

    • The name "tookan_get_task_stats" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Task statistics
    • readOnlyHint: true
  • tookan_get_tasksFull 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; optionall…No findings

    Why it is in this group

    • The name "tookan_get_tasks" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get task details
    • readOnlyHint: true
  • tookan_get_tasks_by_order_idFull details of the tasks carrying the given order ids (the reference you set when creating a task).No findings

    Why it is in this group

    • The name "tookan_get_tasks_by_order_id" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get tasks by order id
    • readOnlyHint: true
  • tookan_list_agentsList agents (drivers / field workers; Tookan calls them fleets) with fleet_id, name, phone, tags, team and live status (0 available, 1 offline, 2 busy).No findings

    Why it is in this group

    • The name "tookan_list_agents" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List agents
    • readOnlyHint: true
  • tookan_list_customersList customers (customer_id, name, phone, email, address), optionally searched by name or phone.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "tookan_list_customers" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "email": it reads mail.
    • untrusted-inputThe description's first sentence says "list" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List customers
    • readOnlyHint: true
  • tookan_list_tasksList 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).No findings

    Why it is in this group

    • The name "tookan_list_tasks" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List tasks
    • readOnlyHint: true
  • tookan_list_teamsList teams (team_id, name, address, tags).No findings

    Why it is in this group

    • The name "tookan_list_teams" says "list": a word for reading.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • title: List teams
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data4
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:37 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 3 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://tookan.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://tookan.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 3 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://tookan.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://tookan.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed
  2. Tools15 added, 15 removed.+15 added−15 removedView diff

Install

Pinned to version 1.32.5. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__tookan__tookan_get_account",
      "mcp__tookan__tookan_list_tasks",
      "mcp__tookan__tookan_get_tasks",
      "mcp__tookan__tookan_get_tasks_by_order_id",
      "mcp__tookan__tookan_get_task_stats",
      "mcp__tookan__tookan_list_agents",
      "mcp__tookan__tookan_get_agent",
      "mcp__tookan__tookan_get_agent_location",
      "mcp__tookan__tookan_list_teams",
      "mcp__tookan__tookan_list_customers",
      "mcp__tookan__tookan_find_customer_by_phone",
      "mcp__tookan__tookan_get_customer"
    ],
    "ask": [],
    "deny": [
      "mcp__tookan__tookan_create_delivery_task",
      "mcp__tookan__tookan_assign_agent_to_task",
      "mcp__tookan__tookan_update_task_status"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as tookan. Review it before you use it.

Capability tags behind 4 rules
  • mcp__tookan__tookan_get_account private-data, untrusted-input
  • mcp__tookan__tookan_get_agent private-data, untrusted-input
  • mcp__tookan__tookan_list_customers private-data, untrusted-input
  • mcp__tookan__tookan_get_customer private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/tookan/verify?hash=7274a31630f3c9d15efd6902f70a566699601551be6ea570b743a185cf4eea6d" | jq -e '.changed == false'

Pinned hash 7274a31630f3, from Oct 25, 2026, 23:19 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.usefulapi/tookan/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.usefulapi/tookan
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/tookan.svg)](https://radar.anlyon.com/servers/io.usefulapi/tookan)

Source: MCP Registry · repository. Synced Nov 20, 2026, 20:18 UTC.

Tookan MCP by usefulapi: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Tookan MCP by usefulapi safe?

No scan can promise that. What its definitions show: 15 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Tookan MCP by usefulapi delete data?

Yes. 3 tools can delete, cancel or revoke something: tookan_create_delivery_task, tookan_assign_agent_to_task and tookan_update_task_status.

Can the Tookan MCP by usefulapi do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Tookan MCP by usefulapi have?

15 tools: 3 destructive, 12 read. tookan_create_delivery_task, tookan_assign_agent_to_task, tookan_update_task_status, tookan_get_account, tookan_list_tasks, tookan_get_tasks, tookan_get_tasks_by_order_id, tookan_get_task_stats and 7 more.

Does the Tookan MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Tookan MCP by usefulapi send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Tookan MCP by usefulapi changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Oct 23, 2026. Every change is on this page and in its Atom feed.