mcp-registry/ai.timix/time-tracking · v1.0.0
As of 2026-10-22 06:31 UTC, the Timix Time Tracking MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 5 minutes.
Time tracking, live project budgets, and billing exports for service firms.
Claude Code
claude mcp add --transport http timix-time-tracking-mcp-server https://api.timix.ai/api/integration/v1/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"timix-time-tracking-mcp-server": {
"type": "http",
"url": "https://api.timix.ai/api/integration/v1/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
114 of 114 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
114 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
61 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Loading this server's tool list costs an agent ~25,810 tokens before any work — more than 95% of MCP servers.
Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →
Handshake + tools/list takes ~1,624 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
In the last 30 days: 0 tool(s) removed and 10 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fai.timix%2Ftime-tracking/fixes
{
"name": "approve_timesheet",
"description": "Approve a submitted timesheet period for a team member. The period and its time reports transition to Approved. Use confirm=true to proceed. Requires Manager or Admin/Owner role (Finance is excluded — timesheet approval is PM work, not finance).",
"inputSchema": {
"type": "object",
"required": [
"submission_period_id"
],
"properties": {
"confirm": {
"type": "boolean",
"description": "Set true to perform the action. Omit or false returns a preview only — nothing is written."
},
"idempotency_key": {
"type": "string",
"description": "Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice."
},
"submission_period_id": {
"type": "string",
"description": "Id of the submission period to approve (from get_pending_approvals or list_approval_history)."
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "assign_user_to_customer",
"description": "Assign an organization member to a billing customer so they can see that customer and all its projects. Requires the org_user_id (discover it with get_project_team or get_employee_timesheet) and the customer_id. The organization is fixed by your context — never pass an organization id. You cannot target a user more privileged than yourself (Owner is not targetable by Admin).",
"inputSchema": {
"type": "object",
"required": [
"org_user_id",
"customer_id"
],
"properties": {
"customer_id": {
"type": "string",
"description": "Id of the customer to assign the user to."
},
"org_user_id": {
"type": "string",
"description": "Id of the OrganizationUser to assign (not the Firebase user id — use get_project_team to discover it)."
},
"idempotency_key": {
"type": "string",
"description": "Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice."
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "assign_user_to_project",
"description": "Assign a member to a project so they can see it and log time against its tasks. Identify the member by email (preferred) or by org_user_id, and the project by project_id (discover ids with find_billing_work - never ask the user for an id). The organization is fixed by your context.",
"inputSchema": {
"type": "object",
"required": [
"project_id"
],
"properties": {
"email": {
"type": "string",
"description": "Email of the member to assign (preferred). Provide this OR org_user_id."
},
"project_id": {
"type": "string",
"description": "Id of the project to assign the member to (required). Must be a project in your organization."
},
"org_user_id": {
"type": "string",
"description": "Organization-user id of the member to assign. Provide this OR email."
},
"idempotency_key": {
"type": "string",
"description": "Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice."
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/ai.timix/time-tracking"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/ai.timix/time-tracking"}) over MCP.
create_holiday_profile ~546 tokensbulk_create_time_reports ~480 tokenscreate_custom_field ~472 tokensset_org_work_schedule ~448 tokensupdate_project ~441 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fai.timix%2Ftime-tracking?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fai.timix%2Ftime-tracking?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.timix%2Ftime-tracking.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.timix%2Ftime-tracking.svg :target: https://glimind.com/server/mcp-registry%2Fai.timix%2Ftime-tracking?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:a55eb818301fc791…, first seen 2026-10-17, included at leaf 14652 of 44,327. Version history · verify what your client received.
Compare: most reliable data servers · most reliable productivity servers · most reliable finance servers · most reliable communication servers · most reliable security servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-22 06:31 UTC, the Timix Time Tracking MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 5 minutes.
Timix Time Tracking MCP server advertises 114 tools, including approve_timesheet, assign_user_to_customer, assign_user_to_project, bulk_create_time_reports, bulk_update_cost_rates.
Point your MCP client at this streamable-http endpoint: https://api.timix.ai/api/integration/v1/mcp
Glimind scanned all 114 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.