Home / MCP registry index / io.usefulapi/clockify
Clockify MCP by usefulapi
io.usefulapi/clockify in the official MCP registry.
Endpoint https://clockify.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Track time in Clockify: time entries, projects, clients, tags and reports; start, stop and log time.
We read its 21 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
clockify_get_current_user clockify_list_workspaces clockify_list_users clockify_list_clients clockify_list_projects clockify_get_project clockify_list_tasks clockify_list_tags clockify_list_time_entries clockify_get_time_entry clockify_get_running_timer clockify_summary_report clockify_detailed_report clockify_create_time_entry clockify_stop_timer clockify_update_time_entry clockify_delete_time_entry clockify_create_project clockify_create_task clockify_create_client clockify_create_tag
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-clockify)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.