Skip to main content
Glama
RichardDillman

Googlebot Simulator MCP

Related Servers

Alternatives to Googlebot Simulator MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables users to check which page content AI crawlers like GPTBot and ClaudeBot cannot read because it only appears after JavaScript runs, by comparing raw HTML with rendered HTML in headless Chrome.
      AGPL 3.0
    • A
      license
      A
      quality
      D
      maintenance
      Audits AI-bot visibility: robots.txt per-bot for 22 AI user-agents (GPTBot/ClaudeBot/PerplexityBot/etc), Cloudflare flags, JSON-LD, sitemap, llms.txt, SPA shell, plus cross-model brand mentions via Perplexity + OpenRouter. 0-100 score. SSRF-guarded, spend-capped.
      4
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables a coding agent to audit any public page the way search engines and AI crawlers see it, including per-crawler robots.txt rules, CDN/firewall blocks, and no-JavaScript content. It returns a prioritized fix pack showing where each fix belongs in the codebase plus a command to verify it, so the agent can apply the changes, flag human-only settings, and re-run the audit to confirm.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables JavaScript-rendered Google searches and readable text extraction from public URLs via a real Chrome instance, along with health and CAPTCHA status monitoring.
      3
      69
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Analyze and generate robots.txt files with AI crawler awareness. Fetch any site's robots.txt, detect which AI bots (GPTBot, ClaudeBot, PerplexityBot, Google-Extended) are blocked or allowed, and generate optimized robots.txt with toggle controls for 20+ AI crawlers.
      5
      1
      MIT

    TDQS

    A4.2/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of confusion between tools. The tool's purpose is clearly distinct by default.

    Naming Consistency5/5

    The single tool name 'simulate_googlebot' follows a clear verb_noun pattern and is descriptive. With only one tool, there are no naming inconsistencies.

    Tool Count3/5

    One tool is on the low end, but it is well-scoped to a specific use case (simulating Googlebot). It feels slightly thin but not inappropriate for its narrow domain.

    Completeness4/5

    The tool covers the main aspects of simulating Googlebot crawling (user-agent, idle detection, event capture, timing, screenshots). No obvious gaps for its stated purpose, though it is a single tool.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues