Emilia Protocol vs SecureNow
A side-by-side look at the Emilia Protocol and SecureNow 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 SecureNow for security over a hosted endpoint. 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 SecureNow when
- You need dedicated capabilities in the Security domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
SECURENOW_APPID, SECURENOW_INSTANCE, SECURENOW_LOGGING_ENABLED, SECURENOW_NO_UUID, OTEL_LOG_LEVEL, SECURENOW_DISABLE_INSTRUMENTATIONS, OTEL_EXPORTER_OTLP_HEADERS, SECURENOW_CAPTURE_BODY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 71/100 · Great | 54/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | SECURENOW_APPIDSECURENOW_INSTANCESECURENOW_LOGGING_ENABLEDSECURENOW_NO_UUIDOTEL_LOG_LEVELSECURENOW_DISABLE_INSTRUMENTATIONSOTEL_EXPORTER_OTLP_HEADERSSECURENOW_CAPTURE_BODY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 598 | 0 |
| Directory activity | 6 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 3 | Not listed |
| Full listing | View Emilia Protocol | View SecureNow |
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.
SecureNow tools
No tool names declared yet. Check the project README from 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"
]
}
}
}
SecureNow
{
"mcpServers": {
"securenow": {
"command": "npx",
"args": [
"-y",
"securenow"
],
"env": {
"SECURENOW_APPID": "YOUR_SECURENOW_APPID_HERE",
"SECURENOW_INSTANCE": "YOUR_SECURENOW_INSTANCE_HERE",
"SECURENOW_LOGGING_ENABLED": "YOUR_SECURENOW_LOGGING_ENABLED_HERE",
"SECURENOW_NO_UUID": "YOUR_SECURENOW_NO_UUID_HERE",
"OTEL_LOG_LEVEL": "YOUR_OTEL_LOG_LEVEL_HERE",
"SECURENOW_DISABLE_INSTRUMENTATIONS": "YOUR_SECURENOW_DISABLE_INSTRUMENTATIONS_HERE",
"OTEL_EXPORTER_OTLP_HEADERS": "YOUR_OTEL_EXPORTER_OTLP_HEADERS_HERE",
"SECURENOW_CAPTURE_BODY": "YOUR_SECURENOW_CAPTURE_BODY_HERE"
}
}
}
}
Frequently asked questions
Emilia Protocol is categorized under Security and uses a local stdio subprocess. SecureNow belongs to Security and uses a remote HTTP/SSE transport. Pick Emilia Protocol for security work and SecureNow 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. SecureNow has no declared pricing — check the project's own site. 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 securenow 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 598 GitHub stars. SecureNow has 54/100 (Good) with 0 views, 0 installs and 0 GitHub stars.