Ext Ops Panel
Open dashboard
Comparison

tempo vs World Business Calendar

tempo is a plugin bundle for AI coding tools published by Kip Cole. Marketplaces we read that list it: 1 (Community GitHub marketplaces). World Business Calendar is an MCP server published by groove79. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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
MarketplacetempoWorld Business Calendar
Community marketplace elixir-tempo/tempo Listed
Version: 0.1.0
Forks (GitHub): 7
Stars (GitHub): 215
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.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

tempo vs World Business Calendar
FacttempoWorld Business Calendar
Marketplaces that list it11
Stars (GitHub) (differs)215 (better)0 (worse)
Forks (GitHub) (differs)7 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@appmonster/mcp-world-calendar)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/elixir-tempo/tempogithub.com/groove79/kmcp
Changes in the last 7 days (differs)02
First seen (differs)2026-10-172026-10-23

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

tempo

In its own words, on Community GitHub marketplaces:

Turn a natural-language date/time problem into correct, validated Tempo (Elixir) — ISO 8601 / IXDTF representation plus relations, set algebra, recurrence, scheduling, and constraint networks — and get a plain-language answer.

World Business Calendar

In its own words, on Official MCP Registry:

Public holidays and working-day math for 200+ countries and regions, local weekends. No keys.

How to run each

tempo As a Claude Code plugin

Claude Code
/plugin marketplace add elixir-tempo/tempo
/plugin install tempo@tempo-plugins

World Business Calendar As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio mcp-world-calendar -- npx -y @appmonster/mcp-world-calendar

Commands 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: tempo · What it can do: World Business Calendar · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. 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