A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API
CountLink is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Shared countdown timers that stay in sync on every screen — no account, any number of viewers.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http countlink-mcp https://countlink.app/mcp
# 2 — ask your agent for something these tools do
# create_timer, create_agenda, create_badge and 1 more
CountLink costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http countlink-mcp https://countlink.app/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
4 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 o
| Parameter | Type | Required | Notes |
|---|---|---|---|
| duration | string | yes | How long the timer runs. Accepts "25m", "1h30m", "90s", "5:00", "1:30:00", or a plain number read as minutes ("45"). A setup link or OBS overlay holds up to 99h59m59s. With start_now or embed_on_websi |
| label | string | no | Optional name shown on the board, e.g. "Exam" or "Break". Keep it short. |
| start_now | boolean | no | False (default) returns a setup link the user starts themselves — correct for a timer that should begin later, and for anything being written down in advance. True returns a link for a countdown alrea |
| for_obs_overlay | boolean | no | True returns a URL to paste into OBS (or any streaming tool) as a Browser Source: a transparent background with just the digits, which starts counting as soon as the scene loads. Use it when someone w |
| embed_on_website | boolean | no | True returns ready-to-paste <iframe> HTML for embedding a countdown on someone's OWN website or landing page — e.g. a launch-day countdown on a marketing page. Unlike for_obs_overlay, this is a fixed |
| embed_width | number | no | Pixel width of the embedded iframe when embed_on_website is true. 160–1600, default 400. Ignored otherwise. |
| embed_height | number | no | Pixel height of the embedded iframe when embed_on_website is true. 80–900, default 160. Ignored otherwise. |
| embed_style | string | no | Board style for embed_on_website: "board" (default, dark split-flap), "minimal" (plain digits) or "light". Ignored otherwise. |
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 yo
| Parameter | Type | Required | Notes |
|---|---|---|---|
| segments | array | yes | The segments in running order. Each has a duration (same grammar as create_timer: "10m", "1h", "90s", "5:00", or a plain number of minutes) and an optional short label. 1–24 segments; the whole agenda |
| start_at | string | no | Optional ISO-8601 instant for a scheduled start, e.g. "2026-09-08T09:15:00Z" or with a local offset like "2026-09-08T09:15:00+01:00". Omit to start immediately. A start_at already in the past is just |
Create a countdown badge — a small image, not an <iframe> — 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 <img> 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)
| Parameter | Type | Required | Notes |
|---|---|---|---|
| duration | string | yes | How long the timer runs. Accepts "25m", "1h30m", "90s", "5:00", "1:30:00", or a plain number read as minutes ("45"). A setup link or OBS overlay holds up to 99h59m59s. With start_now or embed_on_websi |
| label | string | no | Optional short name shown on the badge, e.g. "Launch" or "CFP closes". |
| badge_style | string | no | Visual style: "board" (default, dark), "minimal" (no background — blends into any page) or "light". |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | A countlink.app timer URL. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install CountLink or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish CountLink can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.