Ext Ops Panel
Open dashboard
Comparison

Time (Reference) vs Ziplore: US ZIP Code API (county, time zone, demographics, radius)

Time (Reference) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). Ziplore: US ZIP Code API (county, time zone, demographics, radius) is an MCP server published by CyberMax-tools. 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)Ziplore: US ZIP Code API (county, time zone, demographics, radius)
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: 1.0.0
No figure published
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 Ziplore: US ZIP Code API (county, time zone, demographics, radius)
FactTime (Reference)Ziplore: US ZIP Code API (county, time zone, demographics, radius)
Marketplaces that list it11
Stars (GitHub) (differs)91 180No figure on GitHub
Pulls (Docker Hub) (differs)1 004 327No figure on Docker Hub
Forks (GitHub) (differs)11 780No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/time)Remote server (ziplore.cybermax-tools.workers.dev/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/cybermax-tools/product-factory
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 4 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.

Ziplore: US ZIP Code API (county, time zone, demographics, radius)

In its own words, on Official MCP Registry:

Ziplore: US ZIP to county, FIPS, time zone, Census demographics; radius and city ZIPs. Free, no key.

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

Ziplore: US ZIP Code API (county, time zone, demographics, radius)

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

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

Only Ziplore: US ZIP Code API (county, time zone, demographics, radius) has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Ziplore: US ZIP Code API (county, time zone, demographics, radius) 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: Ziplore: US ZIP Code API (county, time zone, demographics, radius) · 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