Skip to main content
Glama
seoradar-mcp

seoradar-mcp

Related Servers

Alternatives to seoradar-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables running SEO and AI/GEO visibility audits on websites, reading audit results, competitor analyses and expert reports, and importing or retrieving editorial calendars, all from any MCP client such as Claude Desktop, Claude Code or Cursor.
      11
      47 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Provides on-page SEO analysis via MCP tools, including page audits, schema extraction, robots.txt checks, sitemap parsing, and link analysis. No API keys required; works with any MCP-compatible client.
      5
      20 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Checks what GPTBot, ClaudeBot, PerplexityBot and 50+ other AI crawlers can read on a site and what its access policy allows, checks whether a page permits search, answers, training or agent use (with a signed receipt), generates llms.txt, robots.txt and JSON-LD, and reads your Answer Analysis. Nine tools for Claude Desktop, Cursor and other MCP clients.
      9
      139 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to run SEO audits and use site tools for meta tags, robots.txt, schema validation, SERP previews, Core Web Vitals, Open Graph, hreflang, Search Console, GA4, keywords, and backlinks via the Model Context Protocol.
      73 npm
      MIT
    • A
      license
      D
      quality
      C
      maintenance
      Enables LLMs to perform SEO tasks such as keyword research, SERP analysis, backlink analysis, site audits, and more by exposing DataForSEO and other SEO APIs as MCP tools.
      224
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to perform instant SEO audits, check robots.txt, sitemaps, and AI crawler access for any URL without API keys.
      MIT

    TDQS

    A4.3/5.0

    Scored across 7 tools

    Disambiguation5/5

    All tools have clearly distinct purposes: seo_audit triggers an audit and returns a summary, while get_audit_results fetches a detailed report by hash; the description explicitly directs agents to use both together. Monitoring tools (list/add/remove/get status) are cleanly separated by action and scope, and check_api_usage stands alone.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (check_api_usage, get_audit_results, list_monitored_urls, add_monitored_url, remove_monitored_url, get_monitoring_status). However, seo_audit breaks the pattern as a noun phrase rather than a verb_noun construction, creating a minor inconsistency.

    Tool Count5/5

    With 7 tools, the set is well-scoped for an SEO audit and monitoring service. Each tool covers a distinct core operation with no redundancy or bloat, making the count appropriate for the domain.

    Completeness4/5

    The tool set covers the core lifecycle for audits (run, retrieve details) and monitoring (add, list, get status, remove), plus API quota checking. Minor gaps like updating monitoring settings or listing historical audits exist, but agents can work around them without major failures.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data