Skip to main content
Glama
nmarijane

LightSpot MCP Server

by nmarijane

Related Servers

Alternatives to LightSpot MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Checks a website's AI readiness: can ChatGPT, Claude, Perplexity, Google AI and 50+ other AI crawlers (GPTBot, ClaudeBot, PerplexityBot) access it? Scores the site, then generates llms.txt, an AI-crawler robots.txt and JSON-LD, and reads LLM Monitor trends, from Claude Desktop, Cursor and other MCP clients.
      8
      206 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables Claude and other MCP clients to read Google Search Console and Bing Webmaster Tools data, analyze query/page performance, compare periods, inspect indexing and canonical status, and retrieve sitemap and keyword statistics.
      23
      2,007 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI assistants to run evidence-first technical SEO and GEO audits, inspect HTML, structured data, robots policies and sitemaps, and compare before/after reports to verify fixes.
      5
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Exposes OptiQra's full SEO/GEO/AEO audit and AI-fix/insight tools as MCP tools for AI clients like Claude, Cursor, and Windsurf. Use natural language to crawl URLs, analyze performance/a11y/security, and generate AI-driven fixes and strategy insights.
      4
      32 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to run SEO audits and reporting over a user's own Search Console, Google Analytics, Bing, and keyword/competitor provider data, including page/index status, traffic comparisons, backlinks, and local crawl/internal-link analysis.
      1,975 npm
      585
      Apache 2.0

    TDQS

    A3.7/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: run_audit vs audit_and_wait (async vs blocking), get_audit_status (lightweight) vs get_audit (full results), and get_editorial_calendar vs create_editorial_calendar (read vs write) are well-separated by their descriptions. Minor overlap exists between get_audit and get_expert_report (both surface audit-derived output) and between get_site and list_site_audits, but the descriptions clarify the boundaries.

    Naming Consistency4/5

    Ten of eleven names follow a predictable verb_noun pattern (get_*, list_*, run_audit, create_editorial_calendar), which is highly consistent. The lone deviation is audit_and_wait, which inverts to a noun_and_verb compound and breaks the otherwise uniform convention.

    Tool Count5/5

    Eleven tools is a well-scoped set for an SEO/GEO audit platform, comfortably within the ideal 3-15 range. Each tool earns its place by covering a distinct phase: audit triggering, polling, results retrieval, site lookup, and calendar management.

    Completeness4/5

    The audit lifecycle is well covered (trigger, poll, fetch, expert report, wait convenience), and the editorial calendar supports read plus idempotent import. Gaps remain in write operations for sites (no create/delete) and the inability to trigger a new competitor analysis or delete calendar slots, but these are workable given the read-heavy workflow.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues