Ext Ops Panel
Open dashboard
Comparison

chmonitor vs PostgreSQL Performance (read-only)

chmonitor is a plugin bundle for AI coding tools published by duyet. Marketplaces we read that list it: 1 (Community GitHub marketplaces). PostgreSQL Performance (read-only) is an MCP server published by gouranshul. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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
MarketplacechmonitorPostgreSQL Performance (read-only)
Community marketplace duyet/codex-claude-plugins Listed
Version: 2.0.0
Forks (GitHub): 1
Stars (GitHub): 15
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

chmonitor vs PostgreSQL Performance (read-only)
FactchmonitorPostgreSQL Performance (read-only)
Marketplaces that list it11
Stars (GitHub) (differs)15 (better)0 (worse)
Forks (GitHub) (differs)1 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (ghcr.io/gouranshul/pg-perf-mcp:0.1.0)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published4, secrets among them: 2
Parts of the bundle (differs)2Not a bundle
LicenceMITMIT
Repository (differs)github.com/duyet/codex-claude-pluginsgithub.com/gouranshul/pg-perf-mcp
Changes in the last 7 days22
First seen (differs)2026-10-192026-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

chmonitor

In its own words, on Community GitHub marketplaces:

Read-only ClickHouse monitoring and advice through the chmonitor MCP server, with pointers to its docs and codebase.

PostgreSQL Performance (read-only)

In its own words, on Official MCP Registry:

Read-only PostgreSQL performance diagnostics: slow queries, EXPLAIN, index advice, locks, functions

How to run each

chmonitor As a Claude Code plugin

Claude Code
/plugin marketplace add duyet/codex-claude-plugins
/plugin install chmonitor@duyet-claude-plugins

PostgreSQL Performance (read-only)

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Requires: MCP_API_KEY (secret), PGPERF_DB_PASSWORD (secret), PGPERF_DB_URL, PGPERF_DB_USER

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 chmonitor publish no settings it asks for, so we do not compare settings.

What it can do: chmonitor · What it can do: PostgreSQL Performance (read-only) · 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