Emilia Protocol vs Aegis

A side-by-side look at the Emilia Protocol and Aegis MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Emilia Protocol logoEmilia ProtocolSecurity · Local subprocess (stdio)Human sign-off + trust receipts for AI agents: requires a named human's approval before an irreversible action (payment release, record change, deploy), then mints an offline-verifiable Ed25519 Trust Receipt. Also exposes trust profiles, receipt verification, disputes, and delegation. Apache-2.0; policy engine formally verified. Install: npx -y @emilia-protocol/mcp-server.71GreatAuth: no auth requiredAegis logoAegisSecurity · Local subprocess (stdio)Credential isolation proxy for AI agents. Injects secrets at the network boundary with domain restrictions, agent authentication, and audit logging. No SDK required — works as a transparent HTTP proxy or MCP server.53GoodAuth: not declared

Verdict: choose Emilia Protocol for security work as a local process; choose Aegis for security as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Emilia Protocol logoChoose Emilia Protocol when

  • You need dedicated capabilities in the Security domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like ep_guard_action, ep_check_signoff, ep_verify_receipt.
Explore Emilia Protocol

Aegis logoChoose Aegis when

  • You need dedicated capabilities in the Security domain.
  • You prefer a local stdio subprocess transport.
Explore Aegis

Feature & specification comparison

Rows where the two servers differ are marked.

SpecEmilia Protocol logoEmilia ProtocolAegis logoAegis
CategorySecuritySecurity
Quality signal71/100 · Great53/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars61114
Directory activity 6 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
Tools3Not listed

Tools & capabilities

Emilia Protocol tools 3

  • ep_guard_actionRequest authorization before an irreversible action: payments, wire transfers, fund releases, deletions, record or account changes, or sending messages with real-world effect. Submits the exact action for policy evaluation and human authorization. This MCP tool does not itself sit at the executor choke point: even after approval, the executor MUST match the returned action_hash and atomically consume the receipt before effect. If BLOCKED, poll ep_check_signoff with the receipt_id.
  • ep_check_signoffPoll a pending authorization after ep_guard_action returns BLOCKED. Pass the receipt_id. Returns PENDING, APPROVED_PENDING_CONSUME, CONSUMED, or DENIED. Approval alone is not permission to execute: the executor must match action_hash and atomically consume the receipt at its own choke point.
  • ep_verify_receiptAsk the configured EMILIA service to verify a stored trust receipt and report its hash and anchor status. Read-only, but not an offline verifier: the result is the service response for the supplied receipt_id.

Aegis tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Emilia Protocol

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "emiliaprotocol-emilia-protocol": {
      "command": "npx",
      "args": [
        "-y",
        "@emilia-protocol/mcp-server"
      ]
    }
  }
}

Aegis

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "getaegis-aegis": {
      "command": "npx",
      "args": [
        "-y",
        "@getaegis/cli"
      ]
    }
  }
}

Frequently asked questions

Emilia Protocol is categorized under Security and uses a local stdio subprocess. Aegis belongs to Security and uses a local stdio subprocess. Pick Emilia Protocol for security work and Aegis for security.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Emilia Protocol is listed as free. Auth: no auth required. Aegis has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add emiliaprotocol-emilia-protocol and getaegis-aegis as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Emilia Protocol has a quality signal of 71/100 (Great) with 6 views, 0 installs and 611 GitHub stars. Aegis has 53/100 (Good) with 2 views, 0 installs and 14 GitHub stars.