Google Search Console integration for Model Context Protocol (MCP)
AEO Lookup is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Free AI crawler, schema, llms.txt and answer-readiness checks for public web pages. No API key.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http aeo-lookup-mcp https://aeolookup.com/mcp
# 2 — ask your agent for something these tools do
# check_ai_crawler_access, check_structured_data, validate_llms_txt and 8 more
AEO Lookup costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http aeo-lookup-mcp https://aeolookup.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
11 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 crawler's user agent. Separates search and user crawlers (which decide whether you can be cited) from training crawlers (which do not). Free, no key. Docs: https:/
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The page or site to check, for example https://example.co.uk/ (https:// is added if missing). |
| path | string | no | Optional path to test instead of the URL's own path, for example /blog/. |
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 entity signals: a named organisation, sameAs links to other profiles, a logo and an @id. Free, no key. Docs: https://aeolookup.com/aeo-tools/schema-checker/
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The page or site to check, for example https://example.co.uk/ (https:// is added if missing). |
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. States the evidence on how little the file is read. Free, no key. Docs: https://aeolookup.com/aeo-tools/llms-txt-validator/
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The page or site to check, for example https://example.co.uk/ (https:// is added if missing). |
| check_links | boolean | no | Test up to eight of the file's links that are on its own site (default true). |
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 publishing. Free, no key. Docs: https://aeolookup.com/aeo-tools/llms-txt-validator/
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The page or site to check, for example https://example.co.uk/ (https:// is added if missing). |
| max_links | integer | no | Roughly how many links to include (default 40). |
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, declared language and stock AI phrasing. Returns each check's points, what it found and the fix, ordered by points available. Free, no key. Docs: https://aeolook
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The page or site to check, for example https://example.co.uk/ (https:// is added if missing). |
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 scored, because the evidence says few systems read it. Free, no key. Docs: https://aeolookup.com/aeo-tools/api/
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The page or site to check, for example https://example.co.uk/ (https:// is added if missing). |
Estimates how much a UK business could save a year by handing admin to AI: a range in pounds from team size, weekly admin hours per person, hourly pay (default the ONS 2025 UK median) and sector exposure (Department for Education ranking), with two or three insights. Partial by design: the free AI audit gives the full breakdown. Free, no key. Docs: https://aeolookup.com/ai-calculators/ai-savings-c
| Parameter | Type | Required | Notes |
|---|---|---|---|
| industry | string | no | The business sector (default other). |
| staff | integer | yes | Number of staff. |
| admin_hours | number | no | Hours of admin each person does a week (default 10). |
| hourly_pay | number | no | Average hourly pay in pounds (default 19.67, the UK median). |
Estimates the hours a week AI could save one person or a team, from the hours spent on seven everyday task types (email, scheduling, quotes and invoices, data entry, customer questions, documents, marketing), using a share per task informed by IPPR and McKinsey research. Returns a range and the task with the biggest saving. Free, no key. Docs: https://aeolookup.com/ai-calculators/ai-time-saved-cal
| Parameter | Type | Required | Notes |
|---|---|---|---|
| number | no | Hours a week one person spends on email and messages (default 0). | |
| scheduling | number | no | Hours a week one person spends on scheduling, bookings and reminders (default 0). |
| quotes | number | no | Hours a week one person spends on quotes, invoices and chasing payments (default 0). |
| data | number | no | Hours a week one person spends on data entry, admin and updating records (default 0). |
| customers | number | no | Hours a week one person spends on answering customer questions (phone, chat, email) (default 0). |
| documents | number | no | Hours a week one person spends on reports, proposals and documents (default 0). |
| marketing | number | no | Hours a week one person spends on social posts, newsletters and marketing copy (default 0). |
| people | integer | no | How many people spend their week like this (default 1). |
Estimates how much of a team's work AI could take on today, as full-time roles' worth of tasks, from headcount in seven role groups, ordered by the Department for Education's exposure ranking. Measures tasks, not people. Free, no key. Docs: https://aeolookup.com/ai-calculators/will-ai-replace-my-staff/
| Parameter | Type | Required | Notes |
|---|---|---|---|
| admin | integer | no | How many people work as admin, reception and office support (default 0). |
| customer | integer | no | How many people work as customer service and phone sales (default 0). |
| finance | integer | no | How many people work as bookkeeping, payroll and finance admin (default 0). |
| marketing | integer | no | How many people work as marketing and content (default 0). |
| professional | integer | no | How many people work as professionals (accountants, solicitors, consultants, analysts) (default 0). |
| managers | integer | no | How many people work as managers and directors (default 0). |
| handson | integer | no | How many people work as hands-on staff (trades, care, kitchen, warehouse, drivers) (default 0). |
Rates a UK occupation's exposure to AI (high, medium or low, following the Department for Education's 2023 ranking), the share of its tasks AI can do today and the tasks it reaches first. Free, no key. Docs: https://aeolookup.com/ai-calculators/is-my-job-at-risk-from-ai/
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job | string | yes | The occupation. |
Scores how ready a small business is to put AI tools to work, out of 100, from eight yes or no questions (digital records, one customer system, written processes, known repetitive tasks, current AI use, an owner, a clear website, time to bed in), and names the two biggest gaps. Free, no key. Docs: https://aeolookup.com/ai-calculators/ai-readiness-score/
| Parameter | Type | Required | Notes |
|---|---|---|---|
| digital | boolean | no | Most of your business records are in software, not on paper or in heads (15 points). |
| onePlace | boolean | no | Customer details live in one system (a CRM, booking or accounts tool), not scattered across inboxes (15 points). |
| processes | boolean | no | Your routine jobs (quoting, booking, onboarding, invoicing) follow written steps (15 points). |
| repetitive | boolean | no | You can name the three most repetitive tasks in your week (10 points). |
| using | boolean | no | Someone on the team already uses an AI assistant such as ChatGPT or Copilot every week (10 points). |
| owner | boolean | no | One person is responsible for trying AI in the business (10 points). |
| website | boolean | no | Your website answers customers' common questions clearly, so AI assistants can find and quote you (10 points). |
| time | boolean | no | You could give a new tool two or three hours a week for a month to bed in (15 points). |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install AEO Lookup or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| check_ai_crawler_access | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| check_structured_data | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| validate_llms_txt | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| generate_llms_txt | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| score_answer_readiness | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| run_aeo_audit | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| calculate_ai_savings | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| calculate_ai_time_saved | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| estimate_ai_staff_impact | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| check_job_ai_risk | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| score_ai_readiness | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish AEO Lookup can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.