Bright Security vs Emilia Protocol
A side-by-side look at the Bright Security and Emilia Protocol MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
B
Bright SecuritySecurityEnables AI agents to access Bright Security tools for app discovery and security testing.37FairAuth: not declaredVerdict: choose Bright Security for security work; 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?
BChoose Bright Security when
- You need dedicated capabilities in the Security domain.
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 | B Bright Security | |
|---|---|---|
| Category | Security | Security |
| Quality signal | 37/100 · Fair | 71/100 · Great |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 599 |
| Directory activity | 1 views 0 installs 0 upvotes | 6 views 0 installs 0 upvotes |
| Tools | Not listed | 3 |
| Full listing | View Bright Security | View Emilia Protocol |
Tools & capabilities
Bright Security tools
No tool names declared yet. Check the project README from the listing page.
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.
Bright Security
No confirmed install command for Bright Security yet — follow the setup steps linked from its listing page rather than a guessed package name.
Emilia Protocol
{
"mcpServers": {
"emiliaprotocol-emilia-protocol": {
"command": "npx",
"args": [
"-y",
"@emilia-protocol/mcp-server"
]
}
}
}
Frequently asked questions
Bright Security is categorized under Security and uses an install path we have not confirmed yet. Emilia Protocol belongs to Security and uses a local stdio subprocess. Pick Bright Security 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. Bright Security has no confirmed install command yet — follow its own setup instructions.
Bright Security 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 bright-security and emiliaprotocol-emilia-protocol as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Bright Security has a quality signal of 37/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Emilia Protocol has 71/100 (Great) with 6 views, 0 installs and 599 GitHub stars.