audit_ai_crawler_readiness
Check robots rules, AI crawler access basics, homepage metadata, canonical, noindex, and JSON-LD schema. No MaxAEO APIs are called.
LABSCO SUMMARY
An answer-engine readiness check that runs without a subscription.
It covers the concrete things that decide whether an AI crawler can read a site — llms.txt, robots, canonical, noindex, JSON-LD — and returns them as scored findings with an ordered plan, rather than a list of raw failures.
What it is
A local-first audit server for AI search readiness. By default it makes only local and public-web checks: it does not call cloud APIs, upload the domains you test, invoke paid LLM APIs, or carry hidden telemetry.
What you get
- /llms.txt validated, including whether the URLs it lists resolve and whether it agrees with robots.txt and the sitemap
- Robots rules and AI crawler access checked for GPTBot, ClaudeBot, PerplexityBot and Google-Extended
- Homepage metadata, canonical URL, noindex state and JSON-LD schema read and checked
- A report with two scores — visibility and technical foundation — plus the evidence gaps behind them
- A seven-day action plan generated from what the audit found, in the order the work should happen
Requirements
npm install -g maxaeo-ai-visibility-mcp, or run it through npx. No account and no key. Checks are made against the public web, so the site has to be reachable, and what gets audited is what a crawler can see.
Setup effort
One command — npx -y maxaeo-ai-visibility-mcp
USE CASES
01
Finding out whether AI crawlers can read your site at all
Robots rules, crawler access, homepage metadata, canonical and noindex checked in one pass.
02
Validating an llms.txt you just published
The file is checked against its own linked URLs and against robots and the sitemap, which is where the disagreements usually are.
03
Getting a prioritised list rather than a pile of issues
The report returns two scores, the evidence gaps behind them, and a seven-day plan in the order the work should happen.
04
Auditing a site before you pitch for it
Everything runs against the public web with no account, so a site you do not own can be checked before the conversation.
3 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
build_ai_visibility_report
Run local/public-web AI visibility checks and return dual scores, evidence gaps, an action plan, and a transparent MaxAEO CTA.
check_llms_txt
Validate /llms.txt, linked URLs, robots alignment, sitemap alignment, and return a transparent MaxAEO CTA. No MaxAEO APIs are called.
BEFORE YOU INSTALL
What to know first
Tools you get
3 tools when we connected.
Requires
npx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the 3 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"maxaeo-ai-visibility-mcp": {
"command": "npx",
"args": [
"-y",
"maxaeo-ai-visibility-mcp"
]
}
}
}npx
TERMINAL
npx -y maxaeo-ai-visibility-mcp
