OpenAEO
NPM · OPENAEO-AUDIT · SCANNED SEP 24
Asks 8 AI crawlers for your page, checks who really answered, and writes the fixes. MIT.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 40 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2195 tokens (~146/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the OpenAEO MCP server?
OpenAEO runs locally as an npm package, launched with npx -y openaeo-audit. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · openaeo-audit
claude mcp add dev-openaeo-audit -- npx -y openaeo-audit
{
"mcpServers": {
"dev-openaeo-audit": {
"command": "npx",
"args": [
"-y",
"openaeo-audit"
]
}
}
} {
"servers": {
"dev-openaeo-audit": {
"command": "npx",
"args": [
"-y",
"openaeo-audit"
]
}
}
} codex mcp add dev-openaeo-audit -- npx -y openaeo-audit
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-openaeo-audit": {
"type": "local",
"command": [
"npx",
"-y",
"openaeo-audit"
],
"enabled": true
}
}
} openclaw mcp add dev-openaeo-audit --command npx --arg -y --arg openaeo-audit
mcp_servers:
dev-openaeo-audit:
command: "npx"
args: ["-y", "openaeo-audit"] {
"McpServers": {
"dev-openaeo-audit": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"openaeo-audit"
]
}
}
} assistant mcp add dev-openaeo-audit -t stdio -c npx -a -y openaeo-audit
{
"mcpServers": {
"dev-openaeo-audit": {
"command": "npx",
"args": [
"-y",
"openaeo-audit"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 −3
- Stability: pass → 0.80 functional
- 21 Sept 26 0
- Stability: 0.97 → pass security
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 0
- Package version: 1.6.0 → 1.6.4 functional
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −2
- Stability: pass → 0.83 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Analysed npm/openaeo-audit@1.6.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
aeo_alerts ~87
What changed on this site since the last check: a crawler that could reach it last week and cannot now, a check that was passing and is not, citations lost or gained. A crawler going dark usually means nobody touched the site and a CDN moved a default underneath it, which is the one problem an owner cannot notice on their own. Worth calling on a schedule rather than once.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
aeo_audit ~97
Audit a live website for AI-search visibility (AEO/GEO). Fetches the page as an AI crawler would and returns a 0-100 score, a band, every passing/failing check, and prioritised fixes. Use this first to find out why a site isn't being cited by ChatGPT, Claude, Gemini or Perplexity.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain or full URL, e.g. example.com |
No output schema declared.
No examples provided.
aeo_authenticity ~153
How much of the AI crawler traffic a site thinks it is getting is actually real, and how that compares to every other site we have read a log for. Every owner assumes their answer is 100%. The comparison is the part no local tool can produce: it needs other people's logs. Call with no arguments to read the current median, or pass a rate from aeo_read_log to add your own reading and get back where you stand.
| Name | Type | Req | Description |
|---|---|---|---|
| claimed | number | – | Optional: how many requests that rate was computed over |
| domain | string | – | The site the reading is for |
| rate | number | – | Optional: the authenticity rate from aeo_read_log, 0 to 100 |
No output schema declared.
No examples provided.
aeo_check_html ~73
Score a page's HTML against the checks a single file can satisfy (title, meta description, Organization/WebSite/FAQPage JSON-LD, a number in the first 100 words) without making changes. Use to verify your edits worked.
| Name | Type | Req | Description |
|---|---|---|---|
| html | string | yes | The full HTML source of the page |
No output schema declared.
No examples provided.
aeo_citations ~92
Run a citation test: ask the assistants a buyer question and record whether this business is named. Runs on openaeo.dev because it needs provider keys for six surfaces. Needs OPENAEO_API_KEY (Solo and above).
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain to look for in the answers |
| query | string | yes | The buyer question to ask, e.g. 'best film presets for portraits' |
No output schema declared.
No examples provided.
aeo_competitors ~42
Competitor share of voice: which domains the assistants name instead of you, across your tracked prompts. Needs OPENAEO_API_KEY (Business and above).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
aeo_crawler_intel ~118
Has this site's CDN started refusing AI crawlers? Reads OpenAEO's corpus of per-crawler reachability observations to show what each crawler is served today, what changed since the last observation, and how often each has been blocked. Answers what robots.txt cannot: a CDN can refuse ClaudeBot while robots.txt allows it, and a provider changing a default is invisible to the site owner. Needs OPENAEO_API_KEY (Solo and above).
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain to look up, e.g. example.com |
No output schema declared.
No examples provided.
aeo_drift ~79
What regressed. Lists checks that were passing and are not any more, and crawlers that were reachable and are not any more, so a deploy that broke AI visibility is caught before anyone notices the traffic. Needs OPENAEO_API_KEY (Solo and above).
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | Domain to check, defaults to your tracked site |
No output schema declared.
No examples provided.
aeo_fix_files ~100
Generate the paste-ready files a site needs to be readable and citable by AI assistants: robots.txt (allowing the AI crawlers), llms.txt (a quotable index), Organization+WebSite JSON-LD, and a template opening paragraph. Write these into the user's project.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | – | Business/brand name (optional; defaults from the domain) |
| domain | string | yes | Domain, e.g. example.com |
No output schema declared.
No examples provided.
aeo_fix_html ~126
Take a page's HTML and return it with the missing structural pieces injected into <head>: <title>, <meta name=description>, and Organization+WebSite JSON-LD. Only ADDS what's absent, never rewrites or deletes existing content. Returns the fixed HTML plus a before/after readiness score. Use this on a local file, then write the result back.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | – | Business/brand name (optional) |
| domain | string | – | Domain, e.g. example.com |
| html | string | yes | The full HTML source of the page |
No output schema declared.
No examples provided.
aeo_fix_my_site ~146
ONE-SHOT for people who don't have a codebase. Give it a domain and it audits the site, detects the platform (Squarespace, Wix, Webflow, WordPress, Shopify, Framer, Ghost, Carrd or custom), generates the exact files/snippets, and returns click-by-click instructions for where to paste each one in THAT platform's admin, including an honest note when a platform can't do something. Use this whenever the user isn't a developer or their site is on a website builder.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | – | Business name (optional; defaults from the domain) |
| domain | string | yes | Domain or full URL, e.g. example.com |
No output schema declared.
No examples provided.
aeo_history ~42
Score history for a tracked site: how the AEO score has moved over time, and which checks changed. Needs OPENAEO_API_KEY (Solo and above).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
aeo_packet ~123
Generate an engineering packet for a domain (the open-source version): an ordered list of tickets, each with the audit evidence that justifies it, where the change goes for that stack, implementation steps, acceptance criteria, and an `agentPrompt` you can execute directly. Use this when the user wants you to actually FIX their site rather than just audit it, work the tickets in order, P1 first, showing the user each change before you make it.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | – | Business name (optional) |
| domain | string | yes | Domain or full URL |
No output schema declared.
No examples provided.
aeo_read_log ~250
Read a server access log and report what AI crawlers actually got: which arrived, what status they were given, which paths they reached, and whether each request really came from the operator it claimed. Understands the combined format nginx and Apache write by default, and JSON lines from Cloudflare, Fastly, Vercel and Netlify. This is the tool that settles what an audit can only indicate: a fetch sent from this machine wearing a crawler's name is an indication, and the log is the evidence. Where the two disagree, the log is right. Runs entirely locally. The log is parsed in this process and never sent anywhere; the only network call is fetching the operators' public address ranges.
| Name | Type | Req | Description |
|---|---|---|---|
| bots | array | – | Optional: the bots array from a previous aeo_audit call, to reconcile what we measured against what actually happened. |
| domain | string | – | Optional: the site this log belongs to. With an API key this adds your authenticity rate to the corpus and returns how you compare. Only the rate and the request count are sent; the log is not. |
| log | string | yes | The access log text. Paste it or read the file first. |
No output schema declared.
No examples provided.
aeo_verify_crawler ~139
Check whether an IP address really belongs to the crawler it claims to be, against the ranges the operator publishes. OpenAI, Anthropic, Google, Microsoft, Perplexity and Apple all publish these. Answers verified, impostor, or unverifiable, and never says impostor without positive evidence: if the operator publishes nothing, or the feed fails to load, the answer is unverifiable. Use when a log line looks suspicious or before allow-listing anything by name.
| Name | Type | Req | Description |
|---|---|---|---|
| bot | string | yes | The crawler it claims to be, e.g. GPTBot |
| ip | string | yes | The client IP address from your log |
No output schema declared.
No examples provided.
What is the OpenAEO MCP server?
OpenAEO is an MCP server listed in the public MCP registry as dev.openaeo/audit. Asks 8 AI crawlers for your page, checks who really answered, and writes the fixes. MIT. This page covers its npm package (openaeo-audit).
Is the OpenAEO MCP server safe to use?
OpenAEO scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the OpenAEO MCP server expose?
OpenAEO exposes 15 tools: aeo_audit, aeo_fix_files, aeo_fix_html, aeo_fix_my_site, aeo_packet, and 10 more. Their descriptions and schemas cost roughly 1,667 tokens of context every time the server is loaded.
Is the OpenAEO MCP server still maintained?
OpenAEO is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the OpenAEO MCP server under?
OpenAEO declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.