Clickup Intelligence MCP Server

@chykalophia/clickup-intelligence-mcp-server npm v5.0.1

Published by @chykalophia — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Advanced project management intelligence and workflow optimization for ClickUp - AI-powered analytics, smart planning, and automation

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 93/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

high Dynamic code execution in server code (build/tools/real-time-tools.js)MTC-SRC-001

In the server's implementation (`build/tools/real-time-tools.js:134`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: const conditionFn = new Function('_event', `return ${params.condition}`); // eslint-disable-next-line no-new

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server build/tools/real-time-tools.js

Tools 21

Each tool and what it can reach — statically extracted from the published source.

  • clickup_process_webhooknetwork egress
  • clickup_add_processing_ruleno sensitive capability
  • clickup_analyze_burnout_riskno sensitive capability
  • clickup_analyze_project_healthno sensitive capability
  • clickup_analyze_task_complexityno sensitive capability
  • clickup_analyze_team_velocityno sensitive capability
  • clickup_analyze_team_workloadno sensitive capability
  • clickup_analyze_workflow_patternsno sensitive capability
  • clickup_decompose_taskno sensitive capability
  • clickup_forecast_team_capacityno sensitive capability
Show 11 more tools ↓
  • clickup_get_cached_taskno sensitive capability
  • clickup_get_decomposition_templatesno sensitive capability
  • clickup_get_realtime_metricsno sensitive capability
  • clickup_model_team_capacityno sensitive capability
  • clickup_optimize_integrationsno sensitive capability
  • clickup_optimize_sprint_tasksno sensitive capability
  • clickup_optimize_task_assignmentno sensitive capability
  • clickup_plan_smart_sprintno sensitive capability
  • clickup_recommend_automationsno sensitive capability
  • clickup_start_realtime_engineno sensitive capability
  • clickup_stop_realtime_engineno sensitive capability

What this scan could not see

Versions 2

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v5.0.1 latest A 93/100 1 1.13.0 2026-09-07
v4.2.7 A 93/100 1 1.12.1 2026-08-03

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/chykalophia-clickup-intelligence-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/chykalophia-clickup-intelligence-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/chykalophia-clickup-intelligence-mcp-server"><img src="https://mcptrustchecker.com/registry/chykalophia-clickup-intelligence-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/chykalophia-clickup-intelligence-mcp-server/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @chykalophia/clickup-intelligence-mcp-server --online

Use the free API → How scoring works

More in Productivity & Workflow