Skip to main content
Glama
visibilityradar-mcp

visibilityradar-mcp

visibilityradar-mcp

Analyze how AI models see your brand — directly from Claude Desktop, Cursor, Windsurf, or any MCP-compatible AI assistant.

npm version License: MIT sarefe12-sudo/visibilityradar-mcp MCP server

What is this?

VisibilityRadar measures how often and how positively AI models (Claude, GPT-4o, Gemini, Perplexity, Grok, DeepSeek) mention your brand. This MCP server brings that analysis directly into your AI assistant — no browser needed.

Ask Claude: "How visible is my brand on AI models compared to my competitors?" and get an instant, structured report.

Related MCP server: ai-visibility-mcp

Tools

Tool

Description

analyze_brand

Run a full AI visibility analysis: overall score, per-model scores, sentiment, competitors, top recommendations

get_brand_history

Fetch past analysis results and score trends for a brand

Requirements

Setup

1. Get your API key

Go to visibilityradar.ai/profile → scroll to MCP API Keys → click Generate Key.

2. Configure your AI assistant

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "visibilityradar": {
      "command": "npx",
      "args": ["visibilityradar-mcp"],
      "env": {
        "VR_API_KEY": "vr_your_api_key_here"
      }
    }
  }
}

Cursor

Edit ~/.cursor/mcp.json:

{
  "mcpServers": {
    "visibilityradar": {
      "command": "npx",
      "args": ["visibilityradar-mcp"],
      "env": {
        "VR_API_KEY": "vr_your_api_key_here"
      }
    }
  }
}

Windsurf

Edit ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "visibilityradar": {
      "command": "npx",
      "args": ["visibilityradar-mcp"],
      "env": {
        "VR_API_KEY": "vr_your_api_key_here"
      }
    }
  }
}

3. Restart your AI assistant

After saving the config, restart Claude Desktop / Cursor / Windsurf. You should see VisibilityRadar listed as a connected tool.

Example Usage

Once connected, just ask your AI assistant:

Analyze the AI visibility of "Notion" in the US market, compare against Obsidian and Roam Research
What is the brand history for "Linear"?
How does "Shopify" score across AI models compared to WooCommerce?

Example Output

# AI Visibility Report: Notion

**Overall Score: 74/100** (Strong)
**Market:** US
📊 Sentiment: 68% positive · 24% neutral · 8% negative

## Per-Model Scores
  • Claude: 82/100
  • GPT-4o: 78/100
  • Gemini: 71/100
  • Perplexity: 69/100
  • Grok: 74/100
  • DeepSeek: 66/100

## Competitor Comparison
  • Obsidian: 58/100
  • Roam Research: 41/100

## Top Recommendations
  1. [HIGH] Build a stronger Wikipedia presence with product comparisons
  2. [HIGH] Earn more coverage on tech publications indexed by Perplexity
  3. [MEDIUM] Increase presence on X/Twitter for Grok visibility

---
📊 Full report, playbook & content strategy: https://visibilityradar.ai/dashboard

Rate Limits

Plan

Daily MCP analyses

Monthly analyses

Pro

5/day

10/month

Agency

20/day

Unlimited

Every analyze_brand call via MCP counts as one analysis and is saved to your dashboard automatically.

API Endpoints

The MCP server calls the following VisibilityRadar API endpoints:

  • POST https://visibilityradar.ai/api/mcp/analyze — Run analysis

  • GET https://visibilityradar.ai/api/mcp/history — Fetch history

Authentication uses the x-api-key header with your API key.

License

MIT

Available Tools

2 tools
analyze_brandA

Analyze how visible a brand is across AI models (Claude, GPT-4o, Gemini, Perplexity, Grok, DeepSeek). Returns an overall score, per-model scores, sentiment analysis, competitor comparison, and top recommendations. Results are also saved to the VisibilityRadar dashboard.

Inputs: brand (required), market, competitors.

get_brand_historyA

Get the analysis history for a specific brand from the VisibilityRadar dashboard. Shows score trends over time.

Inputs: brand (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: analyze_brand performs new analyses, while get_brand_history retrieves past results. No overlap or ambiguity.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern (analyze_brand, get_brand_history), making the tool set predictable and easy to navigate.

    Tool Count3/5

    With only 2 tools, the server is on the lower end of the typical range for a dedicated service. While the core functionality is covered, the count feels slightly thin for a dashboard scenario.

    Completeness2/5

    The set covers analysis creation and history retrieval but lacks basic CRUD operations such as listing all brands, updating analyses, or deleting entries, which are significant gaps for a dashboard.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      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
      11 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to check whether AI assistants recommend a brand and audit a site's AI-agent readiness, providing visibility scores and specific gaps.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to run brand-visibility audits by querying multiple AI engines, generating competitive leaderboards, and identifying growth opportunities. Integrates with any MCP-capable client to measure and act on brand discoverability in AI recommendations.
      MIT