Skip to main content
Glama
Sign In
mcp-seo-auditor

mcp-seo-auditor

by petrovicistefan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to mcp-seo-auditor

No user-submitted related servers found.

    Related Servers

    • founder-toolkit-mcp

      kienpt91
      A
      license
      A
      quality
      B
      maintenance
      Enables agents to run SEO and AI-search readiness audits (llms.txt, crawler access, sitemaps, structured data, redirects, indexability, and more), look up startup revenue listings and leaderboards, and check a domain's SPF, DKIM, DMARC, and MX records with concrete fixes. Runs locally over stdio with no account or API key, and frames all third-party responses as untrusted data.
      7
      MIT

    • EdGEO

      edgarcia-id
      A
      license
      A
      quality
      A
      maintenance
      It enables compatible AI agents to audit public web pages, crawl bounded same-host site samples, collect and compare AI answers, and read a user's own Google Search Console data locally.
      9
      650 npm
      2
      Apache 2.0

    • librecrawl-technical-seo-audit

      adityaarsharma
      A
      license
      Not graded
      quality
      B
      maintenance
      Open-source technical SEO crawler MCP server built on LibreCrawl. Runs full audits inside Claude, Cursor, or Codex — 50+ checks (hreflang, schema.org, security headers, WAF detection on 200-OK pages), chunked-progressive engine for large sites, ephemeral by design (server forgets every audit after download).
      45
      MIT

    • maxaeo-ai-visibility-mcp

      maxaeo
      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
      71 npm
      1
      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.9/5.0

    Scored across 3 tools

    Disambiguation5/5

    The three tools have clearly distinct inputs and scopes: audit_html takes supplied markup with no network, audit_url fetches a single public page, and crawl_site traverses up to 10 same-origin pages. There is no realistic way to confuse which tool to pick for a given task.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern (audit_html, audit_url, crawl_site). The verbs (audit/crawl) differ meaningfully to reflect the differing action, and the convention is uniform throughout.

    Tool Count4/5

    Three tools is on the lean side but each earns its place by covering a distinct input path (raw HTML, single URL, multi-page crawl). The surface is tightly scoped to static SEO auditing without redundant tools.

    Completeness4/5

    The core workflow—auditing static HTML and single URLs plus a bounded same-origin crawl—is well covered. Minor gaps exist around sitemap/robots analysis and broken-link or redirect-chain detection, but agents can work around these, and the bounded crawl avoids dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources