Shield Kya vs Emilia Protocol
A side-by-side look at the Shield Kya and Emilia Protocol MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Shield Kya 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?
Choose Shield Kya when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
KYA_API_KEY, KYA_OFFLINE, KYA_DIFF_PREVIEW, KYA_GATE. - You want tools like
kya.policy_evaluate, kya.session_ingest, kya.request_approval.
Choose 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 55/100 · Good | 71/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | KYA_API_KEYKYA_OFFLINEKYA_DIFF_PREVIEWKYA_GATE | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 599 |
| Directory activity | 0 views 0 installs 0 upvotes | 6 views 0 installs 0 upvotes |
| Tools | 3 | 3 |
| Full listing | View Shield Kya | View Emilia Protocol |
Tools & capabilities
Shield Kya tools 3
kya.policy_evaluateALLOW` \kya.session_ingestObserve / raise-only riskkya.request_approvalOpen a human Hold. Does not execute the side effect
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.
Shield Kya
{
"mcpServers": {
"shield-kya": {
"command": "npx",
"args": [
"-y",
"@shield-agent/kya@latest"
],
"env": {
"KYA_API_KEY": "YOUR_KYA_API_KEY_HERE",
"KYA_OFFLINE": "YOUR_KYA_OFFLINE_HERE",
"KYA_DIFF_PREVIEW": "YOUR_KYA_DIFF_PREVIEW_HERE",
"KYA_GATE": "YOUR_KYA_GATE_HERE"
}
}
}
}
Emilia Protocol
{
"mcpServers": {
"emiliaprotocol-emilia-protocol": {
"command": "npx",
"args": [
"-y",
"@emilia-protocol/mcp-server"
]
}
}
}
Frequently asked questions
Shield Kya is categorized under Security and uses a local stdio subprocess. Emilia Protocol belongs to Security and uses a local stdio subprocess. Pick Shield Kya 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.
Shield Kya 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 shield-kya and emiliaprotocol-emilia-protocol as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Shield Kya has a quality signal of 55/100 (Good) with 0 views, 0 installs and 1 GitHub stars. Emilia Protocol has 71/100 (Great) with 6 views, 0 installs and 599 GitHub stars.