mcp-clickup-server
npm
v1.4.1
Published by bit9-a — 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.
MCP server para integrar ClickUp con OpenCode/Gentle AI — creá tareas y explorá tu workspace desde lenguaje natural
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 − 1.2 = 99. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −1.2 | Package runs install-time scripts MTC-SUP-010 | supply-chain |
2. Client adoption risk — 99 − 1 = 98. 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:
| Points | Adoption-risk factor |
|---|---|
| −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.
In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/setup.mjs:136`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. 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 response = await fetch(`https://api.clickup.com/api/v2${endpoint}`, { headers: { Authorization: apiKey }, }
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 scripts/setup.mjs
In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/setup.mjs:7`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: { execSync } from "node:child_process"; import { homedir } from "node:os"; import { TARGET_REGISTRY, ROOT } from "./ide
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 scripts/setup.mjs
"mcp-clickup-server" executes postinstall script(s) at install time. An install hook runs at install time; most are routine build/setup, but review what it does before trusting it.
Evidence: test -f dist/index.js || npx tsc
Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.
Location: package mcp-clickup-server
Each tool and what it can reach — statically extracted from the published source.
add_commentno sensitive capabilitycreate_listno sensitive capabilitycreate_spaceno sensitive capabilitycreate_taskno sensitive capabilitydelete_taskno sensitive capabilityget_authenticated_userno sensitive capabilityget_custom_fieldsno sensitive capabilityget_foldersno sensitive capabilityget_list_statusesno sensitive capabilityget_listsno sensitive capabilityget_project_configno sensitive capabilityget_spacesno sensitive capabilityget_taskno sensitive capabilityget_task_commentsno sensitive capabilityget_tasksno sensitive capabilityget_workspace_membersno sensitive capabilityget_workspacesno sensitive capabilityupdate_taskno sensitive capabilityScan 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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.4.1 latest |
A 98/100 | 3 | 1.13.0 | 2026-09-07 |
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.
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 mcp-clickup-server --online
Independent packages implementing the same tool, scanned with the same engine. Compare all 20 side by side →
ClickUp MCP Server - Powering AI Agents with full ClickUp task, document, and chat management capabilities.
A Model Context Protocol (MCP) server that provides a standardized interface for AI assistants to interact with the ClickUp API
ClickUp MCP Server for AI assistants - Model Context Protocol implementation for ClickUp task management
Optimized ClickUp MCP Server - High-performance AI integration with consolidated tools and response optimization
A Model Context Protocol server for the ClickUp API.
Optimized ClickUp MCP Server - High-performance AI integration with consolidated tools and response optimization
Free public tax reference data — GST/VAT, income, company and capital-gains tax rules for 50+ countries.
The approval gate for unattended UCP buying agents — a policy/approval MCP proxy in front of a merchant's UCP checkout endpoint.
Autotask PSA MCP server. Generic entity query/get/create/update across the full REST API plus convenience tools for tickets, companies, contacts, projects, tasks and time entries. AI-safe with readonly mode and destructive-action confirmation. stdio + opt
MCP server for B2C Commerce developer experience tools
Search, compare and contact real-world companies through a public MCP business directory.
Norwegian business register (Brønnøysundregistrene) as an MCP server — companies, roles, subunits and annual accounts, with the register's silent traps encoded as guards.