Ext Ops Panel
Open dashboard
Comparison

Time (Reference) vs America/Monterrey clock

Time (Reference) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 2 (Docker MCP Catalog, PyPI (MCP servers)). America/Monterrey clock 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-11-08. 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)America/Monterrey clock
Docker MCP Catalog Listed
Version: sha256:9c46a918633f
Forks (GitHub): 11 923
Pulls (Docker Hub): 1 068 620
Stars (Docker Hub): 9
Stars (GitHub): 91 847
Not marked · First seen
Not listed
PyPI (MCP servers) Listed
Version: 2026.11.4
Downloads/month (PyPI): 589 169
Downloads/week (PyPI): 171 445
Forks (GitHub): 11 923
Stars (GitHub): 91 847
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

Time (Reference) vs America/Monterrey clock
FactTime (Reference)America/Monterrey clock
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)91 847 (better)0 (worse)
Pulls (Docker Hub) (differs)1 068 620No figure on Docker Hub
Forks (GitHub) (differs)11 923 (better)0 (worse)
Last release (differs)2026-11-05Not published
Where it runs (differs)On your machine (mcp/time)Remote server (agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-america-monterrey/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)2Not published
Environment variables it asks forNot publishedNot published
Licence (differs)NOASSERTIONNot stated
Repository (differs)github.com/modelcontextprotocol/serversgithub.com/sadri-dridi/named-mcp-utilities
Changes in the last 7 days (differs)10
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 23 h 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)

In its own words, on Docker MCP Catalog:

Time and timezone conversion capabilities.

America/Monterrey clock

In its own words, on Official MCP Registry:

Current local time in America/Monterrey.

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

America/Monterrey clock As a remote MCP server

Claude Code
claude mcp add --transport http tz-america-monterrey https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-america-monterrey/mcp

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

Only America/Monterrey clock has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of America/Monterrey clock 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: America/Monterrey clock · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Package data comes from the Python Package Index (pypi.org). 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