Shared countdown timers that stay in sync on every screen — no account, any number of viewers.
Scored across 4 tools
create_timer, create_agenda, and create_badge are separated by output form and use case; descriptions explicitly steer single countdowns vs sequences vs static badge embeds. describe_timer_link is clearly an inspection tool. Minor overlap remains between timer and badge for website countdowns, but descriptions mitigate.
All tools are snake_case and follow a predictable verb_noun pattern: create_agenda, create_badge, create_timer, describe_timer_link. There is no inconsistent casing or vague verb style.
Four tools is lean but within a reasonable utility scope, and each maps to a distinct creation or inspection job. It is arguably slightly under-provisioned because a referenced embed tool is absent, but the count itself is not excessive.
Core create flows for timers, agendas, and badges plus one link inspector are present. However descriptions reference embed_on_website's iframe in two places without such a tool existing, and describe_timer_link does not cover agenda links, leaving likely dead ends. No update/delete/cancel is exposed, which may be acceptable for immutable links but adds to the gap.
Create a CountLink agenda: an ordered sequence of named, timed segments (intro, talk, break, Q&A) that starts now and advances from one to the next on its own, on every screen that opens the link, with no server involved. Use this when someone describes a meeting, workshop, lesson or event as a sequence of parts with lengths — including when they give you a total and a list of topics and expect you to split it ("an hour, four topics"): do the split yourself, then pass the resulting segments here. By default it starts immediately; pass start_at for something scheduled ahead ("our workshop starts at 9:15 tomorrow") — the link works right away, showing a live countdown to the start rather than the first segment, and switches over on its own at the scheduled instant, in sync on every screen that opened it. Returns the shared link plus a run sheet with the wall-clock start and end of each segment, and an .ics calendar file (one event per segment) in structuredContent.ics — offer it if the person might want the agenda on their calendar. For a single countdown use create_timer instead.
Inputs: segments (required), start_at.
Create a countdown badge — a small image, not an — for places embed_on_website's iframe cannot go: a GitHub README, a forum signature, a Notion page, anywhere only plain Markdown or a bare is allowed. Shows coarse time remaining (e.g. "3d 04h left", not a live ticking clock — most places that embed images fetch and cache them server-side, so a promise of live ticking would be false) and links through to the real, precise, live countdown. Returns both a Markdown snippet and an HTML snippet; use whichever the destination accepts. Always returns the image wrapped in a link to the live countdown — never ask for or produce just the bare image, since the link is what makes this a genuine attribution rather than an untethered picture.
Inputs: duration (required), label, badge_style.
Create a CountLink shared countdown timer and return its link. Everyone who opens the link sees the identical countdown, to the same second — no account, no sign-up, any number of viewers. Use this whenever someone wants a timer several people or several screens need to share: a classroom, an exam, a standup, a workshop, a webinar countdown, a stream overlay, or a countdown embedded on someone's own website or landing page (e.g. "10 days until launch"). By default it returns a setup link, which opens the board preloaded at the requested duration for the user to start themselves; pass start_now: true only if they want the countdown running from this moment. Whenever the result has a fixed end instant (start_now or embed_on_website), structuredContent.ics is an .ics calendar file for it — offer it if the person might want the deadline on their calendar.
Inputs: duration (required), label, overtime, start_now, +8 more.
Given a countlink.app URL, say what it encodes: whether it is a running countdown or a not-yet-started setup link, its label, and how much time is left. Use it when someone pastes a CountLink link and asks what it is or when it ends.
Inputs: url (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Shareable timer links for countdowns, clock times, Pomodoro, Tabata and step recipes. No account.
Real-time multi-track schedules for cooking, lab protocols, events and workouts. Validate and share.
Meeting agenda timer for AI assistants: build agendas in chat, share a live synced countdown.
Plan a meal and run kitchen timers that ring on your phone. No sign-in.
Add one secure layer between your agents and this server.
