Ext Ops Panel
Open dashboard
Comparison

io.github.jmavid/time-mcp vs io.github.ryudi84/timestamp

io.github.jmavid/time-mcp is an MCP server published by jmavid. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.ryudi84/timestamp is an MCP server published by ryudi84. 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
Marketplaceio.github.jmavid/time-mcpio.github.ryudi84/timestamp
Official MCP Registry Listed, marked deprecated
Version: 1.0.0
No figure published
Not marked · First seen
Listed
Version: 1.0.3
Downloads/month (npm): 205
Downloads/week (npm): 50
Forks (GitHub): 2
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

io.github.jmavid/time-mcp vs io.github.ryudi84/timestamp
Factio.github.jmavid/time-mcpio.github.ryudi84/timestamp
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub1
Forks (GitHub) (differs)No figure on GitHub2
Last releaseNot publishedNot published
Where it runs (differs)Remote server (time-mcp.jmavid.workers.dev/mcp)On your machine (timestamp-forge-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/ryudi84/sovereign-mcp-servers
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Answered with HTTP 404 (2 days ago)no remote endpoint we check

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

io.github.jmavid/time-mcp

In its own words, on Official MCP Registry:

Current time, timezone conversion & date math for AI agents. On Cloudflare Workers.

io.github.ryudi84/timestamp

In its own words, on Official MCP Registry:

MCP server for timestamp conversion — Unix, ISO 8601, relative time

How to run each

io.github.jmavid/time-mcp As a remote MCP server

Claude Code
claude mcp add --transport http time-mcp https://time-mcp.jmavid.workers.dev/mcp

io.github.ryudi84/timestamp As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio timestamp -- npx -y timestamp-forge-mcp

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

Only io.github.jmavid/time-mcp 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

Neither one's marketplaces publish the settings it asks for.

What it can do: io.github.jmavid/time-mcp · What it can do: io.github.ryudi84/timestamp · Compare two other plugins

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