geo-check-mcp
Related Servers
Alternatives to geo-check-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceOpen-source MCP server that audits websites for AI search readiness, providing deterministic scoring (0-100) and prioritized fix lists for metrics like JSON-LD, llms.txt, heading hierarchy, and AI crawler access.1MIT
- AlicenseNot gradedqualityDmaintenanceMCP server exposing Generative Engine Optimization tools to any AI agent, enabling checking of llms.txt, auditing robots.txt for AI crawlers, and validating JSON-LD schema.MIT
- AlicenseAqualityAmaintenanceAn MCP server that lets an AI agent audit a page for SEO and GEO — on-page tags, structured data, robots.txt, sitemaps, hreflang, and whether ChatGPT, Claude, Perplexity and Gemini can actually crawl and cite you. No API keys required.17195 npm1MIT
- AlicenseNot gradedqualityNot gradedmaintenanceMCP server for website SEO + GEO analysis. Scan any URL to get scores across 5 categories (SEO, GEO, Performance, Security, Accessibility) with actionable fix recommendations. Enables AI coding assistants to audit websites and implement fixes autonomously.-
- AlicenseAqualityDmaintenanceAn MCP server that gives AI agents tools to inspect a website's visibility to AI answer engines, including crawler permissions, llms.txt, structured data, on-page signals, and a full 29-check AI-readiness audit.545 npmMIT
- AlicenseNot gradedqualityBmaintenanceAn open-source, local-first MCP server for automated Schema.org JSON-LD generation, GA4 metric validation, /llm.txt auditing, and content stickiness analytics.MIT
TDQS
Scored across 3 tools
list_ai_crawlers (reference data), check_robots (offline robots.txt evaluation) and check_site (network-based full GEO audit) each have a clearly stated purpose. The only mild overlap is that check_site also covers robots.txt AI-crawler access, so an agent could conceivably pick check_site when it only wanted the robots check, but the offline/online distinction in the descriptions resolves this.
All three names follow a consistent verb_noun snake_case pattern: list_ai_crawlers, check_robots, check_site. The check_ prefix groups the two evaluation tools logically and list_ signals the reference-data tool.
Three tools is on the small side, but the server's scope (GEO/technical crawlability checks) is narrow and each tool earns its place: one reference list, one offline evaluator, one full site audit. Slightly thin but well scoped rather than padded.
The surface covers the core GEO workflow: discovering which crawlers matter, testing robots.txt offline, and running a combined audit of robots.txt, JSON-LD, /llms.txt, sitemap and head tags. Minor gaps exist — no standalone llms.txt or JSON-LD/sitemap check, and no offline HTML inspection — but these are reachable through check_site.