Skip to content

QQQ AI Visibility Checker MCP server

ee.qqq/ai-visibilityqqq.eestreamable-httpv1.2.0Scanned

Free AI visibility check: can AI crawlers read a site, and do ChatGPT, Gemini, Perplexity cite it?

3 tools: 1 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 1 write, 2 read.
  • Reads private data · 2
  • Reads text others write · 3
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the QQQ AI Visibility Checker MCP server can do

The QQQ AI Visibility Checker MCP server is published by qqq.ee, a domain the MCP Registry verified. It has 3 tools. It can create or change data (1 tool: check_ai_visibility), but cannot delete data. 2 tools only read.

2 tools read private data (get_public_report and get_tool_info); 3 tools bring in text other people can write (check_ai_visibility, get_public_report and get_tool_info).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 18, 2026, version 1.2.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

3 tools

Changes things 1Claude Code: ask
  • check_ai_visibilityFree AI visibility and GEO (generative engine optimization) check for a company website by QQQ (qqq.ee).Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Free AI visibility and GEO (generative engine optimization) check for a company website by QQQ (qqq.ee). Checks whether AI crawlers (GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended ...) may read the site, plus robots.txt, sitemap, Organization structured data, indexability and llms.txt, and returns the latest public report of brand mentions and citations in ChatGPT, Gemini and Perplexity answers when the domain has been checked before. The full AI answer check (brand visibility in live AI answers) runs on qqq.ee: the result always includes a prefilled link. Limited to a few checks per day; read-only.

    Annotations the server declares

    • title: Check AI visibility of a website
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 2Show 2 read-only tools
  • get_public_reportReturns the latest public AI visibility report of a domain from QQQ (qqq.ee), when someone has already run the full check on qqq.ee: report date, market and field, in how many sear…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_public_report" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "return" and "chat": it reads messages.
    • untrusted-inputThe description's first sentence says "return" and "chat": it reads messages, which other people can write.
    Description, as the server wrote it
    Returns the latest public AI visibility report of a domain from QQQ (qqq.ee), when someone has already run the full check on qqq.ee: report date, market and field, in how many search-grounded ChatGPT, Gemini, Perplexity and Claude answers the company was named, how often its own website was cited, a summary per AI engine, the questions asked, the cited source domains and short answer excerpts, plus the link to the report page. Reads the stored report only: no website is fetched, no AI model is asked and no new report is created. Without a report, says so and links the full check on qqq.ee. Read-only, no limit.

    Annotations the server declares

    • title: Get the public AI visibility report of a domain
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_tool_infoDescribes the free QQQ AI Visibility Checker (qqq.ee): what it measures (brand mentions and website citations in ChatGPT, Gemini and Perplexity answers, AI crawler access, technica…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_tool_info" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "describe" and "chat": it reads messages.
    • untrusted-inputThe description's first sentence says "describe" and "mention": it reads comments, which other people can write.
    Description, as the server wrote it
    Describes the free QQQ AI Visibility Checker (qqq.ee): what it measures (brand mentions and website citations in ChatGPT, Gemini and Perplexity answers, AI crawler access, technical readiness for AI search / GEO), its limits, and the English and Estonian links to the web tool and full reports. No cost, no website is fetched.

    Annotations the server declares

    • title: About the QQQ AI Visibility Checker
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:53 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://qqq.ee/mcp: tools/list returned 3 tools to an anonymous client, including check_ai_visibility (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.2.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__ai-visibility__get_public_report",
      "mcp__ai-visibility__get_tool_info"
    ],
    "ask": [
      "mcp__ai-visibility__check_ai_visibility"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as ai-visibility. Review it before you use it.

Capability tags behind 3 rules
  • mcp__ai-visibility__check_ai_visibility untrusted-input
  • mcp__ai-visibility__get_public_report private-data, untrusted-input
  • mcp__ai-visibility__get_tool_info private-data, untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/ee.qqq/ai-visibility/verify?hash=4c135261d8c60ccd1503d679dbd8621604c3d1c892ab9759d7386f0b9fc889fe" | jq -e '.changed == false'

Pinned hash 4c135261d8c6, from Nov 18, 2026, 14:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/ee.qqq/ai-visibility/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for ee.qqq/ai-visibility
[![Anlyon Radar](https://radar.anlyon.com/badge/ee.qqq/ai-visibility.svg)](https://radar.anlyon.com/servers/ee.qqq/ai-visibility)

Source: MCP Registry · repository. Synced Nov 4, 2026, 20:17 UTC.

QQQ AI Visibility Checker MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the QQQ AI Visibility Checker MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the QQQ AI Visibility Checker MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the QQQ AI Visibility Checker MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the QQQ AI Visibility Checker MCP server have?

3 tools: 1 write, 2 read. check_ai_visibility, get_public_report and get_tool_info.

Does the QQQ AI Visibility Checker MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the QQQ AI Visibility Checker MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the QQQ AI Visibility Checker MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.