Skip to main content
Glama
Sign In
geo-seo-readiness-lite

geo-seo-readiness-lite

by alicexixi85
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

GEO & SEO Readiness MCP — Lite

An open-source Model Context Protocol server that checks whether a public website can be read and cited by AI search engines (ChatGPT Search, Perplexity, Claude) as well as classic search.

Ask your assistant "Is example.com ready for AI search?" and it runs five rule-based checks and returns a prioritized fix list. No API keys, no account, no dependencies beyond Python 3.10+.

Tools

Tool

What it checks

quick_readiness_report

Runs every check below and returns a fix_first list (FAIL before WARN).

check_ai_crawler_access

robots.txt rules for the page path, split into AI search crawlers (OAI-SearchBot, PerplexityBot, Claude-SearchBot), AI training crawlers (GPTBot, ClaudeBot, Google-Extended, CCBot) and Googlebot/Bingbot. Blocking training crawlers is reported as a policy choice, not an error.

check_llms_txt

Whether /llms.txt exists, is Markdown rather than an HTML soft-404, and has a title, sections and links.

extract_structured_data

JSON-LD types (including @graph), invalid JSON-LD, canonical and og:url pointing to another host, missing meta description, and pages whose initial HTML is an almost-empty JavaScript shell.

check_sitemap

Finds the sitemap from robots.txt or /sitemap.xml, detects urlset vs sitemapindex, counts URLs (reads up to 4 MiB, gzip supported).

Every finding is labelled PASS, WARN, FAIL, INFO or UNMEASURED. When a site blocks the request (403/429, timeouts), the check says UNMEASURED instead of guessing.

Related MCP server: AI Readiness

Install

git clone https://github.com/alicexixi85/geo-seo-mcp-pro.git

Claude Desktop (claude_desktop_config.json) / Cursor (~/.cursor/mcp.json):

{
  "mcpServers": {
    "geo-seo-readiness": {
      "command": "python3",
      "args": ["/absolute/path/to/geo-seo-mcp-pro/server.py"]
    }
  }
}

Docker

docker build -t geo-seo-readiness-lite .
docker run -i --rm geo-seo-readiness-lite

One-off check in a terminal

python3 server.py --check https://example.com

Example prompts

  • "Run a quick readiness report for https://example.com and tell me the three fixes that matter most."

  • "Does my robots.txt block OAI-SearchBot or PerplexityBot on /pricing?"

  • "Is my canonical tag pointing somewhere it shouldn't?"

Limits (read before relying on results)

  • Checks the initial HTML response only. It does not execute JavaScript, so JSON-LD injected client-side is not seen (the tool tells you when the page looks like a JavaScript shell).

  • robots.txt is only one layer. A CDN or WAF (for example Cloudflare bot settings) can still block crawlers by user agent; verify those settings separately.

  • Refuses localhost and private network addresses. Public http/https URLs only.

  • Does not produce a single "score". Rankings and citations depend on much more than technical readiness.

Commercial edition

This repository is the free, MIT-licensed Lite server. A separate paid edition (GEO & SEO Readiness MCP Server 2.1) adds headless-Chromium rendering for SPAs, weighted scoring, two-site competitor comparison, candidate robots.txt / llms.txt / JSON-LD patches and a white-label PDF report for agencies. A sample report from that edition is in GEO_SEO_MCP_2_1_Sample_4Page_Audit_Report.pdf; details and pricing are on Gumroad. The Lite server is complete on its own and does not require the paid edition.

License

MIT. Built by @alicexixi85. Issues and pull requests welcome.

Available Tools

5 tools
check_ai_crawler_accessA
Read-only

Evaluate robots.txt for AI search crawlers (OAI-SearchBot, PerplexityBot, Claude-SearchBot), AI training crawlers (GPTBot, ClaudeBot, Google-Extended, CCBot) and Googlebot/Bingbot, for the given page path.

Inputs: url (required).

check_llms_txtA
Read-only

Fetch /llms.txt for the site and check that it is Markdown with a title, sections and links (detects HTML soft-404s).

Inputs: url (required).

check_sitemapA
Read-only

Find the XML sitemap (robots.txt Sitemap: lines or /sitemap.xml) and count its URLs. Reads up to 4 MiB; supports gzip.

Inputs: url (required), sitemap_url.

extract_structured_dataA
Read-only

Extract JSON-LD types, canonical, og:url, title, meta description and initial-HTML text size for a page; flags canonicals pointing to another host.

Inputs: url (required).

quick_readiness_reportA
Read-only

Run all checks (AI crawler access, llms.txt, JSON-LD/canonical, sitemap) for a URL and return a prioritized fix list.

Inputs: url (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 5 tools

    Disambiguation4/5

    The four granular checks target clearly distinct artifacts (robots.txt, /llms.txt, page HTML structured data, XML sitemap), so they are easy to tell apart. quick_readiness_report overlaps in purpose with the other four because it aggregates them, but its description explicitly frames it as an all-in-one check, making the boundary understandable rather than confusing.

    Naming Consistency4/5

    All names use snake_case and four of five follow a clean verb_noun pattern (check_ai_crawler_access, check_llms_txt, extract_structured_data, check_sitemap). quick_readiness_report deviates by using an adjective instead of a verb, but it remains readable and clearly signals its composite role.

    Tool Count5/5

    Five tools is well-scoped for a 'lite' readiness checker: one convenient aggregate plus four focused checks, each earning its place. There is no bloat or thin single-tool surface.

    Completeness4/5

    The surface covers the declared readiness areas fully: AI crawler access, llms.txt, structured data/canonical, and sitemap, plus a prioritized aggregate report. Minor gaps remain, such as page-level meta robots/noindex checking and broader indexability diagnostics, but these are reasonable omissions for a lite tool.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers

    • maxaeo-ai-visibility-mcp

      maxaeo
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to check whether a public website is crawlable, understandable, and ready for AI search workflows through local-only audits of robots.txt, sitemaps, metadata, and llms.txt.
      3
      80 npm
      2
      MIT

    • AI Readiness

      epistemedeus
      A
      license
      A
      quality
      C
      maintenance
      Check whether a website is visible to AI search engines (ChatGPT, Perplexity, Claude, Google AI Overviews). Returns a 0-100 readiness score, a grade, and a specific fix for each gap. Dependency-free, no API keys.
      2
      5 npm
      1
      MIT
    • Agundur GEO Scanner

      Agundur GEO Scannerofficial

      Agundur-KDE
      A
      license
      Not graded
      quality
      D
      maintenance
      Checks whether a website is readable and citable by AI search engines — llms.txt, Schema.org structured data, AI-bot access in robots.txt, content freshness, answer directness, E-E-A-T signals, plus a LocalBusiness Rich Results validator. Free, no API key, remote Streamable HTTP.
      1
      MIT