Skip to main content
Glama
SerpstatGlobal

LLM Brand Monitor MCP Server

Official
by SerpstatGlobal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to LLM Brand Monitor MCP Server

No user-submitted related servers found.

    Related Servers

    • mcp-server-peecai

      thein-art
      A
      license
      A
      quality
      C
      maintenance
      Track how your brand appears in AI-generated answers across ChatGPT, Perplexity, and other AI models. Analyze visibility, sentiment, citations, and domain rankings with 31 tools — including analytics reports, chat inspection, query analysis, and full CRUD for brands, prompts, tags, and topics.
      17
      73 npm
      2
      MIT
    • LLM Pulse MCP Server by LLM-Pulse

      LLM Pulse MCP Serverofficial

      LLM-Pulse
      A
      license
      A
      quality
      B
      maintenance
      Monitors brand mentions, citations, sentiment, competitor share of voice, and GEO performance across AI search engines.
      1
      1
      MIT

    • Citesurf MCP

      citesurf
      A
      license
      A
      quality
      C
      maintenance
      Enables brand visibility monitoring across major AI platforms like ChatGPT, Claude, Gemini, and Perplexity. It allows users to track visibility scores, analyze competitor data, and receive actionable insights to improve AI-generated brand recommendations.
      16
      7 npm
      1
      MIT

    • MentionsAPI MCP Server

      mukul-dutt
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to check brand mentions across AI search surfaces like ChatGPT, Claude, Gemini, Perplexity, and Google AI Overviews using natural language queries.
      4
      3 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

    A4.4/5.0

    Scored across 17 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose, targeting specific resources (projects, prompts, scans, results, competitors, links, history, usage) with unique actions (list, get, create, update, archive, add, delete, run). There is no functional overlap.

    Naming Consistency5/5

    All tools follow a consistent `lbm_verb_noun` pattern in snake_case. Verbs are standard and nouns are appropriately singular or plural, making it easy to infer tool behavior from names.

    Tool Count5/5

    With 17 tools, the scope is well-balanced. It covers full lifecycle management (CRUD for projects, prompts, scans, results) and adds analytics (competitors, links, history, usage) without unnecessary bloat.

    Completeness4/5

    The surface is nearly complete, covering all major operations. Minor gaps exist: no dedicated tool to update prompts (only add/delete) and no permanent project deletion (only archive). These are workable but not critical.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources