Ext Ops Panel
Open dashboard
Comparison

io.github.Aggrete/aggrete vs SQLGuard — Execution Certificate Firewall

io.github.Aggrete/aggrete is an MCP server published by Aggrete. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). SQLGuard — Execution Certificate Firewall is an MCP server published by cabbageandtea. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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
Marketplaceio.github.Aggrete/aggreteSQLGuard — Execution Certificate Firewall
Official MCP Registry Listed
Version: 0.8.3
Downloads/month (PyPI): 2 518
Downloads/week (PyPI): 623
Forks (GitHub): 2
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 1.1.20
No figure published
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

io.github.Aggrete/aggrete vs SQLGuard — Execution Certificate Firewall
Factio.github.Aggrete/aggreteSQLGuard — Execution Certificate Firewall
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)1No figure on GitHub
Forks (GitHub) (differs)2No figure on GitHub
Last release (differs)2026-10-11Not published
Where it runs (differs)On your machine (aggrete)Remote server (sqlguard.io/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 0Not published
Parts of the bundle (differs)2Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/aggrete/aggretegithub.com/cabbageandtea/sqlguard
Changes in the last 7 days (differs)30
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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

io.github.Aggrete/aggrete

In its own words, on Official MCP Registry:

MCP policy proxy: enforces a code of conduct across connectors before the upstream is called.

SQLGuard — Execution Certificate Firewall

In its own words, on Official MCP Registry:

Permission before writes. Gravity→DENYs→Session $0.25. Pilot $100; Gateway $299. Probe free.

How to run each

io.github.Aggrete/aggrete As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio aggrete -- uvx aggrete

SQLGuard — Execution Certificate Firewall As a remote MCP server

Claude Code
claude mcp add --transport http sqlguard https://sqlguard.io/mcp

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 SQLGuard — Execution Certificate Firewall publish no settings it asks for, so we do not compare settings.

What it can do: io.github.Aggrete/aggrete · What it can do: SQLGuard — Execution Certificate Firewall · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. 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