Emilia Protocol vs Pentagonal
A side-by-side look at the Emilia Protocol and Pentagonal 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 Pentagonal 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 Pentagonal 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:
PENTAGONAL_KEY. - You want tools like
pentagonal_generate, pentagonal_lookup, pentagonal_audit.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 71/100 · Great | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | API key required |
| Pricing | Free | Freemium |
| Required env vars | None listed | PENTAGONAL_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 611 | 1 |
| Directory activity | 6 views 0 installs 0 upvotes | 6 views 0 installs 0 upvotes |
| Tools | 3 | 7 |
| Full listing | View Emilia Protocol | View Pentagonal |
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.
Pentagonal tools 7
pentagonal_generateGenerate a production-quality smart contract from a natural language description. Supports EVM (Solidity) and Solana (Anchor/Rust or SPL Token config). The generator uses Pentagonal's self-learning security rules to produce safer code.pentagonal_lookupLook up any token or smart contract by address. Returns the full intelligence report: price, market cap, ATH, 24h volume, transactions, holders, liquidity, LP lock status, pool count, security flags (honeypot, mintable, pausable, hidden owner, taxes), social links, and source code if verified. Use this before auditing to understand the full token landscape. Supports EVM and Solana tokens. Chain is auto-detected if omitted.pentagonal_auditRun an 8-agent security pen test on a smart contract. Each agent specializes in a different attack vector: reentrancy, flash loans, access control, gas griefing, oracle manipulation, front-running, integer overflow, and economic exploits. Findings are returned with severity ratings and line numbers. New security rules are automatically learned from each audit.pentagonal_fixFix a specific vulnerability in a smart contract. Provide the contract code and the finding details — returns the complete fixed contract preserving all existing functionality.pentagonal_compileCompile Solidity source code and return the ABI, bytecode, constructor arguments, and gas estimates. Use this after generating and auditing a contract to prepare it for deployment.pentagonal_rulesGet the current self-learning security rules. These rules are accumulated from every audit Pentagonal performs — the more contracts audited, the smarter the system gets.pentagonal_chainsList all supported blockchains with their chain IDs, explorer URLs, and deployment hints.
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"
]
}
}
}
Pentagonal
{
"mcpServers": {
"pentagonal-ai-pentagonal": {
"command": "npx",
"args": [
"-y",
"pentagonal-mcp"
],
"env": {
"PENTAGONAL_KEY": "YOUR_PENTAGONAL_KEY_HERE"
}
}
}
}
Frequently asked questions
Emilia Protocol is categorized under Security and uses a local stdio subprocess. Pentagonal belongs to Security and uses a local stdio subprocess. Pick Emilia Protocol for security work and Pentagonal 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. Pentagonal is listed as freemium — a free tier with paid plans. 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 pentagonal-ai-pentagonal 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. Pentagonal has 61/100 (Good) with 6 views, 0 installs and 1 GitHub stars.