MCP Server for ZenTao bug management with CAS SSO login
from $14/mo
Nothing to run from here
Clickup Intelligence is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
Open Installation—
p95 latency
—
call success
local
runs on your machine
—
calls last 7d
What it does
Advanced project management intelligence and workflow optimization for ClickUp - AI-powered analytics, smart planning, and automation
Quickstart
# 1 — run it from where its publisher ships it
npx -y @chykalophia/clickup-intelligence-mcp-server
# 2 — the plan is chosen at checkout, in the browser
# 3 — ask your agent something
> Advanced project management intelligence and workflow optimization for ClickUp - AI-powered analytics, smart planning, and automation
Publishernot claimed
CHAll 1 server
@chykalophia1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Clickup Intelligence as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It is scanned, signed and pinned to the version you choose — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add clickup-intelligence-mcp -- npx -y @chykalophia/clickup-intelligence-mcp-serverReconnect, or start a new session, and the tools appear in the model’s tool list.
This is a paid listing, so the CLI has to be signed in and the licence has to be on your account — how the login works. Until then the install stops with the price rather than half-writing a config entry.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
160 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Retrieve chat channels in a workspace with cursor pagination and optional filtering by channel type, follower status, and activity.
Takes no parameters.
Example callreturns →
Create a new chat channel in a workspace with specified name, description, topic, members, and visibility.
Takes no parameters.
Example callreturns →
Create a chat channel on a specific space, folder, or list for contextual discussions. The channel name is derived from the location.
Takes no parameters.
Example callreturns →
Create a direct message channel with up to 15 users. Provide no user IDs to create a self-DM.
Takes no parameters.
Example callreturns →
Retrieve detailed information about a specific chat channel by its ID.
Takes no parameters.
Example callreturns →
Update a chat channel
Takes no parameters.
Example callreturns →
Retrieve followers of a chat channel who receive notifications about channel activity (cursor-paginated).
Takes no parameters.
Example callreturns →
Retrieve members of a chat channel (cursor-paginated).
Takes no parameters.
Example callreturns →
Retrieve messages from a chat channel with cursor pagination.
Takes no parameters.
Example callreturns →
Send a message to a chat channel. Mentions can be embedded in markdown content.
Takes no parameters.
Example callreturns →
Update the content, assignee, or resolved state of an existing chat message.
Takes no parameters.
Example callreturns →
Delete a chat message. This action cannot be undone.
Takes no parameters.
Example callreturns →
Retrieve replies to a specific chat message (cursor-paginated).
Takes no parameters.
Example callreturns →
Create a reply to a specific chat message.
Takes no parameters.
Example callreturns →
Retrieve reactions on a specific chat message (cursor-paginated).
Takes no parameters.
Example callreturns →
Add a reaction to a chat message using an emoji name (e.g.
Takes no parameters.
Example callreturns →
Remove a reaction from a chat message by emoji name.
Takes no parameters.
Example callreturns →
Retrieve users tagged/mentioned in a specific chat message (cursor-paginated).
Takes no parameters.
Example callreturns →
Search for chat channels by name within a workspace (client-side filtering over the channel list).
Takes no parameters.
Example callreturns →
RAW API TEST: Create a comment bypassing ALL MCP processing to isolate duplication issue. Returns raw ClickUp API response.
Takes no parameters.
Example callreturns →
Get comments for a ClickUp task. Returns comment details including text, author, and timestamps with enhanced markdown styling.
Takes no parameters.
Example callreturns →
Create a new comment on a ClickUp task using structured array format. Supports optional assignee and notification settings. Supports @mentions via tag blocks ({type:
Takes no parameters.
Example callreturns →
Get comments for a ClickUp chat view. Returns comment details with pagination support.
Takes no parameters.
Example callreturns →
Create a new comment in a ClickUp chat view. Supports notification settings. Supports GitHub Flavored Markdown in comment text, or structured comment blocks for @mentions. Provide either comment_text or comment.
Takes no parameters.
Example callreturns →
Get comments for a ClickUp list. Returns comment details with pagination support.
Takes no parameters.
Example callreturns →
Create a new comment on a ClickUp list. Supports optional assignee and notification settings. Supports GitHub Flavored Markdown in comment text, or structured comment blocks for @mentions. Provide either comment_text or comment.
Takes no parameters.
Example callreturns →
Update an existing ClickUp comment
Takes no parameters.
Example callreturns →
Delete a comment from ClickUp.
Takes no parameters.
Example callreturns →
Get threaded comments (replies) for a parent comment. Returns comment details with pagination support.
Takes no parameters.
Example callreturns →
Create a new threaded comment (reply) to a parent comment. Supports notification settings. Supports GitHub Flavored Markdown in comment text, or structured comment blocks for @mentions. Provide either comment_text or comment.
Takes no parameters.
Example callreturns →
Get time entries for a team with filtering options. Supports filtering by date range, user, task, and project.
Takes no parameters.
Example callreturns →
Create a new time entry for time tracking. Can be used for manual time logging or creating timer-based entries.
Takes no parameters.
Example callreturns →
Update an existing time entry. Can modify description, times, billable status, and associated task.
Takes no parameters.
Example callreturns →
Delete a time entry from ClickUp. This action cannot be undone.
Takes no parameters.
Example callreturns →
Get a single time entry by its ID.
Takes no parameters.
Example callreturns →
Get the change history of a time entry. Useful for auditing who edited tracked time.
Takes no parameters.
Example callreturns →
Get all tags that have been used on time entries in a Workspace.
Takes no parameters.
Example callreturns →
Add tags to one or more time entries in bulk.
Takes no parameters.
Example callreturns →
Get the currently running time entry (timer) for the authenticated user, or for a specific user via assignee. The ClickUp API returns at most one running timer per user.
Takes no parameters.
Example callreturns →
Start a timer for the authenticated user. Optionally associate with a task and set description, billable status, and tags.
Takes no parameters.
Example callreturns →
Stop the running timer for the authenticated user. Returns the stopped time entry.
Takes no parameters.
Example callreturns →
Get time tracking summary and analytics. Provides aggregated time data with breakdowns by user and task.
Takes no parameters.
Example callreturns →
Create a new time entry and immediately start the timer. Convenient for starting time tracking in one step.
Takes no parameters.
Example callreturns →
Format a duration from milliseconds to human-readable format. Useful for displaying time tracking data.
Takes no parameters.
Example callreturns →
Upload a file to a ClickUp task as an attachment. Provide the file as base64 data (file_data), a local file path (file_path), or a URL to fetch (file_url). Files stored in the cloud must be fetched first; ClickUp only accepts the binary upload.
Takes no parameters.
Example callreturns →
List attachments for a task or a File custom field using the ClickUp v3 API. Results are cursor-paginated; pass next_cursor from a previous response to fetch the next page.
Takes no parameters.
Example callreturns →
Create multiple tasks in a ClickUp list in a single operation. More efficient than creating tasks individually.
Takes no parameters.
Example callreturns →
Update multiple tasks in ClickUp in a single operation. More efficient than updating tasks individually.
Takes no parameters.
Example callreturns →
⚠️ DESTRUCTIVE: Delete multiple tasks from ClickUp in a single operation. This action cannot be undone and will permanently remove all specified tasks.
Takes no parameters.
Example callreturns →
⚠️ DESTRUCTIVE: Delete a subtask from ClickUp. This action cannot be undone and will permanently remove the subtask.
Takes no parameters.
Example callreturns →
Merge multiple tasks into a single task using ClickUp
Takes no parameters.
Example callreturns →
Create a new checklist in a ClickUp task. Returns the created checklist details.
Takes no parameters.
Example callreturns →
Update an existing ClickUp checklist
Takes no parameters.
Example callreturns →
Delete a checklist from a ClickUp task. Removes the checklist and all its items.
Takes no parameters.
Example callreturns →
Create a new item in a ClickUp checklist. Supports optional assignee and resolved status (resolved is applied via a follow-up update, since the create endpoint does not accept it). Returns the full parent checklist including all items.
Takes no parameters.
Example callreturns →
Update an existing ClickUp checklist item
Takes no parameters.
Example callreturns →
Delete an item from a ClickUp checklist.
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Set a custom field value on a ClickUp task. ${VALUE_FORMAT_GUIDE}
Takes no parameters.
Example callreturns →
Remove a custom field value from a ClickUp task. This clears the field value but keeps the field definition.
Takes no parameters.
Example callreturns →
Get a custom field value from a ClickUp task. Returns the current value and field information.
Takes no parameters.
Example callreturns →
Set multiple custom field values on a ClickUp task in a single operation. More efficient than setting values individually. ${VALUE_FORMAT_GUIDE}
Takes no parameters.
Example callreturns →
Get all custom field values for a ClickUp task. Returns all field values with their definitions.
Takes no parameters.
Example callreturns →
Validate a custom field value against its field type and configuration. Useful for checking values before setting them. ${VALUE_FORMAT_GUIDE}
Takes no parameters.
Example callreturns →
Create a dependency between two tasks. Provide exactly one of depends_on (this task is WAITING ON the other task) or dependency_of (this task is BLOCKING the other task).
Takes no parameters.
Example callreturns →
Get a task
Takes no parameters.
Example callreturns →
Delete a dependency between two tasks. Provide exactly one of depends_on or dependency_of to identify which dependency to remove.
Takes no parameters.
Example callreturns →
Link two tasks together (a non-blocking
Takes no parameters.
Example callreturns →
Remove a link between two tasks. Returns the updated task.
Takes no parameters.
Example callreturns →
Build a dependency graph for a task by traversing related tasks (computed client-side from task data; issues one Get Task request per task in the graph).
Takes no parameters.
Example callreturns →
Check for circular or duplicate dependencies around a task, optionally including proposed new dependencies (computed client-side from task data).
Takes no parameters.
Example callreturns →
Create or delete multiple dependencies in one call (executed as individual API requests; results are reported per item).
Takes no parameters.
Example callreturns →
Get the content of a specific ClickUp doc. Returns combined content from all pages in the doc.
Takes no parameters.
Example callreturns →
Search for docs in a ClickUp workspace by name (matched client-side; the ClickUp API has no full-text doc search). Use
Takes no parameters.
Example callreturns →
Get all docs from a ClickUp workspace. Supports pagination and filtering for deleted/archived docs.
Takes no parameters.
Example callreturns →
Get the pages of a specific ClickUp doc. Returns page content in the requested format (markdown or plain text).
Takes no parameters.
Example callreturns →
List the page hierarchy of a ClickUp doc (page IDs and names, without content). Much cheaper than clickup_get_doc_pages for large docs.
Takes no parameters.
Example callreturns →
Get detailed information about a specific ClickUp document including metadata.
Takes no parameters.
Example callreturns →
Create a new document in a ClickUp workspace. Placement inside the hierarchy (space, folder, list) is set via the parent fields. If content is supplied, it is added as the first page. Note: the ClickUp public API has no doc update/delete, page delete, sharing, or template endpoints.
Takes no parameters.
Example callreturns →
Create a new page in a ClickUp document. Supports markdown and plain text content, an optional sub_title, and nesting under a parent page.
Takes no parameters.
Example callreturns →
Update an existing page in a ClickUp document. Can update name, sub_title, and content. content_edit_mode controls whether content replaces, appends to, or prepends to the existing page content.
Takes no parameters.
Example callreturns →
Get goals for a team with optional filtering. Returns goal details including progress, targets, and team members.
Takes no parameters.
Example callreturns →
Create a new goal with targets and deadlines. Supports team collaboration with multiple owners.
Takes no parameters.
Example callreturns →
Update an existing goal. Can modify name, description, due date, owners, and color.
Takes no parameters.
Example callreturns →
Delete a goal from ClickUp. This action cannot be undone and will remove all associated targets.
Takes no parameters.
Example callreturns →
Get detailed information about a specific goal including all targets and progress data.
Takes no parameters.
Example callreturns →
Create a target (key result) for a goal. Supports different target types: number, currency, boolean, percentage, and automatic (tracked via linked tasks/lists).
Takes no parameters.
Example callreturns →
Update an existing goal target (key result). Sets the current progress value and an optional note.
Takes no parameters.
Example callreturns →
Delete a target (key result) from a goal. This action cannot be undone.
Takes no parameters.
Example callreturns →
Get comprehensive goal analytics and summary for a team. Includes progress statistics, status breakdown, and upcoming deadlines.
Takes no parameters.
Example callreturns →
Create a number-based goal with a target. Convenient helper for creating numeric goals like task counts or metrics.
Takes no parameters.
Example callreturns →
Create a currency-based goal with a monetary target. Convenient helper for creating revenue or budget goals.
Takes no parameters.
Example callreturns →
Format goal progress information for human-readable display. Useful for reporting and dashboards.
Takes no parameters.
Example callreturns →
Get lists from a ClickUp folder or space. For a space, returns both folderless lists and lists inside the space\
Takes no parameters.
Example callreturns →
Get folders from a ClickUp space. Returns folder details including the lists inside each folder.
Takes no parameters.
Example callreturns →
Get details about a specific ClickUp folder including its name, statuses, and lists.
Takes no parameters.
Example callreturns →
Create a new folder in a ClickUp space with the specified name.
Takes no parameters.
Example callreturns →
Update an existing ClickUp folder
Takes no parameters.
Example callreturns →
Delete a folder from ClickUp. Removes the folder and its contents.
Takes no parameters.
Example callreturns →
Get lists that are not in any folder within a ClickUp space.
Takes no parameters.
Example callreturns →
Create a new list in a ClickUp folder or space with the specified name.
Takes no parameters.
Example callreturns →
Create a new list directly in a ClickUp space without placing it in a folder.
Takes no parameters.
Example callreturns →
Get details about a specific ClickUp list including its name and content.
Takes no parameters.
Example callreturns →
Update an existing ClickUp list. All fields are optional; only provided fields are changed.
Takes no parameters.
Example callreturns →
Get the members (users) who have access to a specific ClickUp list.
Takes no parameters.
Example callreturns →
⚠️ DESTRUCTIVE: Delete a list from ClickUp. This action cannot be undone and will permanently remove the list and all its tasks.
Takes no parameters.
Example callreturns →
Create a new list in a ClickUp folder using an existing template.
Takes no parameters.
Example callreturns →
Create a new list in a ClickUp space using an existing template.
Takes no parameters.
Example callreturns →
Create a new folder (with its nested lists and tasks) in a ClickUp space using an existing folder template.
Takes no parameters.
Example callreturns →
Get the folder templates available in a ClickUp workspace. Use the returned template IDs with clickup_create_folder_from_template.
Takes no parameters.
Example callreturns →
Get spaces from a ClickUp workspace. Returns space details including name, settings, and features.
Takes no parameters.
Example callreturns →
Get details about a specific ClickUp space. Returns space name, settings, features, and metadata.
Takes no parameters.
Example callreturns →
Create a new space in a ClickUp workspace. Optionally configure multiple assignees and features (due dates, time tracking, tags, time estimates, checklists, custom fields).
Takes no parameters.
Example callreturns →
Update an existing ClickUp space
Takes no parameters.
Example callreturns →
⚠️ DESTRUCTIVE: Delete a space from ClickUp. This action cannot be undone and will permanently remove the space and ALL of its contents, including folders, lists, and tasks.
Takes no parameters.
Example callreturns →
Get the task tags defined in a ClickUp space. Returns tag names and foreground/background colors.
Takes no parameters.
Example callreturns →
Create a new task tag in a ClickUp space with an optional foreground and background color.
Takes no parameters.
Example callreturns →
Edit an existing task tag in a ClickUp space. Update the tag
Takes no parameters.
Example callreturns →
⚠️ DESTRUCTIVE: Delete a task tag from a ClickUp space. The tag is removed from the space and from all tasks that use it.
Takes no parameters.
Example callreturns →
Get tasks from a ClickUp list. Returns task details including name, description, assignees, and status.
Takes no parameters.
Example callreturns →
Get detailed information about a specific ClickUp task. Returns comprehensive task data including description, assignees, status, and dates.
Takes no parameters.
Example callreturns →
Create a new task in a ClickUp list with specified properties like name, description, assignees, status, and dates. Supports GitHub Flavored Markdown in description field.
Takes no parameters.
Example callreturns →
Update an existing ClickUp task
Takes no parameters.
Example callreturns →
⚠️ DESTRUCTIVE: Delete a task from ClickUp. This action cannot be undone and will permanently remove the task and all its data.
Takes no parameters.
Example callreturns →
Add an existing task to a ClickUp list.
Takes no parameters.
Example callreturns →
Remove a task from a ClickUp list without deleting the task.
Takes no parameters.
Example callreturns →
Get a ClickUp task
Takes no parameters.
Example callreturns →
Get time-in-status data for multiple ClickUp tasks in one call (2–100 task IDs). Returns an object keyed by task_id with { current_status, status_history }. Requires the workspace\
Takes no parameters.
Example callreturns →
Search tasks across an entire ClickUp workspace (team) with filters for statuses, assignees, tags, lists, spaces, and date ranges. Results are paginated (100 tasks per page).
Takes no parameters.
Example callreturns →
Add a tag to an existing ClickUp task. The tag must already exist in the space.
Takes no parameters.
Example callreturns →
Remove a tag from a ClickUp task without deleting the tag itself.
Takes no parameters.
Example callreturns →
Create a new task in a ClickUp list from a saved task template. Template contents such as checklists and subtasks are included.
Takes no parameters.
Example callreturns →
Create a new view in a ClickUp Workspace (team), space, folder, or list. Supports the API view types: list, board, calendar, table, timeline, workload, activity, map, conversation (chat), and gantt.
Takes no parameters.
Example callreturns →
Get all views for a Workspace (team), space, folder, or list. The API returns all views; the optional type filter is applied client-side.
Takes no parameters.
Example callreturns →
Get detailed information about a specific view by its ID.
Takes no parameters.
Example callreturns →
Update an existing view
Takes no parameters.
Example callreturns →
Delete a view from ClickUp. This action cannot be undone.
Takes no parameters.
Example callreturns →
Set or update filters for a view. Filters determine which tasks are visible in the view. Each condition uses {field, op, values} with ClickUp operator tokens (EQ, ANY, ALL, NOT ANY, ...).
Takes no parameters.
Example callreturns →
Set or update the grouping configuration for a view. Grouping organizes tasks into sections; collapsed is an array of collapsed group IDs.
Takes no parameters.
Example callreturns →
Set or update sorting configuration for a view. Sorting determines the order of tasks.
Takes no parameters.
Example callreturns →
Update view display settings such as show_task_locations, show_subtasks, show_assignees, show_images, collapse_empty_columns, and the me_* filters. Provided settings are merged with the current ones.
Takes no parameters.
Example callreturns →
Get tasks that are visible in a specific view, respecting the view
Takes no parameters.
Example callreturns →
Create a duplicate of an existing view with a new name. The API has no duplicate endpoint, so the source view
Takes no parameters.
Example callreturns →
Get the Custom Fields accessible in a Workspace (team), space, folder, or list (Get Accessible Custom Fields endpoint). Note: built-in fields such as status, assignee, dueDate, and priority are not included.
Takes no parameters.
Example callreturns →
Create a new webhook in a ClickUp workspace. Webhooks allow real-time notifications when events occur. The response includes the webhook secret (returned only at creation) — store it for signature verification.
Takes no parameters.
Example callreturns →
Get all webhooks for a workspace, including per-webhook health info (status, fail_count). Optional status/event type filters are applied client-side (the ClickUp API does not support filtering).
Takes no parameters.
Example callreturns →
Get detailed information about a specific webhook by its ID, including health info (status, fail_count). The ClickUp API has no single-webhook endpoint, so this looks the webhook up in the workspace list.
Takes no parameters.
Example callreturns →
Update an existing webhook
Takes no parameters.
Example callreturns →
Delete a webhook from ClickUp. This will stop all notifications to the webhook endpoint.
Takes no parameters.
Example callreturns →
Validate the HMAC-SHA256 signature of a webhook payload to ensure authenticity. The payload must be the raw request body string exactly as received; the signature is the bare hex digest from ClickUp
Takes no parameters.
Example callreturns →
Process an incoming ClickUp webhook delivery ({webhook_id, event, task_id, history_items}) and extract structured information about the event. The signature is verified against the raw body string before parsing.
Takes no parameters.
Example callreturns →
Get information about seats (user licenses) in a ClickUp workspace. Returns details about seat allocation and availability.
Takes no parameters.
Example callreturns →
Get a list of all ClickUp workspaces accessible to the authenticated user. Returns workspace IDs, names, and metadata.
Takes no parameters.
Example callreturns →
Get details about the currently authenticated ClickUp user (whoami). Returns the user ID, username, email, and profile information. Useful for resolving
Takes no parameters.
Example callreturns →
Get the User Groups (ClickUp
Takes no parameters.
Example callreturns →
Get the current pricing plan of a ClickUp workspace. Returns the plan ID and name (e.g. Free Forever, Unlimited, Business).
Takes no parameters.
Example callreturns →
Get the Custom Roles defined in a ClickUp workspace. Useful for resolving the custom_role IDs referenced on workspace members.
Takes no parameters.
Example callreturns →
🚀 EFFICIENT: Find chat channels across workspaces without hierarchical navigation. More efficient than get_workspaces → get_spaces → get_views.
Takes no parameters.
Example callreturns →
📊 ANALYZER: Analyze your planned workflow and get efficiency suggestions. Helps you choose the most efficient tool sequence.
Takes no parameters.
Example callreturns →
📊 OVERVIEW: Get a comprehensive workspace overview in a single call. More efficient than multiple navigation calls.
Takes no parameters.
Example callreturns →
Startermost installed
$10 / month
- 8,000 calls a month, included
- 96 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
Team
$35 / month
- 40,000 calls a month, included
- 480 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
Business
$75 / month
- 180,000 calls a month, included
- 2,160 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
No call is billed on its own, and this plan carries no monthly call limit. $10 a month covers every tool at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: $8.42
$16.58 left
ATrust score 93 / 100
Release 5.0.1 · scanned 25 Aug 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 1 capability
Capabilityhigh
Coveragesource
Verificationrepo
Surface digestf817bc0da5d7cebb538a871a588413c3da1c433d8a7017a3e4733060df023fe1
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (21 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| clickup_analyze_project_health | no tags | |
| clickup_plan_smart_sprint | no tags | |
| clickup_analyze_team_velocity | no tags | |
| clickup_model_team_capacity | no tags | |
| clickup_optimize_sprint_tasks | no tags | |
| clickup_decompose_task | no tags | |
| clickup_analyze_task_complexity | no tags | |
| clickup_get_decomposition_templates | no tags | |
| clickup_analyze_team_workload | no tags | |
| clickup_optimize_task_assignment | no tags | |
| clickup_analyze_burnout_risk | no tags | |
| clickup_forecast_team_capacity | no tags | |
| clickup_analyze_workflow_patterns | no tags | |
| clickup_recommend_automations | no tags | |
| clickup_optimize_integrations | no tags | |
| clickup_start_realtime_engine | no tags | |
| clickup_process_webhook | external-sink | |
| clickup_add_processing_rule | no tags | |
| clickup_get_realtime_metrics | no tags | |
| clickup_get_cached_task | no tags | |
| clickup_stop_realtime_engine | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestf817bc0da5d7cebb
Scanned2026-08-25
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Pinned to 5.0.1 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
5.0.1
undated
installedNo release note was published with this version.
—
no reviews yet
Reviews are earned
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Reviews are earned
Writing one takes an account with at least 50 real tool calls against Clickup Intelligence in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes an account with 50 real tool calls against it.