Clickup Project Management
Security checks across static analysis, malware telemetry, and agentic risk
Overview
This appears to be a transparent ClickUp integration, but it gives a third-party MCP server your ClickUp OAuth token and the ability to change workspace data.
Install only if you are comfortable giving the taazkareem.com MCP server access to your ClickUp workspace through OAuth. Prefer read-only or no-delete tool filters, confirm destructive changes manually, and revoke the ClickUp OAuth token if you no longer use the skill.
Static analysis
No static analysis findings were reported for this release.
VirusTotal
66/66 vendors flagged this skill as clean.
Risk analysis
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The remote server can act on your ClickUp workspace using your OAuth authorization.
The skill explicitly delegates credentialed ClickUp access to a third-party MCP server. This is disclosed and aligned with the integration, but it is high-trust account access.
Every MCP tool call sends your license key and ClickUp OAuth token to the remote server at `clickup-mcp.taazkareem.com`.
Only use this if you trust the operator; consider limiting the ClickUp account/workspace scope and revoke the OAuth token if you stop using the skill.
An agent using the full tool set could create, update, move, or delete ClickUp items.
The documented tool set includes destructive ClickUp operations. This fits project management, but mistakes or overly broad agent instructions could alter or delete workspace data.
`X-Disabled-Tools=delete_task,delete_bulk_tasks,delete_time_entry,delete_task_link,delete_list,delete_folder,delete_space_tag`
Use the Auditor or Safe Power User tool filters when possible, and require explicit confirmation before deletes or bulk changes.
Task names, IDs, comments, field values, and other workspace data may be processed by the third-party MCP service.
The MCP boundary is remote: workspace data and credentials are sent through an external server rather than only to ClickUp directly.
`https://clickup-mcp.taazkareem.com/mcp` | License key, ClickUp OAuth access token, MCP tool call payloads
Review the provider’s repository and privacy posture before use, and avoid sending sensitive workspace content unless necessary.
You must rely on the remote MCP operator and their hosted service for correct credential handling and ClickUp actions.
The local skill package is instruction-only and does not include the remote server implementation, so this review cannot verify the server behavior directly.
Source: unknown; Homepage: https://github.com/taazkareem/clickup-mcp-server
Review the linked project and operator before installing, and monitor ClickUp OAuth/app access after setup.