Ext Ops Panel
Open dashboard
Comparison

claude-time vs io.github.cyanheads/reference-data-mcp-server

claude-time is a plugin bundle for AI coding tools published by nexusbuildsai. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.cyanheads/reference-data-mcp-server is an MCP server published by cyanheads. 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

Where each is published
Marketplaceclaude-timeio.github.cyanheads/reference-data-mcp-server
Claude Code: claude-plugins-community Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.17
Downloads/month (npm): 999
Downloads/week (npm): 325
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

claude-time vs io.github.cyanheads/reference-data-mcp-server
Factclaude-timeio.github.cyanheads/reference-data-mcp-server
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)1 (better)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (reference-data.caseyjhand.com/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published6, secrets among them: 0
Hooks it runs (differs)1Not published
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/nexusbuildsai/claude-timegithub.com/cyanheads/reference-data-mcp-server
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 3 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

claude-time

In its own words, on Claude Code: claude-plugins-community:

Live local time + timezone injected into every prompt. Stamps every response with [HH:MM AM/PM TZ]

io.github.cyanheads/reference-data-mcp-server

In its own words, on Official MCP Registry:

Countries, timezones, elements, constants, HTTP status codes, unit conversion, and MIME type lookup.

How to run each

claude-time As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install claude-time@claude-community

io.github.cyanheads/reference-data-mcp-server As a remote MCP server

Claude Code
claude mcp add --transport http reference-data-mcp-server https://reference-data.caseyjhand.com/mcp

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

Only io.github.cyanheads/reference-data-mcp-server has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of claude-time publish no settings it asks for, so we do not compare settings.

What it can do: claude-time · What it can do: io.github.cyanheads/reference-data-mcp-server · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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