# ai.timix/time-tracking

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

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the content rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.0.0
- **Author:** ai.timix
- **License:** Unknown
- **Endpoints:** streamable-http https://api.timix.ai/api/integration/v1/mcp
- **Source:** https://timix.ai
- **Endpoint health:** reachable (last checked 2026-09-13T05:23:17.332Z, 4 samples) — uptime is not a security property and is not part of the trust score
- **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport)

## Trust

60/100 (B), scored on the content rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: clean
- Obfuscation scan: clean
- Evidence age: 0 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-13T05:23:17.332Z
- **Version scanned:** live
- **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it.

## Tools

114 declared. Observed from a live `tools/list` probe.
- `get_hours_summary` — Get a summary of hours logged for a user or team over a date range
- `get_dashboard_metrics` — Get organization dashboard metrics including utilization, revenue, and active projects
- `get_customer_info` — Get detailed information about a customer including health score and portfolio
- `get_project_status` — Get detailed project status including budget, hours, and task breakdown
- `get_billing_report` — Get billing summary for a customer over a date range
- `get_budget_alerts` — Get all budget alerts for the organization showing projects that are over or near budget
- `list_customers` — List all customers in the organization
- `list_projects` — List all projects in the organization with their status and budget information
- `get_my_time_entries` — Get the current user's time entry analytics for a date range, including hours breakdown by project and customer, billable vs non-billable split, and target comp
- `get_resource_utilization` — Get team resource utilization summary showing target hours, actual hours, billable hours, and utilization percentage for the organization
- `get_unbilled_time` — Get a summary of unbilled time across the organization, including total hours, total amount, number of entries, and aging information
- `get_budget_health` — Get overall budget health summary for the organization, including project counts by status (on-track, warning, critical), total remaining budget hours, and acti
- `get_employee_timesheet` — Get an employee's timesheet report showing target hours, actual hours logged, and variance. Can look up by employee name or default to the requesting user.
- `list_my_time_entries` — List the current user's own individual time entries for a date range, with project name, task/subtask ids, hours, description, billable flag and status. Use thi
- `find_billing_work` — Find the projects, tasks and subtasks in your organization where time can be tracked, optionally filtered by a name fragment. Use this to locate where to record
- `get_project_team` — Get the people associated with a project: who is ASSIGNED to it (formally responsible / accountable) and the TOP CONTRIBUTORS by hours logged (who is actually d
- `log_time` — Create a single time entry on a subtask for the current user. Requires permission to log time.
- `suggest_holiday_profile` — Look up the official public/national holidays for a country (ISO-2 code, e.g. US, IL, GB) and year from an authoritative public source (Hebcal for Israel, Nager
- `create_holiday_profile` — Create and SAVE a national-holiday profile for the organization for a specific year, AFTER the user has explicitly reviewed and confirmed the holiday list. Each
- `create_customer` — Create a new billing customer in your organization. The organization is fixed by your context - never pass an organization id.
- `create_project` — Create a new billing project under one of your customers. The organization is fixed by your context; customer_id must be a customer in your organization. Discov
- `create_task` — Create a task under a project. Tasks group the subtasks that time is logged against. The task inherits its allowed billing types from the parent project. Discov
- `create_subtask` — Create a subtask under a task. All time entries are logged against subtasks, so every task needs at least one. The subtask inherits a valid billing type from th
- `invite_user` — Invite a person to join your organization by email at a chosen role. The organization is fixed by your context - never pass an organization id. Valid roles: Adm
- `assign_user_to_project` — 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 p
- `update_org_settings` — Update core settings for your organization: name, country, default_time_zone, base_currency, first_day_of_month (1-28), auto_close_month_after_days, and the bud
- `update_customer` — Update an existing billing customer in your organization. Only the fields you provide are changed; everything else is left as-is (PATCH semantics). Discover ids
- `update_project` — Update an existing billing project in your organization. Only the fields you provide are changed (PATCH semantics). You can rename the project, update its descr
- `update_task` — Update an existing task in your organization. Only the fields you provide are changed (PATCH semantics). You can rename the task, update its description, change
- `update_subtask` — Update an existing subtask in your organization. Only the fields you provide are changed (PATCH semantics). You can rename the subtask, update its description, 
- `create_time_report` — Create a new time entry on a subtask for the current user. The entry is always attributed to you — you cannot create entries on behalf of another user. Supply s
- `update_time_report` — Update fields on one of your own time entries (PATCH — only the fields you supply are changed; everything else is left as-is). Supply the time_report_id plus an
- `bulk_create_time_reports` — Create multiple time entries in one call. Supply an 'entries' array where each item has subtask_id, date (YYYY-MM-DD), and hours (> 0 and ≤ 24); optionally star
- `bulk_update_time_reports` — Apply a common text description update to multiple of your own time entries. Supply ids (list of time-report ids, max 100) and text (the new description). Retur
- `copy_period` — Copy your own time entries from a source date range into a target date range, preserving each entry's weekday offset relative to the source start (e.g. copy las
- `start_timer` — Start (or replace) your running timer on a subtask. There is at most one running timer per user; starting a new one replaces any existing. Stop it later with st
- `stop_timer` — Stop your running timer. The elapsed time is computed and a Draft time entry is created automatically. Returns the created time entry. No arguments needed.
- `cancel_timer` — Cancel (discard) your running timer without creating a time entry. The elapsed time is lost. No arguments needed.
- `submit_timesheet` — Submit your time entries for a given month for manager approval. Draft and Rejected entries in the month are transitioned to Submitted. A billing-closed month c
- `recall_timesheet` — Withdraw your submitted timesheet for a given month back to Draft (un-submit), reopening entries for editing. Only valid while the period is Submitted — after a
- …and 74 more

## Install

**Verdict: review** — Installable, but 2 things to check first: No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
**Cautions** (coverage gaps and advisories — never blocking)
- No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"time-tracking\": {\n      \"type\": \"http\",\n      \"url\": \"https://api.timix.ai/api/integration/v1/mcp\"\n    }\n  }\n}"
```

## Blast radius

Extensive to critical — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: deletes data; 22 privileged tools.
- Floor 38, ceiling 62 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/ai.timix%2Ftime-tracking
- Install plan: https://forgeregistry.com/api/v1/packages/ai.timix%2Ftime-tracking/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/ai.timix%2Ftime-tracking
- HTML page: https://forgeregistry.com/registry/ai.timix%2Ftime-tracking
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.