Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.usefulapi/clickup

REMOTE · CLICKUP.USEFULAPI.IO · SCANNED SEP 20

Read teams, spaces, lists and tasks; create, update and comment on tasks and track time.

Available components

remote · clickup.usefulapi.io 86
0 this week 86 Trust /100
Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security78
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. View diagnostics → Pass
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
  • The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
Schema Quality & AI Usability82
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1598 tokens (~114/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the io.usefulapi/clickup MCP server?

io.usefulapi/clickup is a hosted endpoint at https://clickup.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.

remote · clickup.usefulapi.io

# add to Claude Code
claude mcp add --transport http io-usefulapi-clickup 'https://clickup.usefulapi.io/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "io-usefulapi-clickup": {
      "url": "https://clickup.usefulapi.io/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "io-usefulapi-clickup": {
      "type": "http",
      "url": "https://clickup.usefulapi.io/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.io-usefulapi-clickup]
url = "https://clickup.usefulapi.io/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-clickup": {
      "type": "remote",
      "url": "https://clickup.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add io-usefulapi-clickup --url 'https://clickup.usefulapi.io/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  io-usefulapi-clickup:
    url: "https://clickup.usefulapi.io/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "io-usefulapi-clickup": {
      "Transport": "http",
      "Url": "https://clickup.usefulapi.io/mcp"
    }
  }
}
# add to Vellum
assistant mcp add io-usefulapi-clickup -t streamable-http -u 'https://clickup.usefulapi.io/mcp'
// mcp.json
{
  "mcpServers": {
    "io-usefulapi-clickup": {
      "type": "http",
      "url": "https://clickup.usefulapi.io/mcp"
    }
  }
}

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

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 1 Sept 26 0
    • Stability: 0.97 → pass security
  • 31 Aug 26 +1

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

  • 28 Aug 26 +1

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

  • 26 Aug 26 +2
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Aug 26 +1

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

  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 3 Aug 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 2 Aug 26 0
    • Authorization: unverified → pass ▲ security
    • First check of Authorization: partial security
    • MCP protocol: unverified → fail ▼ functional
    • Tool coverage: unverified → 100 ▲ functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: excellent functional
    • First check of Schema quality: fail functional
    • First check of Tool coverage: 100 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Probed https://clickup.usefulapi.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=usefulapi.io CN=WE1,O=Google Trust Services,C=US 1 Aug 2026 30 Oct 2026 ECDSA 256 ECDSA-SHA256 77a8fc75c723b7750edd56f71b0f5f3c
SANs: usefulapi.io, clickup.usefulapi.io, *.clickup.usefulapi.io
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of clickup.usefulapi.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 57355 8 Verified
usefulapi.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://clickup.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token" 

Bearer realm="OAuth", resource_metadata="https://clickup.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"

Protected resource metadata

Document https://clickup.usefulapi.io/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://clickup.usefulapi.io/mcp
Authorisation server https://clickup.usefulapi.io

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://clickup.usefulapi.io/mcp Verified 200
http (plaintext) http://clickup.usefulapi.io/mcp Inconclusive 401
MCP tools · 14 exposed · ~1,598 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
clickup_create_task ~249

WRITE: create a new task in a list. `name` is required; the list is the {list_id} path param, not a body field. ClickUp REST: POST /list/{list_id}/task.

NameTypeReqDescription
assigneesarray–User ids to assign the task to (numeric).
descriptionstring–The task description / body text.
due_dateinteger–Due date as Unix time in ms.
due_date_timeboolean–Whether due_date carries a time component (else date-only).
list_idstringyesThe list id to create the task in (path param, not body).
namestringyesThe task name (required).
parentstring–Parent task id — set to create this task as a subtask.
priorityinteger–Task priority: 1=Urgent, 2=High, 3=Normal, 4=Low.
start_dateinteger–Start date as Unix time in ms.
statusstring–Status name (must be a valid status in the list).
tagsarray–Tag names to attach.

No output schema declared.

No examples provided.

clickup_create_task_comment ~123

WRITE: add a comment to a task. `comment_text` is required; the task is the {task_id} path param. ClickUp REST: POST /task/{task_id}/comment.

NameTypeReqDescription
assigneeinteger–User id to assign the comment to (numeric).
comment_textstringyesThe comment text (required).
notify_allboolean–If true, notify everyone tagged/subscribed (else just the assignee).
task_idstringyesThe task id to comment on (path param, not body).

No output schema declared.

No examples provided.

clickup_get_authorized_user ~32

Get the user associated with the current ClickUp API token. ClickUp REST: GET /user.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

clickup_get_list_comments ~42

Get the comments on a list. ClickUp REST: GET /list/{list_id}/comment.

NameTypeReqDescription
list_idstringyesThe list id.

No output schema declared.

No examples provided.

clickup_get_task ~59

Get a single task by id. ClickUp REST: GET /task/{task_id}.

NameTypeReqDescription
include_subtasksboolean–Include the task's subtasks (serialized true/false).
task_idstringyesThe task id.

No output schema declared.

No examples provided.

clickup_get_task_comments ~42

Get the comments on a task. ClickUp REST: GET /task/{task_id}/comment.

NameTypeReqDescription
task_idstringyesThe task id.

No output schema declared.

No examples provided.

clickup_get_tasks ~242

Get the tasks in a list, with optional filters and pagination. ClickUp REST: GET /list/{list_id}/task.

NameTypeReqDescription
archivedboolean–Include archived items — serialized as archived=true/false. Default false.
assigneesarray–Filter by assignee user ids (repeated assignees[] params).
due_date_gtinteger–Only tasks due after this Unix time in ms.
due_date_ltinteger–Only tasks due before this Unix time in ms.
include_closedboolean–Include closed tasks (serialized true/false).
list_idstringyesThe list id.
order_bystring–Sort field, e.g. 'created', 'updated', 'due_date', 'id'.
pageinteger–0-indexed page number for pagination.
reverseboolean–Reverse the sort order (serialized true/false).
statusesarray–Filter by status names (repeated statuses[] params), e.g. ["open","in progress"].
subtasksboolean–Include subtasks (serialized true/false).

No output schema declared.

No examples provided.

clickup_list_folderless_lists ~71

List the lists that live directly in a space (not inside a folder). ClickUp REST: GET /space/{space_id}/list.

NameTypeReqDescription
archivedboolean–Include archived items — serialized as archived=true/false. Default false.
space_idstringyesThe space id.

No output schema declared.

No examples provided.

clickup_list_folders ~61

List folders in a space. ClickUp REST: GET /space/{space_id}/folder.

NameTypeReqDescription
archivedboolean–Include archived items — serialized as archived=true/false. Default false.
space_idstringyesThe space id.

No output schema declared.

No examples provided.

clickup_list_lists ~61

List the lists inside a folder. ClickUp REST: GET /folder/{folder_id}/list.

NameTypeReqDescription
archivedboolean–Include archived items — serialized as archived=true/false. Default false.
folder_idstringyesThe folder id.

No output schema declared.

No examples provided.

clickup_list_spaces ~65

List spaces in a workspace (team). ClickUp REST: GET /team/{team_id}/space.

NameTypeReqDescription
archivedboolean–Include archived items — serialized as archived=true/false. Default false.
team_idstringyesThe workspace (team) id.

No output schema declared.

No examples provided.

clickup_list_workspaces ~49

List the workspaces (the ClickUp API calls these "teams") the token can access — their ids are the team_id used by other tools. ClickUp REST: GET /team.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

clickup_search_tasks ~289

Search/filter tasks across a whole workspace (team), optionally scoped to spaces/folders/lists. ClickUp's "Get Filtered Team Tasks". ClickUp REST: GET /team/{team_id}/task.

NameTypeReqDescription
assigneesarray–Filter by assignee user ids (repeated assignees[] params).
due_date_gtinteger–Only tasks due after this Unix time in ms.
due_date_ltinteger–Only tasks due before this Unix time in ms.
include_closedboolean–Include closed tasks (serialized true/false).
list_idsarray–Restrict to these list ids (repeated list_ids[] params).
order_bystring–Sort field, e.g. 'created', 'updated', 'due_date', 'id'.
pageinteger–0-indexed page number for pagination.
project_idsarray–Restrict to these folder/project ids (repeated project_ids[] params).
reverseboolean–Reverse the sort order (serialized true/false).
space_idsarray–Restrict to these space ids (repeated space_ids[] params).
statusesarray–Filter by status names (repeated statuses[] params), e.g. ["open","in progress"].
team_idstringyesThe workspace (team) id.

No output schema declared.

No examples provided.

clickup_update_task ~213

WRITE: update fields on an existing task. Only the fields you pass are changed. ClickUp REST: PUT /task/{task_id}.

NameTypeReqDescription
archivedboolean–Archive (true) or unarchive (false) the task.
descriptionstring–New task description / body text.
due_dateinteger–Due date as Unix time in ms.
due_date_timeboolean–Whether due_date carries a time component (else date-only).
namestring–New task name.
parentstring–Parent task id (re-parent as a subtask).
priorityinteger–Task priority: 1=Urgent, 2=High, 3=Normal, 4=Low.
start_dateinteger–Start date as Unix time in ms.
statusstring–New status name (must be valid for the list).
task_idstringyesThe task id to update (path param, not body).

No output schema declared.

No examples provided.

Common questions

What is the io.usefulapi/clickup MCP server?

io.usefulapi/clickup is an MCP server listed in the public MCP registry as io.usefulapi/clickup. Read teams, spaces, lists and tasks; create, update and comment on tasks and track time. This page covers its hosted endpoint (https://clickup.usefulapi.io/mcp).

Is the io.usefulapi/clickup MCP server safe to use?

io.usefulapi/clickup scores 86 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 io.usefulapi/clickup MCP server expose?

io.usefulapi/clickup exposes 14 tools: clickup_get_authorized_user, clickup_list_workspaces, clickup_list_spaces, clickup_list_folders, clickup_list_lists, and 9 more. Their descriptions and schemas cost roughly 1,598 tokens of context every time the server is loaded.

Does the io.usefulapi/clickup MCP server require authentication?

Yes. io.usefulapi/clickup 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 io.usefulapi/clickup MCP server still maintained?

io.usefulapi/clickup is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.