ai-visibility-mcp
Related Servers
Alternatives to ai-visibility-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceGenerates a complete suite of AI readiness files (llms.txt, ai.txt, schema, RAG indexes) for any website to optimize representation in ChatGPT, Claude, Gemini, and Perplexity.3-
- AlicenseAqualityCmaintenanceAnalyze and generate robots.txt files with AI crawler awareness. Fetch any site's robots.txt, detect which AI bots (GPTBot, ClaudeBot, PerplexityBot, Google-Extended) are blocked or allowed, and generate optimized robots.txt with toggle controls for 20+ AI crawlers.51MIT
- AlicenseAqualityBmaintenanceEnables AI agents to check whether a public website is crawlable, understandable, and ready for AI search workflows through local-only audits of robots.txt, sitemaps, metadata, and llms.txt.350 npm1MIT
- AlicenseAqualityBmaintenanceEnables inspection of any website's AI-search readiness, checking AI crawler blocks, llms.txt, schema markup, and indexing directives from MCP clients like Claude.433 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to create, validate, and audit llms.txt files for websites, including checking against Google Lighthouse's Agentic Browsing requirements, via Streamable HTTP with no API key needed.8 npm2MIT
- AlicenseAqualityDmaintenanceAudits AI-bot visibility: robots.txt per-bot for 22 AI user-agents (GPTBot/ClaudeBot/PerplexityBot/etc), Cloudflare flags, JSON-LD, sitemap, llms.txt, SPA shell, plus cross-model brand mentions via Perplexity + OpenRouter. 0-100 score. SSRF-guarded, spend-capped.41MIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: one checks live robots.txt and llms.txt, one audits Cloudflare's specific AI bot settings, and one generates llms.txt content. There is no overlap or ambiguity.
All names use snake_case and include a verb, but check_visibility and generate_llms_txt follow a verb_noun pattern while cloudflare_ai_bot_audit places the verb at the end of a compound noun. This slight inconsistency is minor and does not hinder readability.
Three tools is a reasonable number for a focused domain like AI crawler visibility. The scope is narrow enough that each tool earns its place without feeling sparse or excessive.
The tool set covers the core workflows: checking visibility, auditing a specific provider's settings, and generating content. However, it lacks support for other hosting providers beyond Cloudflare and does not include any write/modify capabilities, which may be expected in a visibility management server but is likely intentional as an analysis-only tool.