Is the Theluckystrike Timer Tracking MCP server down?

mcp-registry/io.github.theluckystrike/timer-tracking · v0.22.6

As of 2026-10-25 23:39 UTC, the Theluckystrike Timer Tracking MCP server is down with a Glimind reliability score of 21/100 (grade F). Over the last 30 days it answered 30.5% of Glimind's liveness checks. It had 719 outages in 90 days, with a median recovery of 43 minutes.

Timer and time-tracking add-on: start/stop timers, log entries, CSV export. Data stays local.

Point your MCP client at this streamable-http endpoint: https://mcp.zovo.one/mcp/timer-tracking

Agent-readiness: B (83/100)

What to fix (4)

Get alerted

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/io.github.theluckystrike/timer-tracking"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.theluckystrike/timer-tracking"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• Every tool declares whether it is read-only or destructive.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~4,167 tokens).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• No breaking contract changes in 30 days.

Largest tool definitions

• project_set_rate ~434 tokens
• report ~407 tokens
• entry_add ~402 tokens
• entry_mark_billed ~333 tokens
• timer_start ~320 tokens

Static 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:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.theluckystrike%2Ftimer-tracking.svg)](https://glimind.com/server/mcp-registry%2Fio.github.theluckystrike%2Ftimer-tracking?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fio.github.theluckystrike%2Ftimer-tracking?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.theluckystrike%2Ftimer-tracking.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.theluckystrike%2Ftimer-tracking.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.theluckystrike%2Ftimer-tracking?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:842466a35c83bac0…, first seen 2026-10-17, included at leaf 1922 of 69,428. Version history · verify what your client received.

Working alternatives

• update_time_entry app.decknote/decknote
• log_time app.decknote/decknote
• add_entries app.rowb.hourproof/hours
• reprice_time app.decknote/decknote

Tools (20)

• entry_add
• entry_delete
• entry_edit
• entry_list
• entry_log
• entry_mark_billed
• export_csv
• invoice_summary
• license_activate
• license_status
• project_set_rate
• report
• summary_client
• summary_day
• summary_week
• target_check
• target_set
• timer_start
• timer_status
• timer_stop

Compare: most reliable productivity servers · most reliable files servers · most reliable finance servers · most reliable security servers · most reliable other servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Theluckystrike Timer Tracking MCP server down right now?

As of 2026-10-25 23:39 UTC, the Theluckystrike Timer Tracking MCP server is down with a Glimind reliability score of 21/100 (grade F). Over the last 30 days it answered 30.5% of Glimind's liveness checks. It had 719 outages in 90 days, with a median recovery of 43 minutes.

How many tools does Theluckystrike Timer Tracking MCP server provide?

Theluckystrike Timer Tracking MCP server advertises 20 tools, including entry_add, entry_delete, entry_edit, entry_list, entry_log.

How do I install Theluckystrike Timer Tracking MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.zovo.one/mcp/timer-tracking

Is the Theluckystrike Timer Tracking MCP server safe to connect to an AI agent?

Glimind scanned all 20 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.

Operator of Theluckystrike Timer Tracking MCP server?

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.