CountLink
REMOTE · COUNTLINK.APP
Shared countdown timers that stay in sync on every screen — no account, any number of viewers.
Available components
Last scanned (12 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Productivity and Notes
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1961 tokens (~392/item across 5 items; 4 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities73
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
- Supports UI / widget rendering.Pass
Checks we ran (14)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 11 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 −1
- Stability: pass → 0.97 functional
- 9 Nov 26 +1
- Stability: 0.97 → pass security
- 8 Nov 26 −1
- Stability: pass → 0.97 functional
- 7 Nov 26 +1
- Stability: 0.97 → pass security
- 6 Nov 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Nov 26 +1
- Stability: 0.97 → pass security
- 4 Nov 26 −1
- Stability: pass → 0.97 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://countlink.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=countlink.app | CN=WE1,O=Google Trust Services,C=US | 3 Nov 2026 | 1 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 8ea2e255298decd613954f8c3c158910 |
| SANs: countlink.app | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of countlink.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| countlink.app. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://countlink.app/mcp | Verified | 200 | |
| http (plaintext) | http://countlink.app/mcp | HTTPS enforced | 301 | https://countlink.app/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_agenda Create a chained agenda of timed segments ~397
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 agend… |
| start_at | string | – | 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… |
No output schema declared.
No examples provided.
create_badge Create a countdown badge for a README, forum post or similar ~343
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) 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.
| Name | Type | Req | Description |
|---|---|---|---|
| badge_style | string | – | Visual style: "board" (default, dark), "minimal" (no background — blends into any page) or "light". |
| 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_webs… |
| label | string | – | Optional short name shown on the badge, e.g. "Launch" or "CFP closes". |
No output schema declared.
No examples provided.
create_timer Create a shared countdown timer ~976
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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_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 <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_style | string | – | Board style for embed_on_website: "board" (default, dark split-flap), "minimal" (plain digits) or "light". Ignored otherwise. |
| embed_width | number | – | Pixel width of the embedded iframe when embed_on_website is true. 160–1600, default 400. Ignored otherwise. |
| for_obs_overlay | boolean | – | 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… |
| label | string | – | Optional name shown on the board, e.g. "Exam" or "Break". Keep it short. |
| overlay_color | string | – | Optional digit colour for the OBS overlay as hex, e.g. "ff3df5" or "#5ef2ff". Applies to outline, neon, glass and minimal. Ignored otherwise. |
| overlay_start | string | – | When an OBS overlay (for_obs_overlay) starts counting. load (default): when the scene loads. stream: waits at full time until the stream goes live in OBS. scene: restarts from the full duration every… |
| overlay_style | string | – | Look of the OBS overlay when for_obs_overlay is true. board (default) is the split-flap board; outline is white digits with a dark edge that stays readable over gameplay; neon glows; glass sits the d… |
| overtime | boolean | – | True keeps the countdown running past zero as "+0:42" so everyone sees how far over it is (talks, breaks that run long). Works for shared links, setup links and overlays. |
| start_now | boolean | – | 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 alre… |
No output schema declared.
No examples provided.
describe_timer_link Explain a CountLink link ~81
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | A countlink.app timer URL. |
No output schema declared.
No examples provided.
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.
remote · countlink.app
claude mcp add --transport http app-countlink-countdown 'https://countlink.app/mcp'
What is the CountLink MCP server?
CountLink is an MCP server listed in the public MCP registry as app.countlink/countdown. Shared countdown timers that stay in sync on every screen, no account, any number of viewers. This page covers its hosted endpoint (https://countlink.app/mcp).
Is the CountLink MCP server safe to use?
CountLink scores 84 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the CountLink MCP server expose?
CountLink exposes 4 tools: create_timer, create_agenda, create_badge, describe_timer_link. Their descriptions and schemas cost roughly 1,797 tokens of context every time the server is loaded.
Does the CountLink MCP server require authentication?
No. We connected to CountLink without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the CountLink MCP server still maintained?
CountLink is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the CountLink MCP server?
VerifyMCP ran 14 checks on CountLink, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.