geo-seo-readiness-lite
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Checks whether a public website can be read and cited by AI search engines. Start with quick_readiness_report, then drill into a single check.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| quick_readiness_reportA | Run all checks (AI crawler access, llms.txt, JSON-LD/canonical, sitemap) for a URL and return a prioritized fix list. |
| check_ai_crawler_accessA | 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. |
| check_llms_txtA | Fetch /llms.txt for the site and check that it is Markdown with a title, sections and links (detects HTML soft-404s). |
| extract_structured_dataA | Extract JSON-LD types, canonical, og:url, title, meta description and initial-HTML text size for a page; flags canonicals pointing to another host. |
| check_sitemapA | Find the XML sitemap (robots.txt Sitemap: lines or /sitemap.xml) and count its URLs. Reads up to 4 MiB; supports gzip. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
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.
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.
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.
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.