MCP servers observed by Lowdown
ai.timix/time-tracking MCP server: daily status and tool changes
Answered initialize and tools/list on all 3 checks recorded in the last 30 days (2026-11-10 to 2026-11-16) (Lowdown checks this server every 3 days); 115 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-10; tool definitions last changed on 2026-11-13 after 3 days without change; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ai.timix/time-tracking
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ai.timix/time-tracking?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-16: the server answered initialize and tools/list.
- Observed days in the last 30: 3
- Answered initialize and tools/list: 3
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 3 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 1 of 2 compared days.
- 2026-11-13: input or output schemas changed, descriptions changed
What tools does it list?
115 tools on 2026-11-16:
approve_timesheetassign_user_to_customerassign_user_to_projectbulk_create_time_reportsbulk_update_cost_ratesbulk_update_time_reportscancel_invitecancel_scheduled_reportcancel_timerchange_user_rolecheck_budget_limitsclose_frame_orderclose_monthcommit_importcopy_periodcreate_credit_notecreate_custom_fieldcreate_customercreate_favoritecreate_frame_ordercreate_holiday_profilecreate_projectcreate_scheduled_reportcreate_subtaskcreate_taskcreate_time_reportdelete_api_keydelete_custom_fielddelete_customerdelete_draft_invoicedelete_favoritedelete_frame_orderdelete_holiday_profiledelete_organizationdelete_projectdelete_subtaskdelete_taskdelete_time_reportdelete_work_scheduledisable_userenable_userfind_billing_workgenerate_invoiceget_billing_reportget_budget_alertsget_budget_healthget_cost_rate_historyget_customer_infoget_dashboard_metricsget_employee_timesheetget_financial_analyticsget_frame_order_utilizationget_hours_summaryget_import_templateget_invoiceget_my_time_entriesget_project_statusget_project_teamget_resource_utilizationget_unbilled_timeinvite_userissue_invoicelist_customerslist_favoriteslist_invoiceslist_my_time_entrieslist_projectslist_recycle_binlist_scheduled_reportslog_timemanage_user_work_schedulemark_invoice_paidmark_time_invoicedmove_projectmove_subtaskmove_taskpermanent_delete_entityrecall_timesheetreissue_invoicereject_timesheetremove_userremove_user_from_customerremove_user_projectreopen_monthreopen_timesheetresend_inviterestore_entitysearchsend_invoiceset_budget_thresholdsset_custom_field_valueset_org_work_scheduleset_user_cost_ratestart_timerstop_timersubmit_timesheetsuggest_holiday_profileundo_write_offupdate_custom_fieldupdate_customerupdate_draft_invoiceupdate_frame_orderupdate_holiday_profileupdate_org_settingsupdate_projectupdate_scheduled_reportupdate_subtaskupdate_taskupdate_time_reportupdate_user_preferencesupdate_user_profileuse_favoritevalidate_importvoid_invoicewrite_off_time
MCP Registry declaration
- Registry name:
ai.timix/time-tracking - Declared version: 1.0.0
- Status: active
- Declared hosts:
api.timix.ai
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:ai.timix/time-tracking", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ai.timix/time-tracking?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).