Qqq AI Visibility MCP

What qqq-ai-visibility-mcp does

The qqq-ai-visibility-mcp MCP server exposes QQQ's AI Visibility Checker through MCP. It evaluates a public domain's technical readiness for AI search and returns checks covering the homepage, HTTPS, robots.txt, AI crawler permissions, sitemap, title, description, H1, canonical URL, noindex directives, structured data, JavaScript dependence, important pages, and llms.txt.

The result can also include the most recent public report for the domain. That report records brand mentions across answers from ChatGPT, Gemini, and Perplexity, along with citations to the company's own website, when the domain has been checked previously. Each check includes a prefilled link to the full QQQ report.

How it works

The qqq-ai-visibility-mcp MCP server is hosted by QQQ OÜ at https://qqq.ee/mcp. It uses stateless Streamable HTTP with JSON responses and does not require an API key, login, or MCP session identifier. The repository contains documentation and client configuration examples rather than an application that must be installed locally.

check_ai_visibility accepts a required domain and an optional language value: en is the default and et selects Estonian. The service checks public websites directly for the supported technical signals. The live AI-answer portion is performed on qqq.ee, and the MCP response links to that web-based check.

get_tool_info accepts a language option and explains the checker, its scope, limits, and English and Estonian web links. It does not fetch a website.

Setup and configuration

Connect an MCP client to https://qqq.ee/mcp without authentication. Claude Desktop and Claude's connector flow can use the URL directly. Claude Code can add it with an HTTP transport, while Cursor and VS Code have configuration examples in the repository. Clients that only accept stdio can use mcp-remote as a bridge to the same endpoint.

For example, a Cursor configuration uses the following server entry:

{
  "mcpServers": {
    "qqq-ai-visibility": {
      "url": "https://qqq.ee/mcp"
    }
  }
}

After connecting, ask the client to check a public domain, such as example.com. No environment variables are required.

Tools and capabilities

• check_ai_visibility: Inspects public technical and GEO-related signals, reports the three most important fixes, and returns a previous public visibility report when one exists.
• get_tool_info: Describes what the checker measures and provides links to its web tools without fetching a site.
• Supports English and Estonian output through the language parameter.
• Returns a link for completing the full QQQ check of live AI answers.

Limitations and notes

The qqq-ai-visibility-mcp MCP server is read-only. It does not change websites, create public reports through the MCP check, or send the checked content to AI models. Only public websites are accepted: IP addresses, localhost, and internal hostnames are rejected, and redirects are validated again.

check_ai_visibility is limited to five checks per IP address per UTC day and 300 checks globally per day. Invalid domains do not consume a check. Tool discovery, initialization, ping, and get_tool_info are not subject to that check limit. Requests are limited to 16 KB and batches may contain up to 10 messages.

The service uses an IP address only as the key for the daily counter, with counters deleted after two days. Operational statistics retain items such as step, language, domain, status, country, and duration for 90 days; the stated policy excludes IP addresses, client names, headers, request bodies, MCP details, and keys from logging.