emilia-guard vs Proof Holdings
emilia-guard is a plugin bundle for AI coding tools published by EMILIA Protocol. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Proof Holdings is an MCP server published by proof.holdings. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-30. 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 |   Proof Holdings |
|---|---|---|
| Community marketplace emiliaprotocol/emilia-protocol | Listed Version: 0.1.0 Forks (GitHub): 18 Stars (GitHub): 601 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.7.1 Downloads/month (npm): 739 Downloads/week (npm): 422 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.7.1 Downloads/month (npm): 739 Downloads/week (npm): 422 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 | emilia-guard | Proof Holdings |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 601 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 18 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-26 |
| Where it runs (differs) | On your machine (@emilia-protocol/mcp-server) | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | 2, secrets among them: 1 | 2, secrets among them: 1 |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/emiliaprotocol/emilia-protocol | github.com/proofholdings/mcp-server |
| Changes in the last 7 days (differs) | 0 | 3 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 43 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.
Proof Holdings
One API, all things verified — control, delegation, human approval, anti-impersonation.
How to run each
emilia-guard As a Claude Code plugin
/plugin marketplace add emiliaprotocol/emilia-protocol
/plugin install emilia-guard@emilia-protocolProof Holdings As a remote MCP server
claude mcp add --transport http proof-holdings https://api.proof.holdings/mcpRequires: PROOF_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Proof Holdings has a remote endpoint we check. How we check endpoints
Tools each declares
Neither the marketplaces of emilia-guard nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
Only emilia-guard asks for
EP_API_KEY (secret)EP_BASE_URL
Only Proof Holdings asks for
PROOF_API_KEY (secret)PROOF_BASE_URL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: emilia-guard · What it can do: Proof Holdings · 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.