Skip to main content
Glama

Related Servers

Alternatives to Prerender Buddy MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      MCP server and CLI for querying Common Crawl via AWS Athena, enabling users to check a domain's presence in crawls, analyze dynamics, compare domains, and inspect page text.
      13
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for AI search crawler governance, brand safety, and search infrastructure auditing. Provides tools to audit robots.txt, canonical links, sitemaps, redirects, and send IndexNow notifications.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to scrape, batch-scrape, map, crawl, search, parse documents and feeds, extract structured data, search a local SQLite corpus and watch pages for changes, returning clean markdown with no API keys. Runs entirely locally, with optional browser rendering, polite retries and on-disk output.
      0
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to audit client websites read-only: page and structured-data checks, crawler access, Core Web Vitals, site crawls, answerability scoring, Search Console reporting and answer-engine visibility. Every tool is scoped to a per-client domain allowlist, routed through an SSRF guard and rate limits, and returns fetched third-party text inside a fenced untrusted-data block.
      103 npm
      MIT

    TDQS

    A3.9/5.0

    Scored across 3 tools

    Disambiguation4/5

    The three tools target clearly different artifacts: discovery files (robots.txt/sitemap/llms.txt), returned HTML for one crawler UA, and a comparison of two UA responses. check_crawler_readability and compare_http_responses both involve crawler user-agents and could be momentarily confused, but the inspect-vs-compare distinction is spelled out in the descriptions.

    Naming Consistency5/5

    All three names follow a strict verb_noun pattern (check_discovery_files, check_crawler_readability, compare_http_responses) in consistent snake_case. The shared check_/compare_ prefixes map cleanly to their actions.

    Tool Count4/5

    Three tools is lean but well-matched to a narrow diagnostic purpose covering discovery files, crawler readability, and response comparison. It is slightly thin since each tool is quite broad, but no tool feels redundant or missing.

    Completeness4/5

    The surface covers the key prerender/crawler audits: discovery files, crawler-visible HTML, and UA response diffs. A gap remains in that no tool captures JS-executed or rendered output, though the descriptions make clear this is deliberate scope rather than an oversight.

    Maintenance

    ActivityActive
    ResponsivenessNo issues