Google Search Console integration for Model Context Protocol (MCP)
OpenAEO 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.
Open InstallationWhat it does
Asks 8 AI crawlers for your page, checks who really answered, and writes the fixes. MIT.
Quickstart
# 1 — run it from where its publisher ships it
npx -y openaeo-audit
# 2 — ask your agent something
> Asks 8 AI crawlers for your page, checks who really answered, and writes the fixes. MIT.
OpenAEO is free: there is no plan to choose, no cap to set and nothing that can bill you.
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. This one runs on your machine: your client starts OpenAEO as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It is scanned, signed and pinned to the version you choose — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add openaeo-mcp -- npx -y openaeo-auditReconnect, or start a new session, and the tools appear in the model’s tool list.
Nothing is required, but it can take OPENAEO_API_KEY if you want to set them.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
15 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.
Audit a live website for AI-search visibility (AEO/GEO). Fetches the page as an AI crawler
No parameter schema on file.
Generate the paste-ready files a site needs to be readable and citable by AI assistants:
No parameter schema on file.
Take a page
No parameter schema on file.
ONE-SHOT for people who don
No parameter schema on file.
Generate an engineering packet for a domain (the open-source version): an ordered list of tickets, each with the audit
No parameter schema on file.
Score a page
No parameter schema on file.
Read a server access log and report what AI crawlers actually got: which arrived, what status
No parameter schema on file.
Check whether an IP address really belongs to the crawler it claims to be, against the ranges
No parameter schema on file.
How much of the AI crawler traffic a site thinks it is getting is actually real, and how that
No parameter schema on file.
What changed on this site since the last check: a crawler that could reach it last week and
No parameter schema on file.
Has this site
No parameter schema on file.
Run a citation test: ask the assistants a buyer question and record whether this business is
No parameter schema on file.
Score history for a tracked site: how the AEO score has moved over time, and which checks
No parameter schema on file.
What regressed. Lists checks that were passing and are not any more, and crawlers that were
No parameter schema on file.
Competitor share of voice: which domains the assistants name instead of you, across your
No parameter schema on file.
- Every tool, no call limit
- No card, no account needed
- Source published under a licence you can read
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because nothing bills
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable. OpenAEO costs nothing to install and nothing to call, 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 | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
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.
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
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. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
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
Pinned to 1.6.4 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
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.
Writing one takes an account with at least 50 real tool calls against OpenAEO in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
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 an account with 50 real tool calls against it.