Crawl Readiness MCP Server
Related Servers
Alternatives to Crawl Readiness MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to crawl live websites, audit AEO readiness, generate Schema.org @graph JSON-LD, llms.txt, ai.txt, and robots.txt, inject structured data into HTML, validate optimizations, and retrieve framework-specific code snippets.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to run SEO audits and use site tools for meta tags, robots.txt, schema validation, SERP previews, Core Web Vitals, Open Graph, hreflang, Search Console, GA4, keywords, and backlinks via the Model Context Protocol.73 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants such as Claude, ChatGPT, Cursor, and Claude Code to run 25+ specialized SEO checks on any URL, generate XML sitemaps and robots.txt files, extract brand design elements, and audit technical SEO, content quality, mobile responsiveness, and security.MIT
- AlicenseNot gradedqualityBmaintenanceEnables users to audit websites and online stores for generative and answer-engine readiness, generate deployable llms.txt and llms-full.txt files, JSON-LD schema, and AI crawler rules, analyze robots access for AI bots, and extract clean page content for LLM use.MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude, ChatGPT, Cursor, and other MCP clients to query Google Search Console, GA4, PageSpeed Insights, and live SERPs through 38 read-only SEO tools for quick wins, content decay, indexing, Core Web Vitals, AI traffic, and conversion analysis.2MIT
- AlicenseNot gradedqualityCmaintenanceEnables auditing websites for AI/LLM readiness and generating fixes such as robots.txt rules, llms.txt, JSON-LD schema, and meta tags, plus checking brand and domain citations through natural language.1MIT
TDQS
Scored across 9 tools
Most tools occupy clearly separate slots: generate vs. validate pairs for robots.txt and schema are unambiguous, and get_monitor_trend is a distinct read of existing Answer Analysis data. The main friction is the check_* cluster — check_ai_readiness (site-level score), check_permission (page-level verdict from many signals) and check_content_parity (browser vs. bot diff) all read robots.txt/crawler access, so an agent could pick the wrong one at the edges, though descriptions do differentiate them.
Every name follows verb_noun in snake_case, and the verbs map to a small predictable set (check_, generate_, validate_, get_) that mirrors the resource lifecycle. No camelCase or stylistic outliers.
Nine tools is well inside the sweet spot for a focused diagnostic/generation server. Each tool maps to a distinct artifact or check (readiness, robots, llms.txt, schema, permission, parity, monitor) with no filler.
Coverage is strong: diagnose, generate and validate across the two main artifact types (robots.txt, JSON-LD), plus llms.txt generation, per-page permission verdicts, and a crawler-parity view. The notable asymmetry is that llms.txt and agent-ready files (agents.json) can be generated but not validated, and there is no sitemap-inspection tool even though llms.txt generation depends on one.