AI Visibility Checker runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 28 Aug 2026.
AI visibility checker: GPTBot vs OAI-SearchBot, robots.txt audit, raw-HTML schema. 165 crawlers.
We read the source, 2 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
return json.load(open(os.path.join(HERE, p)))
if(!txt){out.innerHTML=fi("warn","Nothing pasted yet","Open <code>yourstore.com/robots.txt</code> and paste the whole file.");return}
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
AI-search-visibility tools: check crawler access, generate llms.txt, lint robots.txt, census data.
ESLint for AI search: audits AI-crawler access, llms.txt, schema and citability.
AEO audit: score any website 0-100 for AI visibility. Checks schema, meta, content, AI crawlers.
robots.txt tester (RFC 9309), AI crawler access (GPTBot, ClaudeBot...) and sitemap check.
Free MCP tools for AI-search visibility: crawler checks, page audits, and llms.txt generation.
Checks llms.txt, AI crawler access in robots.txt, and sitemap - with a 0-100 AI readiness score.
One-call audit: robots.txt AI-bot rules, llms.txt, JSON-LD, meta tags, sitemap. Score plus fixes.
Live AEO, GEO, JSON-LD Schema, robots.txt AI crawler, and Agent Readiness diagnostic auditor.
Answers built from our own checks of this server.