Should my agent depend on the MCP server ai.timix/time-tracking?

Verdict: allow — rich-solo — safe to depend on As of 2026-08-15T11:28:18Z: a dated observation with receipts, not a warranty.

Timix.AI

ai.timix/time-tracking

Time tracking, live project budgets, and billing exports for service firms.

— the operator's own registry description reported

Publisher ai.timix · first seen 2026-08-12 · endpoint https://api.timix.ai/api/integration/v1/mcp

allow

verdict

rich-solo

cluster

ok_tools

answers

114

tools served

Dependency rating derived

allow — rich-solo — safe to depend on

Cluster rich-solo · distinctiveness 0.391 (moderate). Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.

Reach — can an agent get to it?

answersalive_tools

latency224 ms

vs populationtypical

protocolcurrent

authopen

Use — can it use it?

tools114

vs populationhigh

capabilities1

harnessA

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_6ae25aad5624a347194fb47f · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Tools last seen

approve_timesheet assign_user_to_customer assign_user_to_project bulk_create_time_reports bulk_update_cost_rates bulk_update_time_reports cancel_invite cancel_scheduled_report cancel_timer change_user_role check_budget_limits close_frame_order close_month commit_import copy_period create_credit_note create_custom_field create_customer create_favorite create_frame_order create_holiday_profile create_project create_scheduled_report create_subtask create_task create_time_report delete_api_key delete_custom_field delete_customer delete_draft_invoice delete_favorite delete_frame_order delete_holiday_profile delete_organization delete_project delete_subtask delete_task delete_time_report delete_work_schedule disable_user enable_user find_billing_work generate_invoice get_billing_report get_budget_alerts get_budget_health get_cost_rate_history get_customer_info get_dashboard_metrics get_employee_timesheet get_frame_order_utilization get_hours_summary get_import_template get_invoice get_my_time_entries get_project_status get_project_team get_resource_utilization get_unbilled_time invite_user issue_invoice list_customers list_favorites list_invoices list_my_time_entries list_projects list_recycle_bin list_scheduled_reports log_time manage_user_work_schedule mark_invoice_paid mark_time_invoiced move_project move_subtask move_task permanent_delete_entity recall_timesheet reissue_invoice reject_timesheet remove_user remove_user_from_customer remove_user_project reopen_month reopen_timesheet resend_invite restore_entity search send_invoice set_budget_thresholds set_custom_field_value set_org_work_schedule set_user_cost_rate start_timer stop_timer submit_timesheet suggest_holiday_profile undo_write_off update_custom_field update_customer update_draft_invoice update_frame_order update_holiday_profile update_org_settings update_project update_scheduled_report update_subtask update_task update_time_report update_user_preferences update_user_profile use_favorite validate_import void_invoice write_off_time

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band A — an agent can pick and call these reliably.

legibility check	tools passing	ok
name is clear & specific	114/114	✓
has a description	114/114	✓
description is substantive	113/114	113/114
parameters are typed	114/114	✓
parameters are described	114/114	✓

114 of 114 tools graded · 114 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18

protocol version

—

session model

1.0.0

server version timix-mcp

Capabilities: tools

Drift

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (1 events)

date	type	what changed
2026-08-12	outcome	first probe: ok_tools

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T19:57:42Z	ok_tools	200	224	2025-06-18
2026-08-12T05:32:59Z	ok_tools	200	210	2025-06-18

Watch or embed this verdict

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/ai.timix/time-tracking.svg)](https://robinsaige.com/s/ai.timix/time-tracking)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview