QQQ AI Visibility Checker
officialFree AI visibility and GEO check for any website: whether AI crawlers (GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended) can read it, technical readiness for AI search, and the latest public report of brand mentions and citations in ChatGPT, Gemini and Perplexity. Remote, no API key, read-only.
What can you do with QQQ AI Visibility Checker MCP?
- Check a domain's AI visibility — Ask your assistant to run a technical readiness check on any public domain, covering robots.txt, AI crawler access, sitemap, metadata, and more.
- Retrieve a public AI visibility report — Request the latest published report for a domain, including AI answer mentions, website citations, per-engine results, and top cited sources.
- Understand what the checker measures — Ask for an explanation of the tool's scope, its limitations, and links to the English and Estonian tool pages.
Hosted MCP Server
npx add-mcp 'https://qqq.ee/mcp'Installs into Claude Code, Codex, Cursor and more
Documentation
1
What the server does
The AI Visibility Checker shows whether AI assistants name a company and cite its website, and whether the website is technically readable for AI crawlers. The MCP server brings the free part of that check into any MCP client: you can ask Claude or Cursor to check a domain without leaving the conversation.
The MCP server is a way in, not a second engine. It runs the same technical check as step 1 of the web tool and reads the public report of the domain if someone has already checked it on qqq.ee. Asking AI models about a brand is the paid step, and it only runs on the website.
2
Tools
| Tool | Input | What it returns |
|---|---|---|
| check_ai_visibility | domain (required), language: en (default) or et | Technical readiness for AI search: homepage, HTTPS, robots.txt, access for AI crawlers such as GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot and Google-Extended, sitemap, title, description, H1, canonical, noindex, Organization or Person structured data, JavaScript dependence, key pages and llms.txt. The three most important fixes. If the domain has a public report: mentions out of all answers and citations of the company's own website. A prefilled link to the full check. |
| get_public_report | domain (required), language | The latest public report of a domain, if someone has run the full check on qqq.ee: date, market and field, mentions in search-grounded AI answers, citations of the company's own website, results per AI engine, the questions asked, the most cited sources, other companies named and short answer excerpts, plus the link to the report page. Fetches no website and asks no AI model. Without a report it says so and links the full check. |
| get_tool_info | language | What the checker measures, its limits, and the English and Estonian links. Fetches nothing. |
All three tools are read-only. Each answer ends with a link to qqq.ee: the tool page or the domain's report page.
3
Connect it
The server address is the same in every client:
One-click install: Add to Cursor · Install in VS Code.
Claude (claude.ai and Claude Desktop)
Settings → Connectors → Add custom connector. Enter the URL above and leave authentication empty.
Claude Code
claude mcp add --transport http qqq-ai-visibility https://qqq.ee/mcp
ChatGPT
In developer mode open Settings → Connectors, add a server with the URL above and choose "No authentication".
Cursor
Use the Add to Cursor link, or add to ~/.cursor/mcp.json, or to.cursor/mcp.json in a project:
{
"mcpServers": {
"qqq-ai-visibility": { "url": "https://qqq.ee/mcp" }
}
}
VS Code
Use the Install in VS Code link, or add to.vscode/mcp.json:
{
"servers": {
"qqq-ai-visibility": { "type": "http", "url": "https://qqq.ee/mcp" }
}
}
Windsurf
Add to the Windsurf MCP config (Cascade → MCP servers → View raw config):
{
"mcpServers": {
"qqq-ai-visibility": { "serverUrl": "https://qqq.ee/mcp" }
}
}
Gemini CLI
gemini mcp add --transport http qqq-ai-visibility https://qqq.ee/mcp
Or in ~/.gemini/settings.json:
{
"mcpServers": {
"qqq-ai-visibility": { "httpUrl": "https://qqq.ee/mcp" }
}
}
OpenAI Codex CLI
codex mcp add qqq-ai-visibility --url https://qqq.ee/mcp
Or in ~/.codex/config.toml:
[mcp_servers.qqq-ai-visibility]
url = "https://qqq.ee/mcp"
Clients that only support stdio
The mcp-remote bridge runs the remote server as a local process:
{
"mcpServers": {
"qqq-ai-visibility": { "command": "npx", "args": ["-y", "mcp-remote", "https://qqq.ee/mcp"\] }
}
}
After connecting, ask for example: "Check the AI visibility of example.com."
4
Limits and cost
| What | Limit |
|---|---|
| check_ai_visibility per IP address | 5 a day (UTC) |
| check_ai_visibility in total | 300 a day |
| An invalid domain | does not use up a check |
| get_public_report, get_tool_info and the protocol calls (initialize, tools/list, ping) | no limit |
| Request size | 16 KB, at most 10 messages in a batch |
The check is free. It loads only the website's own pages, about five to eight requests, and a result is shared from a one-hour cache. When the daily limit is reached, the server fetches nothing and answers with a link to run the check on qqq.ee.
Only public websites are accepted: IP addresses, localhost and internal hostnames are refused, and every redirect is checked again.
6
Technical details
| Setting | Value |
|---|---|
| URL | https://qqq.ee/mcp (without www: www.qqq.ee answers with a 301 redirect, which MCP clients do not follow for POST) |
| Transport | Streamable HTTP: POST with JSON-RPC 2.0, answered as application/json |
| Sessions | Stateless: no Mcp-Session-Id and no SSE stream. A GET from a browser is redirected to the tool page, other GET requests get 405 |
| Protocol versions | 2025-11-25, 2025-06-18, 2025-03-26 |
| Authentication | None. CORS is open because no cookies or credentials are used |
| Registry name | ee.qqq/ai-visibility |
The server is listed in the Official MCP Registry as ee.qqq/ai-visibility. Client configuration examples are in the public GitHub repository.
Questions and bug reports: q@qqq.ee.