AEO Lookup MCP server

• Registry namecom.aeolookup/free-aeo-toolsverified in the MCP registry

The registry name sits under aeolookup.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-30
• Tools6
• Server calls itselfaeolookup
• Server version1.0.0
• Protocol version2025-06-18

On 2026-10-30 the server answered initialize and tools/list without a sign-in. First answer in 249 ms.

• Its tools do check whether AI crawlers can reach a website; validate structured data that identifies an organisation, but not compare AI office assistants for a small UK firm.
• Checked on 3 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
• What an agent can do with it2 of 3 use cases
• Answeredmeasuring3 of the 7 daily checks it takes to print a share
• Median first answer352 ms
• Space in an agent's context≈ 2,692 tokensthe definitions of all its tools (11), which an agent carries on every turn
• Tool definitionsA · 100 of 100
• Typed results0 of 11 toolsdeclared outputSchema: results come typed, read once

• Every tool passes all six checks.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• check_ai_crawler_access

  Checks whether the crawlers behind ChatGPT, Claude, Perplexity, Google AI Overviews, Copilot and 14 more may read a page: robots.txt rules (RFC 9309), robots meta and X-Robots-Tag directives, and whether the site's firewall refuses each…

• check_structured_data

  Extracts every JSON-LD block on a page, lists the schema.org types it describes, flags missing required and recommended properties (Organization, LocalBusiness, Article, FAQPage, Product, Service, Person, BreadcrumbList, Event) and scores…

• validate_llms_txt

  Fetches /llms.txt (or the llms.txt address given), validates it against the llmstxt.org proposal (one H1, optional summary, H2 sections of [name](url): notes links), tests up to eight of its links and reports whether llms-full.txt exists…

• generate_llms_txt

  Drafts an llms.txt for a site: the name and summary from its home page, then its pages from the sitemap grouped by section, with titles and descriptions read from up to 24 pages. Returns the file as text, for a person to edit before…

• score_answer_readiness

  Scores a page out of 100 on 14 published checks: indexable, title and description, one H1, question headings, direct first-sentence answers, structured data, dates, a named author, lists and tables, source links, specific figures, length…

• run_aeo_audit

  Runs all four checks on one address (AI crawler access, structured data, llms.txt, answer readiness) and returns each result plus an overall score: the mean of the crawler, schema and answer-readiness scores. llms.txt is reported but not…