Emilia Protocol vs Ssid MCP

A side-by-side look at the Emilia Protocol and Ssid MCP 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 requiredSsid MCP logoSsid MCPSecurity · Local subprocess (stdio)Identify the manufacturer behind any MAC address; flags randomized/private addresses.56GoodAuth: not declared

Verdict: choose Emilia Protocol for security work as a local process; choose Ssid MCP 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

Ssid MCP logoChoose Ssid MCP when

  • You need dedicated capabilities in the Security domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: SSID_API_KEY.
  • You want tools like get_router_defaults, check_router_compliance, lookup_mac.
Explore Ssid MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecEmilia Protocol logoEmilia ProtocolSsid MCP logoSsid MCP
CategorySecuritySecurity
Quality signal71/100 · Great56/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedSSID_API_KEY
Verified ownerCommunity listingCommunity listing
GitHub stars5991
Directory activity 6 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools34

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.

Ssid MCP tools 4

  • get_router_defaultsDefault gateway IP, admin username and password (or the fact that there is none), credential type and factory-reset steps for a router or gateway model, each cited to the manufacturer's own documentation with the source URL. Pass the ssid.ai slug, or brand plus model. Use after lookup_mac identifies the vendor, or whenever a user asks for a router's default login, factory password, gateway address or reset procedure. Covers the 409-model ssid.ai directory; no listing or wildcard search.
  • check_router_complianceWhether a router model still ships a universal default password, the pattern prohibited for consumer connectable products under the UK PSTI Act and targeted by the EU Cyber Resilience Act, based on the manufacturer-cited credential type, with the ssid.ai Router Compliance Index totals for context. Pass the ssid.ai slug (get it from get_router_defaults). Documentation reading, not legal advice.
  • lookup_macIdentify the organisation behind a MAC address and detect randomized/private (locally-administered) addresses used by modern phones. Resolves the IEEE registries longest-prefix-first, so an address inside a block the IEEE subdivided returns the company that actually holds it (MA-M, MA-S or IAB) rather than the MA-L registrar. Returns vendor, blockType (MA-L | MA-M | MA-S | IAB), block start/end for a sub-block, OUI, kind, randomized flag, confidence and the source registry file. A randomized address keeps vendor: null and adds cidRegistrant when its prefix is a registered Company ID (DA:A1:19 is Google's). For the router's factory login, call get_router_defaults next.
  • submit_correctionPropose a fix to a router model's default gateway IP, username, password, credential type, or reset steps on ssid.ai. Requires an official manufacturer source URL (never an aggregator/forum). Queued for verification — never applied automatically. Use the router's slug from ssid.ai/routers/<slug>. Requires an ssid Pro key ($15/mo, ssid.ai/pricing) sent as SSID_API_KEY or a Bearer token; the three read tools stay free.

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"
      ]
    }
  }
}

Ssid MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "ssid-mcp-2": {
      "command": "npx",
      "args": [
        "-y",
        "ssid-mcp"
      ],
      "env": {
        "SSID_API_KEY": "YOUR_SSID_API_KEY_HERE"
      }
    }
  }
}

Frequently asked questions

Emilia Protocol is categorized under Security and uses a local stdio subprocess. Ssid MCP belongs to Security and uses a local stdio subprocess. Pick Emilia Protocol for security work and Ssid MCP 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. Ssid MCP 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 ssid-mcp-2 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 599 GitHub stars. Ssid MCP has 56/100 (Good) with 1 views, 0 installs and 1 GitHub stars.