ai-visibility-mcp
Related Servers
Alternatives to ai-visibility-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables users to interrogate ChatGPT, Perplexity, and Gemini with buyer questions and live web search to learn whether a business is recommended, ranked, competing with others, and having its website cited. Returns structured findings and estimated provider costs.190 npmMIT
- AlicenseAqualityDmaintenanceTrack brand visibility across ChatGPT, Perplexity, Claude, and Gemini.611MIT
- AlicenseAqualityCmaintenanceProvides twelve read-only tools that report how often ChatGPT, Claude, Gemini, Perplexity and Google AI Overviews name and cite a brand, covering visibility, share of voice, sentiment, competitor mentions, sources, alerts and ranked recommendations with the underlying answers. It lets users query these measurements directly from Claude, Cursor or any MCP client, with denominators and null-handling rules included so results are interpreted correctly.1291 npmMIT
- AlicenseAqualityBmaintenanceChecks whether ChatGPT, Perplexity, and Gemini cite your brand for a given keyword, and who's winning the citation battle for it instead.610MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to monitor and analyze a brand's visibility across ChatGPT, Claude, Perplexity, and Google AI Overviews, providing insights, recommendations, and competitive analysis without switching tabs.25806 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to scan brand visibility across ChatGPT, Claude, Gemini & Perplexity, analyze website GEO readiness, compare competitors, and get actionable recommendations.MIT
TDQS
Scored across 4 tools
Each tool targets a different output: raw answers (ask_engines), per-question business presence (check_visibility), question generation (suggest_questions), and competitor ranking (compare_competitors). The boundary between ask_engines and check_visibility is thin since both fan out the same questions to the same engines, differing only in whether raw output or analysis is returned.
All four tools follow a clean verb_noun snake_case pattern (ask_engines, check_visibility, suggest_questions, compare_competitors). No mixed conventions or vague single-word names.
Four tools is a tight, purposeful surface for a niche AI-visibility monitoring workflow, and each maps to a distinct step. The count is slightly lean given that raw-answer retrieval could arguably be a mode of the analysis tool rather than a peer.
The core loop (generate questions, check presence, benchmark competitors) is covered, but there is no tool for managing configured engines/business identity, no historical or trend tracking across runs, and no export/reporting operation. Agents will hit a dead end if they need to inspect or change configuration rather than just consume results.