# CountLink (remote · countlink.app) Shared countdown timers that stay in sync on every screen — no account, any number of viewers. - Trust score: 80/100 (high trust) - Change this week: +3 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-10-02 ## Components - remote · `countlink.app`: 80/100 (this document), [markdown](https://verifymcp.io/servers/app-countlink-countdown/countlink.md), [page](https://verifymcp.io/servers/app-countlink-countdown/countlink) ## Channel facts - Endpoint: `https://countlink.app/mcp` - Transports: `streamable-http` - Auth: `none` - Version: `1.0.0` ## Trust breakdown How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-10-02. - **Endpoint Security**: 74/100 - The endpoint's TLS certificate is valid, in date, and uses a strong key. - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. - HTTPS is enforced; there's no plaintext access path. - HSTS check failed: the Strict-Transport-Security header is absent. - DNSSEC check failed: this domain isn't protected by DNSSEC. - **Transport & Reachability**: 100/100 - Verified streamable-http transport via a live MCP handshake. - **Schema Quality & AI Usability**: 65/100 - AI-judged instruction clarity (excellent). - Context-footprint check failed: tool/resource definitions use about 1711 tokens (~427/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 90/100 - Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 100% of tool parameters carry a description. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation. - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 60/100 - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. ## Install ### How do I install the CountLink MCP server? CountLink is a hosted endpoint at https://countlink.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation. ### Claude ```bash claude mcp add --transport http app-countlink-countdown 'https://countlink.app/mcp' ``` ### Cursor ```json { "mcpServers": { "app-countlink-countdown": { "url": "https://countlink.app/mcp" } } } ``` ### VS Code ```json { "servers": { "app-countlink-countdown": { "type": "http", "url": "https://countlink.app/mcp" } } } ``` ### Codex ```toml [mcp_servers.app-countlink-countdown] url = "https://countlink.app/mcp" ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "app-countlink-countdown": { "type": "remote", "url": "https://countlink.app/mcp", "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add app-countlink-countdown --url 'https://countlink.app/mcp' --transport streamable-http ``` ### Hermes ```yaml mcp_servers: app-countlink-countdown: url: "https://countlink.app/mcp" ``` ### Netclaw ```json { "McpServers": { "app-countlink-countdown": { "Transport": "http", "Url": "https://countlink.app/mcp" } } } ``` ### Vellum ```bash assistant mcp add app-countlink-countdown -t streamable-http -u 'https://countlink.app/mcp' ``` ### Other ```json { "mcpServers": { "app-countlink-countdown": { "type": "http", "url": "https://countlink.app/mcp" } } } ``` The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs. ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-10-01 (score 80, +1) No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-09-29 (score 79, +1) No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-09-28 (score 78, 0) - [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server ### 2026-09-26 (score 78, +1) - [cosmetic] “create_badge” reworded the description of “duration” - [cosmetic] “create_timer” reworded the description of “duration” ### 2026-09-25 (score 77, 0) - [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server ### 2026-09-24 (score 77, +1) No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-09-22 (score 76, +1) No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-09-20 (score 75, +1) No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes. ## MCP tools (4) ### `create_timer` (~741 tokens) Create a shared countdown timer 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. Input parameters: - `duration` (string, required): 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_webs… - `embed_height` (number): Pixel height of the embedded iframe when embed_on_website is true. 80–900, default 160. Ignored otherwise. - `embed_on_website` (boolean): True returns ready-to-paste