Skip to content
MCPSTAMP
MCP server report

Timix.AI MCP server

ai.timix/time-tracking

We checked this server on 2 November 2026 with McpStamp Check engine 1.2.0. It scored 84 of 100 (grade B), higher than 31.0% of the 33,003 registry servers that responded over HTTPS that day. Ready for Gemini and MCP Registry. Not ready for Claude and ChatGPT.

Measured facts

Score
84B
Sign-in
OAuth
Tools listed
114
Protocol version
2025-06-18
Stores

Store readiness

StoreStatusReason
Claude Connectors Directory Not ready Blocked by readOnlyHint or destructiveHint on every tool and Human-readable title on every tool.
ChatGPT app directory Not ready Blocked by readOnlyHint or destructiveHint on every tool, Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT) and Human-readable title on every tool.
Gemini Connected Apps Ready No blocking check failed.
Official MCP Registry Ready No blocking check failed.

MCP Registry ready means a valid public remote for the registry, not that the server is listed in a store.

Fixes

5 checks to fix

  1. Fails

    readOnlyHint or destructiveHint on every tool

    tool_annotations

    Blocks Claude and ChatGPT.

    Measured 114/114 tools set neither readOnlyHint nor destructiveHint: get_hours_summary, get_dashboard_metrics, get_customer_info, get_project_status, get_billing_report

    Set annotations.readOnlyHint: true on read-only tools and destructiveHint: true on tools that modify or delete data (Claude needs one of them on every tool; ChatGPT needs all three hints, see tool_open_world).

  2. Fails

    Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT)

    tool_open_world

    Blocks ChatGPT.

    Measured 114/114 tools miss an explicit hint: get_hours_summary, get_dashboard_metrics, get_customer_info, get_project_status, get_billing_report and 109 more

    Set readOnlyHint, destructiveHint and openWorldHint to explicit true/false on every tool (OpenAI app review requires all three).

  3. Fails

    Human-readable title on every tool

    tool_titles

    Blocks Claude and ChatGPT.

    Measured 114/114 without title: get_hours_summary, get_dashboard_metrics, get_customer_info, get_project_status, get_billing_report and 109 more

    Add a short human-readable "title" to every tool (shown in store UIs and consent screens).

  4. Warning

    Tool descriptions

    tool_descriptions

    Measured 4 under 60 chars: get_billing_report, list_customers, get_invoice, list_scheduled_reports

    Keep each tool description between 60 and 2000 characters: when to use it, what it returns, key limits.

  5. Warning

    refresh_token grant advertised

    auth_refresh

    Measured grant_types_supported: ["authorization_code"]

    Issue refresh tokens and list "refresh_token" in grant_types_supported so users are not logged out hourly.

21 checks passed, 1 did not run

Passed. Served over HTTPS, initialize over Streamable HTTP, Supported protocol version negotiated, JSON or SSE response Content-Type, JSON-RPC error for unknown method, GET answers SSE or 405, initialize latency, serverInfo name and version, Server instructions, tools capability declared, Sign-in method the store supports (OAuth or none), Protected resource metadata (RFC 9728), Resource metadata "resource" equals the server URL, Authorization server metadata (RFC 8414 / OIDC), First metadata URL Gemini tries answers 200 with the required fields, issuer equals the authorization_servers entry; token_endpoint_auth_methods_supported (ChatGPT), PKCE S256 advertised, Client registration (DCR or Client ID Metadata Documents), tools/list returns tools, inputSchema is an object schema, Tool names are valid and portable.

Not run. 401 carries WWW-Authenticate resource_metadata. These need an OAuth sign-in flow the check could not reach.

Run a fresh check

This page is the 2 November 2026 snapshot. If you maintain this server and have shipped fixes since then, re-check it. The live check and the badge show the current result, and the next snapshot will pick up the change.

Re-check now

Badge

README badge

The badge shows the latest score for this URL and links to this report.

McpStamp score for Timix.AI

Markdown

[![McpStamp score](https://www.mcpstamp.com/badge?url=https%3A%2F%2Fapi.timix.ai%2Fapi%2Fintegration%2Fv1%2Fmcp)](https://www.mcpstamp.com/r/ai-timix-time-tracking/)

HTML

<a href="https://www.mcpstamp.com/r/ai-timix-time-tracking/"><img src="https://www.mcpstamp.com/badge?url=https%3A%2F%2Fapi.timix.ai%2Fapi%2Fintegration%2Fv1%2Fmcp" alt="McpStamp score" height="20"></a>
Registry entry

About this server

Time tracking, live project budgets, and billing exports for service firms.
Registry name
ai.timix/time-tracking
Remote URL
https://api.timix.ai/api/integration/v1/mcp
Version
1.0.0
Website
timix.ai
Checked
2 November 2026, engine 1.2.0, no credentials

The description above is the server's own text from the official MCP Registry. If a result looks wrong, run a fresh check and email support@zovo.one with the report link.

More grade B servers

All grade B servers · All server reports · State of MCP readiness, November 2026