Emilia Protocol vs Shellward — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Emilia Protocol vs Shellward
In-depth architectural comparison of the Emilia Protocol and Shellward 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
Emilia Protocol
Security · Local stdio
Quality: 71/100 (Great) | Auth: No auth required
Shellward
Security · Local stdio
Quality: 56/100 (Good) | Auth: No auth required
Verdict Summary: Choose Emilia Protocol if you need specialized Security tools running via a local process. Choose Shellward 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 Emilia Protocol when:
You need dedicated capabilities in the Security domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You need dedicated capabilities in the Security domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: SHELLWARD_MODE, SHELLWARD_LOCALE, SHELLWARD_THRESHOLD, SHELLWARD_BASELINE_PATH.
Primary tools included: Stdio MCP server with local execution, Prompt injection detection for Chinese and English text, PII, credential, and sensitive-data scanning.
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.
AI Agent Security Middleware & MCP Server with 8-layer defense including prompt injection detection, DLP data flow tracking, command blocking, and PII detection. 7 MCP tools, zero dependencies.
Category & Scope
Tools & Capabilities Breakdown
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.
Shellward Tools (6)
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).
Emilia Protocol is categorized under Security and uses a local stdio subprocess. In contrast, Shellward belongs to Security using local stdio subprocess. Select Emilia Protocol when you need capabilities focused on security and Shellward when you require tools for security.