Skip to main content
Glama
Rocniubi

Countdowns Online MCP

by Rocniubi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Countdowns Online MCP Server

Countdown Timers - How Many Days Until | Countdowns Online

MCP Badge License: MIT Zero Config Stdio Transport MCP

A Model Context Protocol server that exposes the canonical Countdowns Online knowledge surface — verified event dates, countdown semantics, and custom countdown sharing, FAQ, official links — to MCP-compatible AI clients such as Claude Desktop, Cursor, Windsurf, and Continue. Read-only, no API keys, no quota, ~50 ms cold start.

Official website: https://countdowns.online

⏳ About Countdowns Online

Countdowns Online is a static, browser-based directory of countdown pages for dates people want to track: game launches, movie releases, sports, holidays, seasons, and cultural events. Its useful distinction is not just the ticking clock but the meaning of the date behind it. A page can explain whether a target is a calendar date, a region-specific release, a venue schedule, or another date with a defined time basis. The site keeps source links and verification metadata visible so visitors can decide how much confidence to place in an event.

Related MCP server: EndOfLife MCP Server

Key Features

  • Verified event pages — Canonical detail routes use /<category>/<slug>/ and surface the target date, date status, applicable region, time basis, last verification date, and official sources. Events that have not passed the source-verification gate remain distinct from confirmed entries and are excluded from the sitemap.

  • Date semantics — The site does not turn a calendar date into a universal midnight launch. Cinema showtimes, regional storefront unlocks, venue schedules, and local observances can differ by region. Annual events roll forward to their next occurrence, and Black Friday is derived from the Friday after US Thanksgiving.

  • Custom countdowns — /create/ lets a user enter a title, date, description, optional image, emoji, and category, then copy a share URL or generate a client-side image card. Saved countdowns remain in browser localStorage; custom state is encoded in the /c/ URL shell, which is noindex.

  • Client-side live display — The visible days, hours, minutes, and seconds are calculated in the browser. This MCP exposes static site knowledge and date rules, not a live timer feed or a user's saved countdowns.

Use Cases

Visitors can use a verified event page to understand what a published date means before adding it to a calendar or sharing it. They can create a private countdown for a personal milestone, or use a category page to browse public events. For a current remaining-time value, newly published event, or under-review page, the official site is the source of truth.

Who Is It For

Countdowns Online is for people planning around releases, holidays, sports, seasonal dates, and personal milestones. It is most useful when the date has regional or source-verification context that a generic timer would hide. This MCP intentionally stays read-only and conservative: it does not claim that an unverified date is confirmed or that every event has one globally applicable time.

Tools

get_countdown_overview

Return the canonical countdown categories, verified date semantics, and public entry points exposed by the site. (Countdowns Online)

Input: no parameters. Returns: text/markdown.

get_official_links

Return the canonical list of official links for Countdowns Online (website, support, docs when available).

Input: no parameters. Returns: text/markdown.

Resources

  • site://countdowns-online/events — Verified event dates, recurrence rules, regional timing semantics, and custom countdown entry points.

  • site://countdowns-online/faq — Short FAQ generated from public site metadata.

  • site://countdowns-online/links — Canonical URLs to share with users.

Prompts

tell_me_about_countdowns_online

Summarize what the site is, who it's for, and how it works. — Countdowns Online

choose_a_countdown_countdowns_online

Choose a countdown while respecting date verification and regional timing. — Countdowns Online

Installation

Install via Smithery

npx -y @smithery/cli install countdowns-online-mcp --client claude

(Replace claude with cursor, windsurf, or continue for those clients.)

Install from source

git clone https://github.com/Rocniubi/countdowns-online-mcp.git
cd countdowns-online-mcp
pnpm install

Then add to your MCP client config (claude_desktop_config.json for Claude Desktop, mcp.json for Cursor / Windsurf / Continue):

{
  "mcpServers": {
    "countdowns-online-mcp": {
      "command": "node",
      "args": [
        "/absolute/path/to/countdowns-online-mcp/src/index.mjs"
      ]
    }
  }
}

Debug with MCP Inspector

npx @modelcontextprotocol/inspector node src/index.mjs

Official Links

Development

pnpm install
pnpm start                 # run the server over stdio

License

MIT

Available Tools

2 tools
get_countdown_overviewA

Return the canonical countdown categories, verified date semantics, and public entry points exposed by the site. (Countdowns Online)

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Without annotations, the description carries the burden. It indicates a read-only operation by stating 'Return...', but does not address authentication, rate limits, or other behavioral aspects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, concise sentence that front-loads the action and clearly communicates the tool's purpose without wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no parameters and no output schema, the description adequately specifies what the tool returns. However, it could hint at the return structure since there is no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

No parameters exist, so the input schema fully covers them. The description does not need to add parameter details, achieving the baseline for zero-parameter tools.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Return') and the specific resources ('canonical countdown categories, verified date semantics, and public entry points'), which distinguishes it from the sibling tool 'get_official_links'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use when needing an overview of countdown categories, but does not explicitly state when to use it versus alternatives or note any prerequisites or restrictions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updatesv0.1.0
    • First observedget_countdown_overview
    • First observedget_official_links
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.9/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have distinctly different purposes: one provides an overview of countdown categories and date semantics, the other returns official links. There is no overlap in functionality.

Naming Consistency5/5

Both tools follow the consistent pattern 'get_<descriptive_noun>', using snake_case and the verb 'get' for read operations.

Tool Count3/5

With only 2 tools, the server feels thin for a domain that likely involves multiple countdown entities and operations. While the tools are focused, the count is borderline minimal.

Completeness2/5

The server only offers informational tools (overview and links). There are no tools to retrieve, create, or manage specific countdowns, leaving significant gaps for any practical use.

Resources

Related MCP Connectors

Related MCP Servers

  • mcp-ctftime

    tomek7667
    A
    license
    A
    quality
    C
    maintenance
    Enables AI assistants to query CTF (Capture The Flag) cybersecurity competition data from CTFtime.org, including events, team rankings, results, and votes through the public CTFtime API.
    7
    39 npm
    MIT

  • EndOfLife MCP Server

    brianprost
    A
    license
    A
    quality
    F
    maintenance
    Provides access to the endoflife.date API to query support and end-of-life information for thousands of software products. It enables users to retrieve detailed release schedules, lifecycle data, and product categories through natural language.
    16
    7
    353 npm
    MIT

  • YearAtAGlance MCP Server

    mindfullabai
    A
    license
    A
    quality
    D
    maintenance
    Integrates the YearAtAGlance calendar with AI assistants to manage events, categories, and event density heatmaps. It enables users to perform CRUD operations on calendar data and utilize AI-powered features like natural language milestone creation and yearly analysis.
    15
    5 npm
    MIT