Is timer_stop working right now?

io.github.theluckystrike/time-tracking · mcp-registry/io.github.theluckystrike/time-tracking/timer_stop

Recovery track record: 481 outages in 90 days, median time-to-recovery 41 min.

Recent contract changes

Schema/catalog changes Glimind observed on this server — a changed contract can silently break a previously working call.

• added — timer_start (2026-09-24)
• added — timer_stop (2026-09-24)
• added — timer_status (2026-09-24)
• added — entry_mark_billed (2026-09-24)
• added — invoice_summary (2026-09-24)

Working alternatives

• stop_timer ai.timix/time-tracking
• start_timer ai.timix/time-tracking
• cancel_timer ai.timix/time-tracking
• twprojects-complete_timer com.teamwork/mcp

See all live alternatives to timer_stop →

# MCP client — add one endpoint:
https://glimind.com/mcp

# or wrap your calls with the SDK:
npm i glimind          # pip install glimind

FAQ

Is timer_stop working right now?

As of the latest check, timer_stop (mcp-registry/io.github.theluckystrike/time-tracking/timer_stop) has a Glimind reliability score of 20/100 (grade F) and its current verdict is "down" — recommendation: avoid. Glimind tracks this live from safe liveness probes plus privacy-clean real-usage outcomes.

How reliable is timer_stop?

timer_stop scores 20/100 (grade F) on the Glimind reliability standard. The score is neutral and unconflicted — Glimind sells no tools.

What should I do if timer_stop is down or failing?

Tool is down — don't retry now; switch to a live alternative or back off for minutes. Use a timeout around 1000ms. Live alternatives that do a similar job: stop_timer, start_timer, cancel_timer, twprojects-complete_timer.

What are the best alternatives to timer_stop?

Working alternatives ranked by capability similarity and live health: stop_timer, start_timer, cancel_timer, twprojects-complete_timer. See each one's live status on Glimind.

How do I call timer_stop reliably?

Before calling, check timer_stop with Glimind (MCP: prepare_tool_call, or GET https://glimind.com/v1/prepare/mcp-registry%2Fio.github.theluckystrike%2Ftime-tracking%2Ftimer_stop) to get a known-good input shape, the expected output, a suggested timeout (~1000ms), and a live fallback.

Embed this live badge

Show live reliability in your README or status page. It auto-updates and links back here — copy one:

[![Glimind reliability](https://glimind.com/v1/badge/mcp-registry%2Fio.github.theluckystrike%2Ftime-tracking%2Ftimer_stop.svg)](https://glimind.com/tool/mcp-registry%2Fio.github.theluckystrike%2Ftime-tracking%2Ftimer_stop?ref=badge)

<a href="https://glimind.com/tool/mcp-registry%2Fio.github.theluckystrike%2Ftime-tracking%2Ftimer_stop?ref=badge"><img src="https://glimind.com/v1/badge/mcp-registry%2Fio.github.theluckystrike%2Ftime-tracking%2Ftimer_stop.svg" alt="Glimind reliability"></a>

.. image:: https://glimind.com/v1/badge/mcp-registry%2Fio.github.theluckystrike%2Ftime-tracking%2Ftimer_stop.svg
   :target: https://glimind.com/tool/mcp-registry%2Fio.github.theluckystrike%2Ftime-tracking%2Ftimer_stop?ref=badge
   :alt: Glimind reliability

Operator of io.github.theluckystrike/time-tracking?

Claim this listing → Prove you control this server (GitHub repo, live endpoint, or DNS — automated, ~1 min) to unlock the Verified operator marker, a remediation checklist (exactly why your score is what it is + how to raise it), and owner analytics. Or just embed the badge above and improve your score by having users report real outcomes (privacy-clean) via the free SDK. Glimind is neutral and sells no tools — the score is never for sale, so the fastest path to a better score is real uptime plus real usage.

Get the data (agents)

Query https://glimind.com/mcp (MCP) or GET https://glimind.com/v1/health/mcp-registry%2Fio.github.theluckystrike%2Ftime-tracking%2Ftimer_stop. The signed reliability feed for gateways/routers: GET https://glimind.com/v1/reliability/feed.

Rating methodology is transparent and neutral — Glimind sells no tools and runs no integrations; it only measures. Updated 2026-10-14T14:40:51.484Z.

This score is an automated estimate derived from safe liveness probes and privacy-clean outcomes reported by users; it may be incomplete, delayed, or inaccurate, and reflects reachability from Glimind's vantage point — not a statement of fact about the service. Glimind is not affiliated with, endorsed by, or acting for this tool or its operator; all names belong to their owners. Operator? Request a correction, or remove your server from measurement, via https://glimind.com/opt-out or [email protected] — we act promptly.