Countdowns Online MCP
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Countdowns Online MCPShow me the countdown categories"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Countdowns Online MCP Server
Countdown Timers - How Many Days Until | Countdowns Online
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 installThen 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.mjsOfficial Links
Website: https://countdowns.online
Development
pnpm install
pnpm start # run the server over stdioLicense
MIT
Available Tools
2 toolsget_countdown_overviewA
Return the canonical countdown categories, verified date semantics, and public entry points exposed by the site. (Countdowns Online)
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It only describes what is returned without mentioning any side effects, authentication requirements, or whether it is read-only.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence that efficiently conveys the tool's purpose without extraneous words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with no parameters and no output schema, the description fully covers what the tool returns, including the site context via '(Countdowns Online)'.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With no parameters (0 params), the baseline is 4. The description does not need to add parameter details.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns 'canonical countdown categories, verified date semantics, and public entry points'. It distinguishes itself from sibling 'get_official_links' by focusing on the countdown overview rather than links.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage when an overview of countdown categories and entry points is needed, but does not provide explicit when-to-use or when-not-to-use guidance compared to the sibling tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_official_linksA
Return the canonical list of official links for Countdowns Online (website, support, docs when available).
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden. The verb 'Return' implies a read-only operation, but no explicit statement about side effects or behavioral traits. Minimal but adequate given the simplicity.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence, 16 words, no filler. All information is front-loaded and essential.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple 0-parameter tool with no output schema, the description sufficiently explains the return value and scope. Could be slightly improved by noting the format or any limitations, but overall adequate.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, and the schema coverage is 100%. The description adds meaning by specifying the output (links for website, support, docs), which is beyond the empty schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Return' and the resource 'canonical list of official links', specifying the contents (website, support, docs). It distinguishes from the sibling tool 'get_countdown_overview' by focusing solely on links.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies the tool should be used for obtaining official links, but does not explicitly state when to use it versus the sibling (get_countdown_overview) or provide any exclusion criteria.
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. Dates show when Glama detected each change.
2 tool updates
v0.1.0- First observed
get_countdown_overview - First observed
get_official_links
TDQS
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.
Both tools follow the consistent pattern 'get_<descriptive_noun>', using snake_case and the verb 'get' for read operations.
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.
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
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Time and date math for AI agents: Unix timestamp conversion, DST-correct time zone conversion, durations, epoch arithmetic, cron schedules, and holiday countdowns. Eight tools, no key.
Current time, timezone conversion & date math for AI agents. On Cloudflare Workers.
Public holiday data for 30+ countries. Check holidays, working days and calendars via AI assistants.
Search indexed websites, read raw page markdown, and score AI visibility for any site.
Related MCP Servers
- AlicenseAqualityCmaintenanceEnables 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.746MIT
- AlicenseAqualityFmaintenanceProvides 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.7343MIT
- AlicenseAqualityDmaintenanceIntegrates 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.1512MIT
- AlicenseNot gradedqualityCmaintenanceWraps PredictHQ Events API to enable AI agents to query global event data through natural language, part of Pipeworx gateway.8MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Rocniubi/countdowns-online-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server