CountLink is an MCP server with 4 tools an agent can call, among them create_agenda, create_badge, create_timer. It answers at https://countlink.app/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 9 of 9 times since 6 September 2026; the last check, on 18 October 2026, succeeded.
Shared countdown timers that stay in sync on every screen — no account, any number of viewers.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
create_agenda | 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 some Inputs: segments, start_at |
create_badge | 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 remain Inputs: duration, label, badge_style |
create_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 peo Inputs: duration, label, start_now, for_obs_overlay, embed_on_website, embed_width |
describe_timer_link | 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 |
Every block below points at https://countlink.app/mcp. Pick your client and copy.
claude mcp add --transport http countlink https://countlink.app/mcp
{
"mcpServers": {
"countlink": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://countlink.app/mcp"]
}
}
}{
"mcpServers": {
"countlink": {
"url": "https://countlink.app/mcp"
}
}
}{
"servers": {
"countlink": {
"type": "http",
"url": "https://countlink.app/mcp"
}
}
}{
"context_servers": {
"countlink": {
"url": "https://countlink.app/mcp"
}
}
}{
"mcpServers": {
"countlink": {
"serverUrl": "https://countlink.app/mcp"
}
}
}{
"mcpServers": {
"countlink": {
"url": "https://countlink.app/mcp"
}
}
}name: CountLink
version: 0.0.1
schema: v1
mcpServers:
- name: CountLink
type: streamable-http
url: https://countlink.app/mcp{
"mcpServers": {
"countlink": {
"httpUrl": "https://countlink.app/mcp"
}
}
}{
"mcpServers": {
"countlink": {
"type": "http",
"url": "https://countlink.app/mcp"
}
}
}{
"mcpServers": {
"countlink": {
"url": "https://countlink.app/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fcountlink.app%2Fmcp&type=streamable_http&id=countlink&name=CountLink
It answered our last check on 18 October 2026 in 288 ms. Over 9 checks since 6 September 2026 it answered 9. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by countlink.app and served from countlink.app, the vendor's own domain: https://countlink.app/mcp.
4, as returned by the server's own tools/list on 6 September 2026: create_agenda, create_badge, create_timer, describe_timer_link.
It answered our last check on 18 October 2026 in 288 ms. Over 9 checks since 6 September 2026 it answered 9.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://countlink.app/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: app.countlink. Endpoint host: countlink.app. ARD identifier: urn:air:app.countlink:mcp:countdown.
First indexed 6 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.