QQQ AI Visibility Checker
REMOTE · QQQ.EE
Free AI visibility check: can AI crawlers read a site, and do ChatGPT, Gemini, Perplexity cite it?
Available components
Last scanned (7 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 25 Oct 2026.
Category Marketing and SEO
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 620 tokens (~206/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 17 Oct 26 70
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Oct 2026 · Probed https://qqq.ee/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=qqq.ee | CN=WE1,O=Google Trust Services,C=US | 29 Sept 2026 | 28 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 77ef5f608ce09eee0ebc58898d709916 |
| SANs: qqq.ee, www.qqq.ee, *.www.qqq.ee | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of qqq.ee. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ee. | present | 34382 | 8 | Verified |
| qqq.ee. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://qqq.ee/mcp | Verified | 200 | |
| http (plaintext) | http://qqq.ee/mcp | HTTPS enforced | 301 | https://qqq.ee/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_ai_visibility Check AI visibility of a website ~211
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Public website domain or URL, for example example.com or https://www.example.com/. IP addresses and private hosts are refused. |
| language | string | – | Language of the answer and of the qqq.ee links: en (English, default) or et (Estonian). |
No output schema declared.
No examples provided.
get_public_report Get the public AI visibility report of a domain ~201
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Website domain or URL, for example example.com or https://www.example.com/. |
| language | string | – | Language of the answer and of the qqq.ee links: en (English, default) or et (Estonian). |
No output schema declared.
No examples provided.
get_tool_info About the QQQ AI Visibility Checker ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Language of the answer and of the qqq.ee links: en (English, default) or et (Estonian). |
No output schema declared.
No examples provided.
How do I install the QQQ AI Visibility Checker MCP server?
QQQ AI Visibility Checker is a hosted endpoint at https://qqq.ee/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · qqq.ee
claude mcp add --transport http ee-qqq-ai-visibility 'https://qqq.ee/mcp'
What is the QQQ AI Visibility Checker MCP server?
QQQ AI Visibility Checker is an MCP server listed in the public MCP registry as ee.qqq/ai-visibility. Free AI visibility check: can AI crawlers read a site, and do ChatGPT, Gemini, Perplexity cite it? This page covers its hosted endpoint (https://qqq.ee/mcp).
Is the QQQ AI Visibility Checker MCP server safe to use?
QQQ AI Visibility Checker scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the QQQ AI Visibility Checker MCP server expose?
QQQ AI Visibility Checker exposes 3 tools: check_ai_visibility, get_public_report, get_tool_info. Their descriptions and schemas cost roughly 523 tokens of context every time the server is loaded.
Does the QQQ AI Visibility Checker MCP server require authentication?
No. We connected to QQQ AI Visibility Checker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the QQQ AI Visibility Checker MCP server still maintained?
QQQ AI Visibility Checker is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.