Ext Ops Panel
Open dashboard
Comparison

cache-clock vs Prometheus MCP Server

cache-clock is a plugin bundle for AI coding tools published by Hamza Zafar. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Prometheus MCP Server is an MCP server published by pab1it0. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-10-22. 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
Marketplacecache-clockPrometheus MCP Server
Community marketplace hamzafer/claude-code-mods Listed
Version: 0.1.1
Forks (GitHub): 34
Stars (GitHub): 330
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.6.2
Forks (GitHub): 104
Stars (GitHub): 519
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:3c3921301229
Forks (GitHub): 104
Stars (GitHub): 519
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

cache-clock vs Prometheus MCP Server
Factcache-clockPrometheus MCP Server
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)330 (worse)519 (better)
Forks (GitHub) (differs)34 (worse)104 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (ghcr.io/pab1it0/prometheus-mcp-server:1.6.2)
Transport (differs)Not statedstdio
Tools it declares (differs)Not published6
Environment variables it asks for (differs)Not published14, secrets among them: 2
Licence (differs)Not statedMIT
Repository (differs)github.com/hamzafer/claude-code-modsgithub.com/pab1it0/prometheus-mcp-server
Changes in the last 7 days (differs)20
First seen (differs)2026-10-202026-10-11

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

cache-clock

In its own words, on Community GitHub marketplaces:

A prompt-cache line under your status line, from Claude Code's own cache figures: time left while warm, hit rate and misses, and how many tokens the next message re-caches once cold. /cache-clock setup adds it.

Prometheus MCP Server

In its own words, on Official MCP Registry:

MCP server providing Prometheus metrics access and PromQL query execution for AI assistants

How to run each

cache-clock As a Claude Code plugin

Claude Code
/plugin marketplace add hamzafer/claude-code-mods
/plugin install cache-clock@claude-code-mods

Prometheus MCP Server As a local MCP server: Docker image

Claude Code
claude mcp add --env "PROMETHEUS_PASSWORD=<YOUR_PROMETHEUS_PASSWORD>" --env "PROMETHEUS_TOKEN=<YOUR_PROMETHEUS_TOKEN>" --env "PROMETHEUS_URL=<YOUR_PROMETHEUS_URL>" --transport stdio prometheus-mcp-server -- docker run -i --rm -e PROMETHEUS_PASSWORD -e PROMETHEUS_TOKEN -e PROMETHEUS_URL ghcr.io/pab1it0/prometheus-mcp-server:1.6.2

Requires: PROMETHEUS_PASSWORD (secret), PROMETHEUS_TOKEN (secret), PROMETHEUS_URL

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

Tools each declares

The marketplaces of cache-clock publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: cache-clock · What it can do: Prometheus MCP Server · 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. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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