[{"_1":2,"_3":-5,"_4":-5},"loaderData",{"_5":6,"_7":8,"_9":10},"actionData","errors","root",{"_109":110},"routes/modules.$creator.$moduleId",{"_14":15,"_16":17,"_18":19,"_20":21},"routes/modules.$creator.$moduleId.endpoints",{"_11":12,"_13":-5},"error","Module not found","tools","module",{"_20":22,"_23":24,"_25":26,"_27":28,"_29":30,"_31":32,"_33":34,"_35":26,"_36":37,"_38":-5,"_39":-5,"_40":41,"_42":43,"_44":45,"_46":47,"_48":47,"_49":50,"_51":52,"_53":54,"_55":-5,"_56":47,"_57":58,"_59":60,"_61":62,"_63":64,"_65":66,"_67":47,"_68":69,"_70":71,"_72":73,"_74":75,"_76":77,"_78":-5,"_79":-5,"_80":-5,"_81":47,"_82":-5,"_83":58,"_84":85,"_86":87,"_88":89,"_90":91,"_92":93,"_94":95},"apiUrl","https://odel.app/api","creator","mrbrunocode","moduleId","countlink","@mrbrunocode/countlink","displayName","CountLink","tagline","Shared countdown timers that stay in sync on every screen — no account, any number of viewers.","iconKey","https://avatars.githubusercontent.com/u/43336831?v=4","category","remote","status","published","visibility","public","metaDescription","deploymentType","external","workerName","bindingName","mcpConfig","{\"url\":\"https://countlink.app/mcp\",\"transport\":\"streamable-http\",\"authType\":\"none\"}","pricingModel","free","creatorUserId","system:external-import","createdAt",1788668373000,"updatedAt","sourceRegistry","official-mcp-registry","sourceUrl","https://registry.modelcontextprotocol.io/v0/servers?search=app.countlink%2Fcountdown","sourceVerified",false,"sourceMissingSince","importedAt","upstreamStars",0,"upstreamUpdatedAt",1788643489000,"detectedTransport","streamable-http","detectedAuthType","none","probeStatus","ok","lastProbedAt","githubRepoUrl","https://github.com/mrbrunocode/countlink","githubRepoFullName","mrbrunocode/countlink","releaseId","ext-mrbrunocode-countlink","version","1.0.0","descriptionMarkdown","# CountLink\n\nA free, zero-backend countdown timer. Set a duration, copy the link, send it to\na room — everyone who opens that link sees the identical countdown, perfectly\nin sync, because the deadline is a timestamp encoded in the URL itself. No\naccount, no server, no database.\n\nLive at [countlink.app](https://countlink.app). For local dev, open `index.html`\ndirectly or serve the folder — see below.\n\n**License:** source-available, not open source. No LICENSE file means all\nrights reserved by default — this repo is public so the \"nothing you paste is\nuploaded\" claim is checkable, not an invitation to redistribute or relaunch it\nas your own product.\n\n## Why this exists\n\nFull research and reasoning is in the project memory (see `/Users/bruno/.claude/projects/-Users-bruno-Code-boring-apps/memory/`),\nbut the short version: single-purpose \"boring\" utility sites (vClock, Wheel of\nNames, word counters) generate real, verifiable ad revenue at near-zero\noperating cost. vClock specifically — a free online timer — earns an\nestimated ~$500K/yr from Google AdSense on ~5.4M monthly visits. CountLink\ncopies that proven *business model* (free tool, one ad slot, programmatic SEO\npages) while adding a genuine feature vClock doesn't have: shareable,\nsynced-by-link countdowns.\n\n## Project structure\n\n```\nindex.html the tool — home page, canonical version of the UI\ncontrol.html phone-control remote (opt-in, off by default — see docs/phone-control-setup.md)\nassets/\n style.css all styling, shared by index.html and every /timers/ page\n app.js all timer logic, shared the same way\n control.js control.html's logic — separate file, different DOM shape\n realtime.js thin Ably pub/sub wrapper for phone control, inert with no key configured\n realtime-config.js the on/off switch — window.COUNTLINK_ABLY_KEY, empty by default\ntimers/ programmatic SEO landing pages (see docs/monetization.md)\n 5-minute-timer.html\n ...\nscripts/\n build-timer-pages.mjs regenerates everything in /timers/ + sitemap.xml from one data list\ndocs/\n monetization.md step-by-step: analytics, AdSense, Pro/Stripe, growing /timers/\n phone-control-setup.md how to turn on pause/adjust/stop from a phone (currently dark — needs an Ably key)\nads.txt AdSense seller-verification file (fill in once approved)\nrobots.txt allows crawling, points to sitemap.xml\nsitemap.xml generated — do not hand-edit, re-run the build script instead\narchive/ earlier prototype ideas explored before CountLink (kept for reference)\n```\n\n## Running it locally\n\nNo build step, no dependencies. Any static file server works, but use the\nincluded one during development — it sends `Cache-Control: no-store` so\nedits always show up on reload (a plain file server can leave your browser\nserving stale CSS/JS after a change):\n\n```bash\ncd /Users/bruno/onepage\nnode scripts/dev-server.mjs 4173\n# open http://localhost:4173\n```\n\n(This is also what `.claude/launch.json` runs when using the Claude Code preview.)\n\n## How the sync mechanic works\n\n`assets/app.js` writes the countdown's end-timestamp and label into the URL\nhash on start, e.g. `#t=1783378107213&l=Workshop%20resumes`. Opening that same\nURL on any other device reads the same timestamp and counts down to it using\nthe device's own clock — so there's nothing to host, nothing to keep running,\nand no possibility of the \"server\" going down.\n\n## The URL contract: `#t=` vs `#for=`\n\nThere are two shapes of link, and the difference is the product:\n\n| Shape | Means | Written by |\n|---|---|---|\n| `#t=` | a **running** countdown, one fixed instant every screen agrees on | `makeLink()`, when someone presses start |\n| `#for=` | a **setup** link — the board opens preloaded at that duration, ready but not started | anyone, in advance, by hand |\n\n`#for=` exists because until it did, **only a human in a browser who had\nalready pressed start could produce a working CountLink URL** — the share link\ncarries an absolute timestamp, so nothing that doesn't know the current epoch\ntime could write one. That ruled out every context that wants to write a timer\ndown in advance: an AI assistant answering \"give me a 25 minute shared timer\"\n(the largest traffic channel this site has), a bookmark, a calendar invite, a\nlesson plan, a saved OBS scene.\n\nIt accepts the same grammar the board accepts on paste — `25m`, `1h30m`,\n`90s`, `5:00`, `1:30:00`, `45` — by calling the very same\n`parsePastedDuration()`, so there is only one duration syntax on the whole\nsite. Add a label with `&l=`. Works on any timer page.\n\n**A setup link deliberately does not start itself.** If it did, three people\nopening the same `#for=25m` would each get their own countdown from whenever\nthey clicked — the per-visitor \"evergreen countdown\" deliberately rejected in\n`docs/` and the exact opposite of \"one fixed instant, identical on every\nscreen\". `e2e/setup-link.spec.mjs` fails if that ever changes.\n\nThe one exception is **`&go=1`**, which starts on load. It is opt-in precisely\nso \"a shared link never auto-starts\" stays a visible rule rather than a hidden\nper-page exception, and it exists for the OBS overlay — a Browser Source is one\nscene on one machine with every control stripped out and no link to copy from\nit, so there is no second viewer to fall out of sync with. The full overlay URL\nis `/embed/?overlay=1#for=10m&go=1`; **both halves matter** — `/embed/` is the\nad-and-analytics-free build, `?overlay=1` is what actually makes it\ntransparent. Never hand out `/?overlay=1` (see `docs/overlay-ads.md`: it\nredirects to `/embed/` too late to stop the preload scanner queueing the ad\nscripts, and ads on a content-free screen is a live AdSense violation).\n\n## The MCP server (`/mcp`)\n\n`functions/mcp.js` is a Cloudflare Pages Function exposing CountLink over the\nModel Context Protocol, so an assistant can *hand someone a working link*\nrather than telling them to go and make one. Four tools, all genuinely\nread-only (there is no backend — a timer is string arithmetic over a\nduration): `create_timer`, `create_agenda`, `create_badge` and\n`describe_timer_link`.\n\n`create_agenda` takes an ordered list of `{ duration, label? }` segments and\nreturns one link on `/timers/agenda-timer` that starts now (or at an optional\n`start_at`) and advances through every segment on every screen, plus a run\nsheet. It mirrors `encodeAgendaHash()` in `assets/app.js` byte for byte and\nis round-tripped through that page's own `parseAgendaHash()` in the tests.\n`describe_timer_link` reads agenda links too, including a scheduled one that\nhasn't started yet.\n\nA scheduled `start_at` in the future shows a \"Starts soon\" countdown, not an\ninflated first segment — `computeAgendaState()`'s `idx` gained a `-2`\n(\"not started\") sentinel alongside the existing `-1` (\"finished\"), because\nevery segment boundary being positive meant *any* negative elapsed time used\nto resolve to segment 0, folding the wait into that segment's remaining time.\nMirrored in `functions/mcp.js`'s `describeUrl()`. `e2e/agenda.spec.mjs`\ncovers the live transition — a 2-second-out agenda actually ticking over\ninto its first segment with no reload, across all 5 browser projects.\n\n`create_timer` covers three shapes with boolean flags: a plain shared link by\ndefault, `for_obs_overlay: true` for a self-starting OBS Browser Source, and\n`embed_on_website: true` for a ready-to-paste `