zerm vs io.github.rog0x/time
zerm is an MCP server published by zerm.dev. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.rog0x/time is an MCP server published by rog0x. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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 |  zerm |  io.github.rog0x/time |
|---|---|---|
| Official MCP Registry | Listed Version: 0.3.3 No figure published Not marked · First seen |
Listed Version: 1.0.2 Downloads/month (npm): 156 Downloads/week (npm): 38 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 | zerm | io.github.rog0x/time |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (zerm.dev/mcp) | On your machine (@rog0x/mcp-time-tools) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/rog0x/mcp-time-tools |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | not checked yet | 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
zerm
Agent utility belt: memory, locks, webhook inboxes, timers, DNS, email, URL, timezone, cron
io.github.rog0x/time
Timezone, dates, cron, timestamps for AI agents
How to run each
zerm As a remote MCP server
claude mcp add --transport http zerm https://zerm.dev/mcpio.github.rog0x/time As a local MCP server: npm package
claude mcp add --transport stdio time -- npx -y @rog0x/mcp-time-toolsCommands built only from what the marketplaces declare; the full set for every client is on each card.
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: zerm · What it can do: io.github.rog0x/time · 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.