Emilia Protocol vs Vorim MCP Server
A side-by-side look at the Emilia Protocol and Vorim MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Emilia Protocol for security work as a local process; choose Vorim MCP Server 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 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.
Choose Vorim MCP Server when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
VORIM_API_KEY, VORIM_BASE_URL. - You want tools like
vorim_ping, vorim_register_agent, vorim_register_ephemeral.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 71/100 · Great | 47/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | API key required |
| Pricing | Free | Free |
| Required env vars | None listed | VORIM_API_KEYVORIM_BASE_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 611 | 54 |
| Directory activity | 6 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 3 | 19 |
| Full listing | View Emilia Protocol | View Vorim MCP Server |
Tools & capabilities
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.
Vorim MCP Server tools 19
vorim_pingCheck API health and connectivityvorim_register_agentRegister a new agent with Ed25519 cryptographic identityvorim_register_ephemeralRegister a `did:key` ephemeral agent with TTLvorim_get_agentGet agent details by IDvorim_list_agentsList all agents with pagination and filteringvorim_update_agentUpdate agent metadata (name, description, status)vorim_revoke_agentPermanently revoke an agentvorim_check_permissionCheck if agent has a permission scope (sub-5ms)vorim_grant_permissionGrant a permission with optional expiry and rate limitsvorim_list_permissionsList all active permissions for an agentvorim_revoke_permissionRevoke a specific permission scopevorim_delegate_credentialDelegate OAuth credentials to an agent- +7 more on the listing page
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.
Emilia Protocol
{
"mcpServers": {
"emiliaprotocol-emilia-protocol": {
"command": "npx",
"args": [
"-y",
"@emilia-protocol/mcp-server"
]
}
}
}
Vorim MCP Server
{
"mcpServers": {
"kzino-vorim-mcp-server": {
"command": "npx",
"args": [
"-y",
"@vorim/mcp-server"
],
"env": {
"VORIM_API_KEY": "YOUR_VORIM_API_KEY_HERE",
"VORIM_BASE_URL": "YOUR_VORIM_BASE_URL_HERE"
}
}
}
}
Frequently asked questions
Emilia Protocol is categorized under Security and uses a local stdio subprocess. Vorim MCP Server belongs to Security and uses a local stdio subprocess. Pick Emilia Protocol for security work and Vorim MCP Server 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.
Emilia Protocol is listed as free. Auth: no auth required. Vorim MCP Server is listed as free. Auth: api key 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 emiliaprotocol-emilia-protocol and kzino-vorim-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Emilia Protocol has a quality signal of 71/100 (Great) with 6 views, 0 installs and 611 GitHub stars. Vorim MCP Server has 47/100 (Fair) with 2 views, 0 installs and 54 GitHub stars.