JEStats Screaming Frog Audit
Related Servers
Alternatives to JEStats Screaming Frog Audit
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables 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
- AlicenseAqualityDmaintenanceEnables SEO auditing and site analysis by crawling websites, identifying issues, and generating reports like sitemaps and markdown exports.59 npm4MIT
- AlicenseNot gradedqualityCmaintenanceEnables 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
- FlicenseAqualityBmaintenanceEnables comprehensive website SEO analysis including crawling, on-page audits, site structure visualization, and content topic classification with taxonomy mapping.71-
- AlicenseCqualityCmaintenanceEnables read-only SEO and generative-search visibility audits by combining official Google Search Console and Bing Webmaster Tools data with a bounded crawl of a site's public pages. Returns confirmed issues, per-query and per-page opportunities, GEO readiness signals, and prioritized actions with verification steps, while also supporting import of Google generative-search impressions from CSV exports.25MIT

crawlcove-mcpofficial
AlicenseAqualityAmaintenanceLets AI assistants crawl sites or load exported crawl data, then query SEO issues, inspect individual pages, and trace broken internal links from real crawl results. It supports live same-origin crawls up to 200 pages and exported datasets for deeper analysis.6MIT
TDQS
Scored across 9 tools
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.
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.
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.
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.