Time (Reference) vs Whether the current UTC year is a leap year
Time (Reference) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). Whether the current UTC year is a leap year is an MCP server published by sadri-dridi. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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
| Marketplace |  Time (Reference) |  Whether the current UTC year is a leap year |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:9c46a918633f Forks (GitHub): 11 793 Pulls (Docker Hub): 1 016 770 Stars (Docker Hub): 9 Stars (GitHub): 91 324 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 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
| Fact | Time (Reference) | Whether the current UTC year is a leap year |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 91 324 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 1 016 770 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 11 793 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/time) | Remote server (agent-observatory-sensor.nolimit-observatory.workers.dev/s/leap-utc/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 2 | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | NOASSERTION | Not stated |
| Repository (differs) | github.com/modelcontextprotocol/servers | github.com/sadri-dridi/named-mcp-utilities |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 2 days ago |
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)
Time and timezone conversion capabilities.
Whether the current UTC year is a leap year
Whether the current UTC year is a leap year
How to run each
Time (Reference) As a local MCP server: Docker image
claude mcp add --transport stdio time -- docker run -i --rm mcp/timeWhether the current UTC year is a leap year As a remote MCP server
claude mcp add --transport http leap-utc https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/leap-utc/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Whether the current UTC year is a leap year has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Whether the current UTC year is a leap year publish no list of tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Time (Reference) · What it can do: Whether the current UTC year is a leap year · 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.