Aeo MCP vs AI Distiller MCP
A side-by-side look at the Aeo MCP and AI Distiller MCP 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 AI Distiller MCP 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.
Choose AI Distiller MCP 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
distill_file, distill_directory, distill_with_dependencies.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 53/100 · Good | 65/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
Tools & capabilities
Aeo MCP tools 5
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.
AI Distiller MCP tools 16
distill_fileExtracts essential code structure from a single file - the core functionality of AI Distiller. Returns clean, structured code signatures optimized for AI context windows. USAGE: Essential for providing accurate code context to AI assistants. Automatically detects language and extracts API signatures, types, and structure while removing unnecessary implementation details.distill_directoryExtracts essential code structure from entire directories - the core functionality of AI Distiller. Processes all supported programming languages and returns structured API/code signatures optimized for AI context windows. USAGE: Perfect for understanding codebases, API discovery, and providing accurate code context to AI assistants. Supports filtering by visibility levels, file patterns, and content types.
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
{
"mcpServers": {
"aeo-mcp": {
"command": "npx",
"args": [
"-y",
"aeo-mcp"
]
}
}
}
AI Distiller MCP
{
"mcpServers": {
"janreges-ai-distiller-mcp": {
"command": "npx",
"args": [
"-y",
"@janreges/ai-distiller-mcp"
]
}
}
}
Frequently asked questions
Aeo MCP is categorized under Security and uses a local stdio subprocess. AI Distiller MCP belongs to Security and uses a local stdio subprocess. Pick Aeo MCP for security work and AI Distiller MCP 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. AI Distiller MCP 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 janreges-ai-distiller-mcp 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. AI Distiller MCP has 65/100 (Great) with 4 views, 0 installs and 172 GitHub stars.