QQQ AI Visibility Checker

QQQ AI Visibility Checker: MCP server

Free AI visibility and GEO check for any website, inside Claude, ChatGPT, Cursor, VS Code and other MCP clients. It tells you whether AI crawlers (GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended and others) may read a site, whether the site is technically ready for AI search, and what the latest public report says about brand mentions and citations in answers from ChatGPT, Gemini, Perplexity, Claude and Kimi.

• Server URL: https://qqq.ee/mcp (use this exact host: www.qqq.ee redirects, and a redirect breaks POST requests)
• Transport: Streamable HTTP (stateless JSON responses)
• Authentication: none, no API key
• Registry name: ee.qqq/ai-visibility
• Documentation: https://qqq.ee/en/mcp-server/ (Estonian: https://qqq.ee/mcp-server/)
• Web tool: https://qqq.ee/en/ai-visibility-checker/
• Changes: CHANGELOG.md

This repository holds the documentation and client configuration only. The server is hosted by QQQ OÜ on qqq.ee; there is nothing to install or run.

Tools

All three tools are read-only. The full check of live AI answers runs on qqq.ee, and every answer from the server links there.

What a public report contains

get_public_report returns readable text and the same data as structuredContent.report. Reports are stored as they were measured, so an older report has fewer fields: a missing field means the report predates it, not zero.

There is no combined score: mentions, citations and technical readiness stay separate.

Connect

Claude (claude.ai, Claude Desktop)

Settings → Connectors → Add custom connector → URL https://qqq.ee/mcp, no authentication.

Claude Code

claude mcp add --transport http qqq-ai-visibility https://qqq.ee/mcp

ChatGPT

Developer mode → Settings → Connectors → add a server with URL https://qqq.ee/mcp, authentication "No authentication".

Cursor

~/.cursor/mcp.json or .cursor/mcp.json in a project (examples/cursor.mcp.json):

{

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

VS Code

.vscode/mcp.json (examples/vscode.mcp.json):

{

"servers": { "qqq-ai-visibility": { "type": "http", "url": "https://qqq.ee/mcp" } } }

Windsurf

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 ~/.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 ~/.codex/config.toml:

[mcp_servers.qqq-ai-visibility]

url = "https://qqq.ee/mcp"

Clients that only support stdio

Use the mcp-remote bridge (examples/claude-desktop-stdio.json):

{

"mcpServers": { "qqq-ai-visibility": { "command": "npx", "args": ["-y", "mcp-remote", "https://qqq.ee/mcp"] } } }

Then ask, for example: *"Check the AI visibility of example.com."*

Plugins

This repository is also a plugin for agents that install plugins from GitHub. It bundles the remote server config and a skill that tells the agent when to use each tool:

• Claude Code: /plugin marketplace add meelis545/qqq-ai-visibility-mcp, then /plugin install qqq-ai-visibility@qqq-ai-visibility (.claude-plugin/, .mcp.json, skills/)
• Cursor: .cursor-plugin/plugin.json and mcp.json
• Agent Plugins (agent-plugins.org): plugin.json and mcp.json
• OpenClaw / ClawHub: clawhub/qqq-ai-visibility/SKILL.md, a skill that calls the same tools with curl (no MCP client needed)

Limits

Only public websites are checked: IP addresses, localhost and internal hostnames are refused, and redirects are validated again.

Privacy

• The IP address is only the key of a daily counter; counters are deleted after two days. Calls from Cloudflare Workers all share one Cloudflare address, so for them the key is the calling site's domain, which Cloudflare adds to the request.
• Usage statistics (90 days): step, language, domain, status, country, duration. No IP address, no client name.
• Headers, request bodies, MCP client details and keys are not logged.
• An MCP check does not create a public report and sends nothing to AI models. get_public_report only reads a report that is already public on qqq.ee.

Full policy: https://qqq.ee/en/privacy-policy/

Protocol details

• Protocol versions: 2025-11-25, 2025-06-18, 2025-03-26
• No Mcp-Session-Id, no SSE stream; GET from a browser redirects to the web tool, other GET requests get 405
• CORS open (*): no cookies or credentials are used
• server.json is the entry in the official MCP Registry

Contact

QQQ OÜ, Niine 11, 10414 Tallinn, Estonia · q@qqq.ee · https://qqq.ee/en/

QQQ OÜ is an SEO and AI search agency and is not affiliated with Invesco QQQ Trust or the Nasdaq ticker QQQ.