Ext Ops Panel
Open dashboard
Comparison

cache-clock vs io.github.dcostenco/prism-coder

cache-clock is a plugin bundle for AI coding tools published by Ray Amjad. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.dcostenco/prism-coder is an MCP server published by dcostenco. Marketplaces we read that list it: 3 (Official MCP Registry, npm registry (MCP servers), Community GitHub marketplaces). As of our marketplace pass on 2026-11-10. 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-clockio.github.dcostenco/prism-coder
Community marketplace ray-amjad/awesome-claude-code-function-hooks Listed
Version: 0.5.4
Forks (GitHub): 21
Stars (GitHub): 112
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 20.22.4
Downloads/month (npm): 5 043
Downloads/week (npm): 859
Forks (GitHub): 28
Stars (GitHub): 156
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 20.22.4
Downloads/month (npm): 5 043
Downloads/week (npm): 859
Forks (GitHub): 28
Stars (GitHub): 156
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 io.github.dcostenco/prism-coder
Factcache-clockio.github.dcostenco/prism-coder
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)112 (worse)156 (better)
Forks (GitHub) (differs)21 (worse)28 (better)
Last release (differs)Not published2026-10-28
Where it runs (differs)Installs as a plugin bundleOn your machine (prism-mcp-server)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published8, secrets among them: 3
Parts of the bundle (differs)Not published2
Licence (differs)MITApache-2.0
Repository (differs)github.com/ray-amjad/awesome-claude-code-function-hooksgithub.com/dcostenco/prism-coder
Changes in the last 7 days00
First seen (differs)2026-11-032026-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 one-line band above the prompt: context used, and a countdown until the prompt cache goes cold

io.github.dcostenco/prism-coder

In its own words, on Official MCP Registry:

Session memory for coding agents: local-first recall, drift detection, on-device inference.

How to run each

cache-clock As a Claude Code plugin

Claude Code
/plugin marketplace add ray-amjad/awesome-claude-code-function-hooks
/plugin install cache-clock@claude-code-mods

io.github.dcostenco/prism-coder As a local MCP server: npm package

Claude Code
claude mcp add --env "BRAVE_API_KEY=<YOUR_BRAVE_API_KEY>" --env "GEMINI_API_KEY=<YOUR_GEMINI_API_KEY>" --env "SUPABASE_KEY=<YOUR_SUPABASE_KEY>" --transport stdio prism-coder -- npx -y prism-mcp-server

Requires: BRAVE_API_KEY (secret), GEMINI_API_KEY (secret), SUPABASE_KEY (secret)

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

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: io.github.dcostenco/prism-coder · 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. Package data comes from the public npm registry (registry.npmjs.org). 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