Aeo MCP vs Emilia Protocol — MCP Server Comparison | AllMCPs
Aeo MCP vs Emilia Protocol
A side-by-side look at the Aeo MCP 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 Aeo MCP 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 Aeo MCP when
You need dedicated capabilities in the Security domain.
You prefer a local stdio subprocess transport.
You want tools like audit_url, check_ai_crawlers, inspect_llms_txt.
audit_urlRun a full AI-readiness (AEO) audit of a website: 29 checks across AI crawler access, structured data, content extractability, and answerability, returning a 0-100 score with prioritized fixes. Use when asked how visible a site is to ChatGPT, Perplexity, Gemini, or Claude, or for an overall AEO/AI-SEO health check.
check_ai_crawlersCheck whether AI crawlers like GPTBot, ClaudeBot, PerplexityBot, Google-Extended, CCBot, and Bingbot are allowed to read a website, based on its robots.txt. Use when asked about AI visibility, AEO, crawler permissions, or why a site does not appear in ChatGPT or Perplexity.
inspect_llms_txtFetch and validate a website's llms.txt file (the Markdown file that tells AI engines what the site is about and which pages matter). Returns its title, summary, sections, links, and any structural issues. Use when asked whether a site has llms.txt or how to improve it.
extract_structured_dataExtract and summarize a page's JSON-LD structured data (schema.org): which types exist (Product, Article, FAQPage, Organization), their key fields, and any parse errors. Use when asked whether a page has the schema markup AI answer engines rely on for citations.
extract_page_signalsExtract the on-page signals AI engines parse: title, meta description, h1, canonical, lang, text-to-HTML ratio, heading outline, and whether the page looks client-side rendered (invisible to most AI crawlers). Use to diagnose why engines misread or skip a 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.
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.
Aeo MCP is categorized under Security and uses a local stdio subprocess. Emilia Protocol belongs to Security and uses a local stdio subprocess. Pick Aeo MCP 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.
Aeo MCP 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 aeo-mcp and emiliaprotocol-emilia-protocol as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Aeo MCP has a quality signal of 53/100 (Good) with 2 views, 0 installs and 0 GitHub stars. Emilia Protocol has 71/100 (Great) with 5 views, 0 installs and 612 GitHub stars.
Poll 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.