ClickUp MCP by usefulapi
io.usefulapi/clickupusefulapi.iostreamable-httpv1.40.4Scanned
Read teams, spaces, lists and tasks; create, update and comment on tasks and track time.
14 tools: 3 can delete or cancel things and 11 only read.
- Reads private data · 4
- Reads text others write · 2
- Can send data out · 1
- 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 ClickUp MCP by usefulapi can do
The ClickUp MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 14 tools. It can delete or cancel things (3 tools: clickup_create_task, clickup_update_task and clickup_create_task_comment). 11 tools only read.
4 tools read private data (clickup_list_folders, clickup_list_lists, clickup_list_folderless_lists and 1 more); 2 tools bring in text other people can write (clickup_get_task_comments and clickup_get_list_comments); 1 tool can send data out of your system (clickup_create_task_comment). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Oct 25, 2026, version 1.40.4.
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.
14 tools
Deletes or cancels 3Claude Code: deny
clickup_create_taskWRITE: create a new task in a list.No findings
Why it is in this group
- The name "clickup_create_task" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- title: Create task
- destructiveHint: true
clickup_create_task_commentWRITE: add a comment to a task.Can send data outNo findings
Why it is in this group
- The name "clickup_create_task_comment" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- outboundThe name "clickup_create_task_comment" says "create" and "comment": it writes something other people read.
Description, as the server wrote it 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.
Annotations the server declares
- title: Create task comment
- destructiveHint: true
clickup_update_taskWRITE: update fields on an existing task.No findings
Why it is in this group
- The name "clickup_update_task" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it WRITE: update fields on an existing task. Only the fields you pass are changed. ClickUp REST: PUT /task/{task_id}.
Annotations the server declares
- title: Update task
- destructiveHint: true
Only reads 11Show 11 read-only tools
clickup_get_authorized_userGet the user associated with the current ClickUp API token.No findings
Why it is in this group
- The name "clickup_get_authorized_user" says "get": a word for reading.
Description, as the server wrote it Get the user associated with the current ClickUp API token. ClickUp REST: GET /user.
Annotations the server declares
- title: Get authorized user
- readOnlyHint: true
clickup_get_list_commentsGet the comments on a list.Reads text others writeNo findings
Why it is in this group
- The name "clickup_get_list_comments" says "get": a word for reading.
What it can reach
- untrusted-inputThe name "clickup_get_list_comments" says "get" and "comment": it reads comments, which other people can write.
- untrusted-inputThe description's first sentence says "get" and "comment": it reads comments, which other people can write.
Description, as the server wrote it Get the comments on a list. ClickUp REST: GET /list/{list_id}/comment.
Annotations the server declares
- title: Get list comments
- readOnlyHint: true
clickup_get_taskGet a single task by id.No findings
Why it is in this group
- The name "clickup_get_task" says "get": a word for reading.
Description, as the server wrote it Get a single task by id. ClickUp REST: GET /task/{task_id}.
Annotations the server declares
- title: Get task
- readOnlyHint: true
clickup_get_task_commentsGet the comments on a task.Reads text others writeNo findings
Why it is in this group
- The name "clickup_get_task_comments" says "get": a word for reading.
What it can reach
- untrusted-inputThe name "clickup_get_task_comments" says "get" and "comment": it reads comments, which other people can write.
- untrusted-inputThe description's first sentence says "get" and "comment": it reads comments, which other people can write.
Description, as the server wrote it Get the comments on a task. ClickUp REST: GET /task/{task_id}/comment.
Annotations the server declares
- title: Get task comments
- readOnlyHint: true
clickup_get_tasksGet the tasks in a list, with optional filters and pagination.No findings
Why it is in this group
- The name "clickup_get_tasks" says "get": a word for reading.
Description, as the server wrote it Get the tasks in a list, with optional filters and pagination. ClickUp REST: GET /list/{list_id}/task.
Annotations the server declares
- title: Get tasks
- readOnlyHint: true
clickup_list_folderless_listsList the lists that live directly in a space (not inside a folder).Reads private dataNo findings
Why it is in this group
- The name "clickup_list_folderless_lists" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "folder": it reads files.
Description, as the server wrote it List the lists that live directly in a space (not inside a folder). ClickUp REST: GET /space/{space_id}/list.
Annotations the server declares
- title: List folderless lists
- readOnlyHint: true
clickup_list_foldersList folders in a space.Reads private dataNo findings
Why it is in this group
- The name "clickup_list_folders" says "list": a word for reading.
What it can reach
- private-dataThe name "clickup_list_folders" says "list" and "folder": it reads files.
- private-dataThe description's first sentence says "list" and "folder": it reads files.
Description, as the server wrote it List folders in a space. ClickUp REST: GET /space/{space_id}/folder.
Annotations the server declares
- title: List folders
- readOnlyHint: true
clickup_list_listsList the lists inside a folder.Reads private dataNo findings
Why it is in this group
- The name "clickup_list_lists" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "folder": it reads files.
- private-dataThe input names a folder (input.folder_id), and the tool reads: it reads files.
Description, as the server wrote it List the lists inside a folder. ClickUp REST: GET /folder/{folder_id}/list.
Annotations the server declares
- title: List lists
- readOnlyHint: true
clickup_list_spacesList spaces in a workspace (team).No findings
Why it is in this group
- The name "clickup_list_spaces" says "list": a word for reading.
Description, as the server wrote it List spaces in a workspace (team). ClickUp REST: GET /team/{team_id}/space.
Annotations the server declares
- title: List spaces
- readOnlyHint: true
clickup_list_workspacesList the workspaces (the ClickUp API calls these "teams") the token can access — their ids are the team_id used by other tools.No findings
Why it is in this group
- The name "clickup_list_workspaces" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List workspaces
- readOnlyHint: true
clickup_search_tasksSearch/filter tasks across a whole workspace (team), optionally scoped to spaces/folders/lists.Reads private dataNo findings
Why it is in this group
- The name "clickup_search_tasks" says "search": a word for reading.
What it can reach
- private-dataThe description's first sentence says "search" and "folder": it reads files.
Description, as the server wrote it 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.
Annotations the server declares
- title: Search tasks
- 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.
8 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.
- Reads private data4
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__clickup__clickup_create_task_comment"
]
}
}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.
Looked at Nov 20, 2026, 19:34 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
- 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://clickup.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://clickup.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.
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://clickup.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://clickup.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Install
Pinned to version 1.40.4. Values in angle brackets are yours to fill in.
claude mcp add --transport http clickup https://clickup.usefulapi.io/mcpclaude mcp add --transport http clickup https://clickup.usefulapi.io/mcpRun 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.
{
"permissions": {
"allow": [
"mcp__clickup__clickup_get_authorized_user",
"mcp__clickup__clickup_list_workspaces",
"mcp__clickup__clickup_list_spaces",
"mcp__clickup__clickup_list_folders",
"mcp__clickup__clickup_list_lists",
"mcp__clickup__clickup_list_folderless_lists",
"mcp__clickup__clickup_get_tasks",
"mcp__clickup__clickup_get_task",
"mcp__clickup__clickup_get_task_comments",
"mcp__clickup__clickup_get_list_comments",
"mcp__clickup__clickup_search_tasks"
],
"ask": [],
"deny": [
"mcp__clickup__clickup_create_task",
"mcp__clickup__clickup_update_task",
"mcp__clickup__clickup_create_task_comment"
]
}
}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 clickup. Review it before you use it.
Capability tags behind 7 rules
- mcp__clickup__clickup_list_folders private-data
- mcp__clickup__clickup_list_lists private-data
- mcp__clickup__clickup_list_folderless_lists private-data
- mcp__clickup__clickup_get_task_comments untrusted-input
- mcp__clickup__clickup_get_list_comments untrusted-input
- mcp__clickup__clickup_search_tasks private-data
- mcp__clickup__clickup_create_task_comment outbound
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/clickup/verify?hash=9b57a37acd4e1631b6dff4e6822a777031591b4dbd1dcf8a800234db57d28d8a" | jq -e '.changed == false'Pinned hash 9b57a37acd4e, from Oct 25, 2026, 23:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.usefulapi/clickup/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/clickup)Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.
ClickUp MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the ClickUp MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 14 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 ClickUp MCP by usefulapi delete data?
- Yes. 3 tools can delete, cancel or revoke something: clickup_create_task, clickup_update_task and clickup_create_task_comment.
Can the ClickUp 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 ClickUp MCP by usefulapi have?
- 14 tools: 3 destructive, 11 read. clickup_create_task, clickup_update_task, clickup_create_task_comment, clickup_get_authorized_user, clickup_list_workspaces, clickup_list_spaces, clickup_list_folders, clickup_list_lists and 6 more.
Does the ClickUp MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the ClickUp MCP by usefulapi send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): clickup_create_task_comment.
Has the ClickUp MCP by usefulapi changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.