Ext Ops Panel
Open dashboard
Comparison

Time (Reference) vs io.github.theluckystrike/scheduling

Time (Reference) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.theluckystrike/scheduling is an MCP server published by theluckystrike. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceTime (Reference)io.github.theluckystrike/scheduling
Docker MCP Catalog Listed
Version: sha256:9c46a918633f
Forks (GitHub): 11 780
Pulls (Docker Hub): 1 004 327
Stars (Docker Hub): 9
Stars (GitHub): 91 180
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.22.3
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Time (Reference) vs io.github.theluckystrike/scheduling
FactTime (Reference)io.github.theluckystrike/scheduling
Marketplaces that list it11
Stars (GitHub) (differs)91 180 (better)1 (worse)
Pulls (Docker Hub) (differs)1 004 327No figure on Docker Hub
Forks (GitHub) (differs)11 780 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/time)Remote server or your machine
Transport (differs)stdioStreamable HTTP, stdio
Tools it declares (differs)2Not published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Licence (differs)NOASSERTIONNot stated
Repository (differs)github.com/modelcontextprotocol/serversgithub.com/theluckystrike/mcp-servers
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Time (Reference)

In its own words, on Docker MCP Catalog:

Time and timezone conversion capabilities.

io.github.theluckystrike/scheduling

In its own words, on Official MCP Registry:

Meeting scheduling across time zones: slot finding, DST checks, .ics invites.

How to run each

Time (Reference) As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio time -- docker run -i --rm mcp/time

io.github.theluckystrike/scheduling As a remote MCP server

Claude Code
claude mcp add --transport http scheduling https://mcp.zovo.one/mcp/scheduling

Requires: MCP_LICENSE_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of io.github.theluckystrike/scheduling publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Time (Reference) publish no settings it asks for, so we do not compare settings.

What it can do: Time (Reference) · What it can do: io.github.theluckystrike/scheduling · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built