Remote MCP · Endpoint

Timix.AI MCP server

No. Timix.AI answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://api.timix.ai/api/integration/v1/mcp

The last check completed an MCP handshake.

Registry name
ai.timix/time-tracking
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
60 ms
Tools exposed
114 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Time tracking, live project budgets, and billing exports for service firms.
Listing
From the official MCP registry (active).
Recent checks of Timix.AI
CheckedResultHandshake
5 hours agoHandshake completed60 ms
2 days agoHandshake completed71 ms
4 days agoHandshake completed320 ms
5 days agoHandshake completed66 ms
7 days agoHandshake completed98 ms
8 days agoHandshake completed67 ms
9 days agoHandshake completed68 ms
12 days agoHandshake completed53 ms
13 days agoHandshake completed87 ms
15 days agoHandshake completed89 ms
16 days agoHandshake completed81 ms
17 days agoHandshake completed154 ms
19 days agoHandshake completed58 ms
19 days agoHandshake completed66 ms
20 days agoHandshake completed60 ms
21 days agoHandshake completed71 ms
22 days agoHandshake completed56 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Timix.AI and makes no claim about it beyond what these checks measured.