In-depth architectural comparison of the Feranor Resilience and Emilia Protocol MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Feranor Resilience
Security · Remote HTTP/SSE
Quality: 69/100 (Great) | Auth: No auth required
Emilia Protocol
Security · Local stdio
Quality: 71/100 (Great) | Auth: No auth required
Verdict Summary: Choose Feranor Resilience if you need specialized Security tools running via a hosted cloud SSE transport. Choose Emilia Protocol if your workspace requires Security integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Feranor Resilience when:
You need dedicated capabilities in the Security domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Freemium).
Primary tools included: Invisible Unicode and homoglyph detection, Text cleanup with before-and-after risk comparison, Domain scores across TLS, DNS, headers, and speed.
Scan/purge hidden text & score web domains: TLS, DNS, headers, speed. Free scans, $0.01 actions.The Tools:
text_scan_v1 — free
Scans a text string for invisible Unicode characters, homoglyphs, and normalization issues. Returns a risk score, a list of flagged characters, and detected homoglyphs. Never modifies the input text.
text_purge_v1 — $0.01 per call
Removes invisible Unicode characters and replaces homoglyphs in a text string, then normalizes the result. Returns the cleaned text plus a before-and-after risk comparison.
domain_check_score_v1 — free
Overall score, per-category scores, and how many findings each category raised. Use it to triage: rank a list of domains, confirm one is healthy, or decide whether the full report is worth pulling. It tells you which categories are weak and how many issues they hold, but not what the issues are.
domain_check_score_batch_v1 — free
The same triage scores for up to 100 domains in a single call. One score summary per distinct domain: overall score, per-category scores, and how many findings each category raised. Never the findings themselves.
domain_check_v1 — $0.01 per call
Full report for one domain: weighted score out of 100, per-category breakdown, and every individual finding with a prioritised remediation order.
domain_check_batch_v1 — from $0.005 per domain
The same full report for up to 100 domains in a single call, with one payment for the whole batch instead of one per domain. Both cheaper per domain and much faster than calling domain_check_v1 in a loop.
Tools & Capabilities Breakdown
Feranor Resilience Tools (5)
Invisible Unicode and homoglyph detection
Text cleanup with before-and-after risk comparison
Domain scores across TLS, DNS, headers, and speed
Single-domain detailed findings with remediation priority
Batch scoring and reporting for up to 100 domains
Emilia Protocol Tools (3)
ep_guard_action
Request 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.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Feranor Resilience is categorized under Security and uses a remote streaming HTTP/SSE transport. In contrast, Emilia Protocol belongs to Security using local stdio subprocess. Select Feranor Resilience when you need capabilities focused on security and Emilia Protocol when you require tools for security.
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.
Poll 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_receipt
Ask 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.