alloydb vs Postgres Secured (Aegis Zero-Trust)
alloydb is a plugin bundle for AI coding tools published by gemini-cli-extensions. Marketplaces we read that list it: 3 (Claude Code: claude-plugins-official, Claude Code: claude-plugins-community, Community GitHub marketplaces). Postgres Secured (Aegis Zero-Trust) is an MCP server published by Yash-0620. 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
| Marketplace |  alloydb |  Postgres Secured (Aegis Zero-Trust) |
|---|---|---|
| Claude Code: claude-plugins-official | Listed Version: 0.2.0 Forks (GitHub): 6 Stars (GitHub): 24 Not marked · First seen |
Not listed |
| Claude Code: claude-plugins-community | Listed Version: 0.2.0 Forks (GitHub): 6 Stars (GitHub): 24 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.2 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 | alloydb | Postgres Secured (Aegis Zero-Trust) |
|---|---|---|
| Marketplaces that list it (differs) | 3 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 96 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 13 (better) | 0 (worse) |
| Last release (differs) | 2026-10-23 | Not published |
| Where it runs (differs) | On your machine (@toolbox-sdk/server) | Not stated |
| Transport | Not stated | Not stated |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 9, secrets among them: 1 | Not published |
| Parts of the bundle (differs) | 8 | Not a bundle |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/gemini-cli-extensions/alloydb | github.com/yash-0620/postgres-mcp |
| Changes in the last 7 days (differs) | 20 or more | 0 |
| First seen | 2026-10-11 | 2026-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
alloydb
Create, connect, and interact with an AlloyDB for PostgreSQL database and data.
Postgres Secured (Aegis Zero-Trust)
Enterprise PostgreSQL MCP secured by Aegis Zero-Trust to block unauthorized SQL injections.
How to run each
alloydb As a Claude Code plugin
/plugin install alloydb@claude-plugins-officialPostgres Secured (Aegis Zero-Trust)
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
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 Postgres Secured (Aegis Zero-Trust) publish no settings it asks for, so we do not compare settings.
What it can do: alloydb · What it can do: Postgres Secured (Aegis Zero-Trust) · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.