Clockify (tracegazer) MCP Server
clockify-mcp
PyPI
v0.3.2
Published by tracegazer — 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.
Full-coverage Clockify MCP — 112 tools across 18 domains (incl. invoices, scheduling, time-off & approvals), native OpenTelemetry observability, and a 3-tier read/time-tracking/full access model.
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 − 4 = 96. 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 |
|---|---|
| −3 | capability blast radius (moderate) — 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
medium Untrusted input can drive an external actionMTC-FLOW-005
Untrusted-input tools ([download_expense_receipt]) co-exist with external-action tools ([create_webhook, update_webhook, delete_webhook, generate_webhook_token]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.
Evidence: untrusted [download_expense_receipt] → sinks [create_webhook, update_webhook, delete_webhook, generate_webhook_token]
Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.
Location: flow download_expense_receipt → create_webhook
Tools 112
Each tool and what it can reach — statically extracted from the published source.
create_webhooknetwork egressdelete_webhooknetwork egressdownload_expense_receiptingests untrusted inputgenerate_webhook_tokennetwork egressupdate_webhooknetwork egressadd_invoice_itemno sensitive capabilityadd_invoice_paymentno sensitive capabilityapprove_time_off_requestno sensitive capabilityarchive_expense_categoryno sensitive capabilitybulk_update_time_entriesno sensitive capability
Show 102 more tools ↓
change_invoice_statusno sensitive capabilitycopy_assignmentno sensitive capabilitycreate_assignmentno sensitive capabilitycreate_clientno sensitive capabilitycreate_expenseno sensitive capabilitycreate_expense_categoryno sensitive capabilitycreate_holidayno sensitive capabilitycreate_invoiceno sensitive capabilitycreate_projectno sensitive capabilitycreate_shared_reportno sensitive capabilitycreate_tagno sensitive capabilitycreate_taskno sensitive capabilitycreate_time_entryno sensitive capabilitycreate_time_entry_for_userno sensitive capabilitycreate_time_off_policyno sensitive capabilitycreate_time_off_requestno sensitive capabilitycreate_workspace_custom_fieldno sensitive capabilitydelete_assignmentno sensitive capabilitydelete_clientno sensitive capabilitydelete_expenseno sensitive capabilitydelete_expense_categoryno sensitive capabilitydelete_holidayno sensitive capabilitydelete_invoiceno sensitive capabilitydelete_invoice_paymentno sensitive capabilitydelete_projectno sensitive capabilitydelete_shared_reportno sensitive capabilitydelete_tagno sensitive capabilitydelete_taskno sensitive capabilitydelete_time_entryno sensitive capabilitydelete_workspace_custom_fieldno sensitive capabilityduplicate_invoiceno sensitive capabilityduplicate_time_entryno sensitive capabilityexport_reportno sensitive capabilityfind_user_team_managerno sensitive capabilitygenerate_attendance_reportno sensitive capabilitygenerate_detailed_reportno sensitive capabilitygenerate_expense_reportno sensitive capabilitygenerate_summary_reportno sensitive capabilitygenerate_weekly_reportno sensitive capabilityget_clientno sensitive capabilityget_current_userno sensitive capabilityget_expenseno sensitive capabilityget_invoiceno sensitive capabilityget_invoice_paymentsno sensitive capabilityget_projectno sensitive capabilityget_project_scheduling_totalsno sensitive capabilityget_shared_reportno sensitive capabilityget_tagno sensitive capabilityget_taskno sensitive capabilityget_time_entryno sensitive capabilityget_time_off_policyno sensitive capabilityget_user_member_profileno sensitive capabilityget_user_scheduling_totalsno sensitive capabilityget_webhookno sensitive capabilityget_webhook_logsno sensitive capabilityget_workspaceno sensitive capabilityimport_invoice_itemsno sensitive capabilitylist_approval_requestsno sensitive capabilitylist_clientsno sensitive capabilitylist_expense_categoriesno sensitive capabilitylist_expensesno sensitive capabilitylist_holidaysno sensitive capabilitylist_holidays_in_periodno sensitive capabilitylist_invoicesno sensitive capabilitylist_project_custom_fieldsno sensitive capabilitylist_projectsno sensitive capabilitylist_scheduled_assignmentsno sensitive capabilitylist_shared_reportsno sensitive capabilitylist_tagsno sensitive capabilitylist_tasksno sensitive capabilitylist_time_entriesno sensitive capabilitylist_time_off_balances_by_policyno sensitive capabilitylist_time_off_balances_by_userno sensitive capabilitylist_time_off_policiesno sensitive capabilitylist_time_off_requestsno sensitive capabilitylist_user_groupsno sensitive capabilitylist_usersno sensitive capabilitylist_webhooksno sensitive capabilitylist_workspace_custom_fieldsno sensitive capabilitylist_workspacesno sensitive capabilitypublish_assignmentsno sensitive capabilityreject_time_off_requestno sensitive capabilityremove_project_custom_fieldno sensitive capabilityresubmit_approval_entriesno sensitive capabilityset_project_custom_fieldno sensitive capabilitystop_running_timerno sensitive capabilitysubmit_approval_requestno sensitive capabilitysubmit_approval_request_for_userno sensitive capabilityupdate_approval_requestno sensitive capabilityupdate_assignmentno sensitive capabilityupdate_clientno sensitive capabilityupdate_expenseno sensitive capabilityupdate_expense_categoryno sensitive capabilityupdate_holidayno sensitive capabilityupdate_invoiceno sensitive capabilityupdate_projectno sensitive capabilityupdate_shared_reportno sensitive capabilityupdate_tagno sensitive capabilityupdate_taskno sensitive capabilityupdate_time_entryno sensitive capabilityupdate_workspace_custom_fieldno sensitive capabilitywithdraw_time_off_requestno sensitive capability
Toxic flows 1
Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).
What this scan could not see
- Tools were statically extracted from the published source (112 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>".
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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.3.2 latest |
A 96/100 | 1 | 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.
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 clockify-mcp --online --registry pypiOther implementations of Clockify 10
Independent packages implementing the same tool, scanned with the same engine. Compare all 11 side by side →
MCP Server for Clockify Time Tracking API
Feature-rich MCP server for Clockify API integration with full CRUD operations
A Model Context Protocol (MCP) server that provides seamless integration with Clockify time tracking API. This server enables AI assistants to interact with Clockify to manage time entries, projects, tasks, and workspaces.
MCP server for Clockify time tracking API - track time, manage projects, and generate reports
MCP server for the Clockify time-tracking API (curated tools + generic passthrough)
Model Context Protocol server for Clockify time tracking integration. Enables Claude AI to directly manage time entries, projects, tasks, and generate reports through Clockify's API.
More in Lifestyle & Local
MCP server for Australian address search and validation via Addressr
Admissions data & match scores for law, medical, dental, MBA, pharmacy, vet, optometry schools
Live AI data for agents: model releases, regulations (EU AI Act), GenAI glossary, daily news.
AirTreks MCP Server — complex flight routing intelligence for AI agents. Plan multi-city trips, validate alliance routings, get carrier recommendations, and create trip ideas.
Physician-reviewed medical opinions and prescriptions for AI agents.
Thin MCP server + CLI that proxy the atrium /api/v1 observability surface using an oc_live_ Bearer key. Talks HTTP only — no Convex imports.