MCP Tenant Isolation vs Emilia Protocol

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

MCP Tenant Isolation logoMCP Tenant IsolationSecurity · Local subprocess (stdio)Static analysis scanner for MCP server code and multi-tenant SaaS applications.57GoodAuth: not declaredEmilia 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 required

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

Which MCP server should you choose?

MCP Tenant Isolation logoChoose MCP Tenant Isolation when

  • You need dedicated capabilities in the Security domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like scan_tenant_isolation, list_tenant_isolation_rules, explain_tenant_isolation_rule.
Explore MCP Tenant Isolation

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

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMCP Tenant Isolation logoMCP Tenant IsolationEmilia Protocol logoEmilia Protocol
CategorySecuritySecurity
Quality signal57/100 · Good71/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars4598
Directory activity 1 views 0 installs 0 upvotes 6 views 0 installs 0 upvotes
Tools43

Tools & capabilities

MCP Tenant Isolation tools 4

  • scan_tenant_isolationScan a project path. Returns structured findings with completeness, coverage, concern families, and receipt.
  • list_tenant_isolation_rulesReturns all 57 rules with metadata. Filterable by category.
  • explain_tenant_isolation_ruleReturns rule details, OWASP mapping, CWE IDs, fix suggestions.
  • suppress_tenant_isolation_findingAdd a suppression with reason, approver, controls, and expiry.

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.

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.

MCP Tenant Isolation

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mcp-tenant-isolation": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-tenant-isolation"
      ]
    }
  }
}

Emilia Protocol

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

Frequently asked questions

MCP Tenant Isolation is categorized under Security and uses a local stdio subprocess. Emilia Protocol belongs to Security and uses a local stdio subprocess. Pick MCP Tenant Isolation for security work and Emilia Protocol 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.

MCP Tenant Isolation has no declared pricing — check the project's own site. Emilia Protocol is listed as free. Auth: no auth required. 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 mcp-tenant-isolation and emiliaprotocol-emilia-protocol as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, MCP Tenant Isolation has a quality signal of 57/100 (Good) with 1 views, 0 installs and 4 GitHub stars. Emilia Protocol has 71/100 (Great) with 6 views, 0 installs and 598 GitHub stars.