Skip to main content
Glama

Related Servers

Alternatives to geo-inspector-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      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
      50 npm
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      An 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.
      5
      37 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI assistants to run live SEO/readiness audits against 50+ AI crawlers, validate schema and robots.txt, and generate llms.txt, robots.txt, and JSON-LD files directly from MCP-compatible clients like Claude Desktop and Cursor.
      8
      138 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to run a free AI-readiness audit of any URL, checking AI crawler rules, JavaScript-free page text, JSON-LD, llms.txt, sitemap, meta description, FAQ schema, and returning a score with findings and fixes. Also exposes the same capability via an A2A agent endpoint.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Open-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.
      1
      MIT

    TDQS

    A4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of website metadata for AI discoverability: robots.txt, llms.txt, schema markup, and meta directives. No functional overlap.

    Naming Consistency5/5

    All tool names follow a clear verb_noun pattern: check_robots_txt, fetch_llms_txt, detect_schema_markup, check_meta_directives, with consistent snake_case.

    Tool Count5/5

    4 tools is an ideal size for this focused domain—each tool addresses a necessary and distinct inspection task without redundancy or clutter.

    Completeness4/5

    The set covers the key AI-related metadata surfaces: robots.txt, llms.txt, schema.org markup, and meta robots directives. A minor gap is direct sitemap inspection, though sitemaps are referenced in robots.txt.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues