Ticktick (karbassi) MCP Server

mcp-ticktick PyPI v0.1.2

Published by karbassi — 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 for TickTick task management

Trust grade
A
99/100
Last scanned get badge →
Trust
A · 99/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
Minimal
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 = 99/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 − 1 = 99. 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
−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 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 45

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

  • add_filterno sensitive capability
  • add_folderno sensitive capability
  • add_habitno sensitive capability
  • add_projectno sensitive capability
  • add_tagsno sensitive capability
  • add_taskno sensitive capability
  • archive_habitsno sensitive capability
  • checkin_habitno sensitive capability
  • complete_taskno sensitive capability
  • delete_filtersno sensitive capability
Show 35 more tools ↓
  • delete_foldersno sensitive capability
  • delete_habitsno sensitive capability
  • delete_projectno sensitive capability
  • delete_tagsno sensitive capability
  • delete_taskno sensitive capability
  • edit_filterno sensitive capability
  • edit_habitno sensitive capability
  • edit_projectno sensitive capability
  • edit_tagno sensitive capability
  • edit_taskno sensitive capability
  • focus_logno sensitive capability
  • focus_saveno sensitive capability
  • focus_statsno sensitive capability
  • focus_statusno sensitive capability
  • focus_timelineno sensitive capability
  • get_projectno sensitive capability
  • get_taskno sensitive capability
  • habit_logno sensitive capability
  • list_calendarsno sensitive capability
  • list_eventsno sensitive capability
  • list_filtersno sensitive capability
  • list_foldersno sensitive capability
  • list_habitsno sensitive capability
  • list_projectsno sensitive capability
  • list_tagsno sensitive capability
  • list_tasksno sensitive capability
  • list_trashno sensitive capability
  • manage_habit_sectionsno sensitive capability
  • merge_tagsno sensitive capability
  • move_taskno sensitive capability
  • rename_folderno sensitive capability
  • rename_tagno sensitive capability
  • set_subtaskno sensitive capability
  • sync_accountno sensitive capability
  • unparent_taskno sensitive capability

What this scan could not see

Versions 1

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
v0.1.2 latest A 99/100 0 1.13.0 2026-08-25

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 · 99/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mcp-ticktick/badge.svg)](https://mcptrustchecker.com/registry/mcp-ticktick)
HTML
<a href="https://mcptrustchecker.com/registry/mcp-ticktick"><img src="https://mcptrustchecker.com/registry/mcp-ticktick/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mcp-ticktick/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 mcp-ticktick --online --registry pypi

Use the free API → How scoring works

Other implementations of Ticktick 6

Independent packages implementing the same tool, scanned with the same engine. Compare all 7 side by side →

More in Productivity & Workflow