emilia-guard vs SQLGuard — Execution Certificate Firewall
emilia-guard is a plugin bundle for AI coding tools published by EMILIA Protocol. Marketplaces we read that list it: 1 (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-15. 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 |  emilia-guard | |
|---|---|---|
| Community marketplace emiliaprotocol/emilia-protocol | Listed Version: 0.1.0 Forks (GitHub): 16 Stars (GitHub): 611 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | 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
| Fact | emilia-guard | SQLGuard — Execution Certificate Firewall |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 611 | No figure on GitHub |
| Forks (GitHub) (differs) | 16 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@emilia-protocol/mcp-server) | Remote server (sqlguard.io/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/emiliaprotocol/emilia-protocol | github.com/cabbageandtea/sqlguard |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 41 h ago |
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
emilia-guard
Hold irreversible Claude tool calls until a named human approves on their own device; mint an offline-verifiable Trust Receipt. Fail-closed.
SQLGuard — Execution Certificate Firewall
Permission before writes. Gravity→DENYs→Session $0.25. Pilot $100; Gateway $299. Probe free.
How to run each
emilia-guard As a Claude Code plugin
/plugin marketplace add emiliaprotocol/emilia-protocol
/plugin install emilia-guard@emilia-protocolSQLGuard — Execution Certificate Firewall As a remote MCP server
claude mcp add --transport http sqlguard https://sqlguard.io/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only SQLGuard — Execution Certificate Firewall has a remote endpoint we check. How we check endpoints
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: emilia-guard · What it can do: SQLGuard — Execution Certificate Firewall · 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.