In-depth architectural comparison of the Catalyst Governance 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
Catalyst Governance
Security · Remote HTTP/SSE
Quality: 48/100 (Fair) | Auth: No auth required
Emilia Protocol
Security · Local stdio
Quality: 71/100 (Great) | Auth: No auth required
Verdict Summary: Choose Catalyst Governance 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 Catalyst Governance when:
You need dedicated capabilities in the Security domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Governance middleware for AI agents: permission gates, approvals, compliance scanning, audit ledger.
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.
Category & Scope
Tools & Capabilities Breakdown
Catalyst Governance Tools (10)
catalyst_my_governance
Show your governance profile and plan capabilities
catalyst_check_action
Check if a capability is permitted before acting
catalyst_log_task
Record a task or action into the governance pipeline
catalyst_pending_approvals
List proposals awaiting human sign-off
catalyst_await_approval
Poll a specific proposal's approval status
catalyst_register_approval_webhook
Register a callback URL for approval events
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).
Catalyst Governance is categorized under Security and uses a remote streaming HTTP/SSE transport. In contrast, Emilia Protocol belongs to Security using local stdio subprocess. Select Catalyst Governance when you need capabilities focused on security and Emilia Protocol when you require tools for security.
Run an automated compliance scan (requires add-on)
catalyst_list_compliance_frameworks
List available compliance frameworks
catalyst_get_dashboard
Get the governance dashboard snapshot
catalyst_export_ledger
Export the hash-linked audit chain
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.
ep_check_signoff
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.