Skip to main content
Glama
Sign In
JEStats Screaming Frog Audit

JEStats Screaming Frog Audit

by jestatsio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to JEStats Screaming Frog Audit

No user-submitted related servers found.

    Related Servers

    • seohead

      PavloSEO
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables local-first SEO evidence tooling by analyzing Screaming Frog exports, running bounded live and infrastructure checks, and producing structured audits, task backlogs, and reports via CLI and MCP.
      MIT

    • toadstone

      spcaeo
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables an AI agent to run and query self-hosted SEO crawls directly, returning findings grouped by check with evidence, stable issue ids, and a one-line fix ready to become tickets. Ships ten read-only-by-default, unmetered tools so a request to crawl a site and report what to fix comes back as actionable issues rather than a CSV.
      11
      -

    • agentic-seo-check

      rivi-software
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to audit URLs, static build output, raw HTML, and whole sites for SEO issues, returning actionable findings with rule IDs, severities, fixes, selectors, and evidence, plus optional JavaScript rendering and Lighthouse performance checks.
      5,518 npm
      2
      MIT

    • screaming-frog-mcp

      YerayRodri
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to analyze Screaming Frog SEO Spider crawl files directly, offering SEO audits, issue summaries, custom SQL queries, and comparisons without manual exports.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 9 tools

    Disambiguation4/5

    Each tool has a fairly distinct role: lifecycle control (control_audit), diagnostics (connection_status), native crawl listing (list_crawls), job creation (start_audit), job listing (list_audits), progress polling (audit_status), findings querying (list_findings/finding_details), and reporting (render_report). The only mild overlap is between list_crawls vs list_audits and control_audit vs audit_status, but descriptions clearly separate control actions from status reconciliation.

    Naming Consistency4/5

    Names are uniformly snake_case with mostly verb_noun or clear noun prefixes (list_crawls, start_audit, list_findings, render_report). A few are noun_status/noun_noun forms (connection_status, audit_status, finding_details), which is a minor deviation but still predictable and readable.

    Tool Count5/5

    Nine tools is well-scoped for an audit lifecycle server, with each tool earning its place across connection, crawl listing, job management, findings, and reporting. No redundant or filler tools are apparent.

    Completeness4/5

    The surface covers the full audit lifecycle: connectivity diagnostics, native crawl enumeration, job creation/control/status, findings retrieval, and report rendering. Minor gaps exist (e.g., no explicit export/download or findings export beyond render_report, no delete/cleanup of audit jobs), but core workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data

    Resources