CueScout is answering right now. Last checked 3 min ago. It exposes 14 tools.
Check if ChatGPT or Perplexity names a brand for a buying question, and if AI bots can read a site.
Uptime history
12 days of history
12 days agonow
100.0%
Uptime 24h
92 of 92 checks
14
Tools
read from the server
118 ms
Response time
average over 24h
open, no key
Access
streamable-http
What changed 4
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 15 October 2026. No other catalogue keeps this.
15 Oct
4 tool descriptions were rewritten
check_ai_readiness, get_prompt_answers, get_site_audit and 1 more
Nothing serious here today
Today is the operative word: we check CueScout every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.
run in your terminal
claude mcp add cuescout --transport http https://mcp.cuescout.com/mcpSettings → Connectors → Add custom connector, then paste this address
https://mcp.cuescout.com/mcp~/.codex/config.toml
[mcp_servers.cuescout]
url = "https://mcp.cuescout.com/mcp".cursor/mcp.json
{
"mcpServers": {
"cuescout": {
"url": "https://mcp.cuescout.com/mcp"
}
}
}.vscode/mcp.json
{
"servers": {
"cuescout": {
"type": "http",
"url": "https://mcp.cuescout.com/mcp"
}
}
}Available tools 14
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
visibility
check_ai_visibility
Use this when someone asks whether an AI answer engine names or cites a brand for a buying question, or which other brands it names. Sends one question to one search-grounded engine through its API and returns whether the brand was named, whether its domain was cited, which of the listed competitors were named, and the pages the answer cited. Each call is a fresh API request with no account history or personalization, and one question is one datapoint, not an overall visibility score.
get_ai_visibility
Use this when someone asks how visible their brand is in AI answers, what their share of AI voice is, or how they compare with competitors. Reads the results CueScout already collected for the brand: how often AI answers named it, its share of voice, how often its site was cited, and the same for each competitor, over the last 7, 28 or 90 days. It does not run new checks.
brands
list_brands
Use this to see which brands the connected CueScout account tracks, with their sites and the competitors set for each. The other account tools take one of these brands.
citation
list_citation_sources
Use this when someone asks which websites or pages AI answers rely on in their brand's category, or where they should try to get mentioned. Returns the pages cited most often across the brand's tracked prompts, with how many times each was cited, by which engines, and which brands each page names.
crawler
check_ai_crawler_access
Use this when someone asks why their site never shows up in AI answers, or whether GPTBot, ClaudeBot, PerplexityBot or Google-Extended can crawl it. Reads the site's robots.txt and reports which of those crawlers are blocked, including by a blanket rule the owner may not have meant. One fetch, no AI.
profile
get_profile
Use this when someone asks which CueScout account is connected. Returns the account name and email.
prompt
get_prompt_answers
Use this when someone wants to read what the AI engines actually answered to one of their tracked prompts. Returns the most recent answer from each engine, whether the brand was named or cited, which brands were named, and the pages each answer cited.
prompts
list_prompts
Use this when someone asks which questions CueScout tracks for their brand, which ones the brand is missing from, or who gets named instead. Returns each tracked prompt with the latest verdict per engine (named and cited, named, or not named), the brand's mention and citation rate over the window, and the brands named instead.
readiness
check_ai_readiness
Use this when someone asks whether AI engines can read, crawl or quote their website, or wants an AI-readiness audit of a site. Runs eight checks: AI crawler access in robots.txt, llms.txt, Organization and FAQ schema, canonical and meta tags, server-rendered copy, and whether an about page and a pricing page exist. It does not measure whether any engine actually cites the site. No AI call, nothing stored.
site
get_site_audit
Use this when someone asks whether AI engines can read their own brand's site, based on CueScout's last audit of it: crawler access, llms.txt, schema, meta tags, server-rendered copy, and about and pricing pages. Reads the stored result; it does not re-run the audit.
sitemap
check_sitemap
Use this when someone wants their XML sitemap checked. Reports whether a site's sitemap is reachable, parses, is declared in robots.txt, and is free of cross-host entries a crawler discards. A handful of fetches, no AI.
todo
get_todo
Use this when someone wants the details of one To-do: why it matters, the steps to do it, and the evidence behind it.
todos
list_todos
Use this when someone asks what they should do next to show up in AI answers. Returns CueScout's To-dos for the brand in priority order: the action, why it matters and its priority. Filter by status: todo (default), suggested, done or dismissed.
validate
validate_structured_data
Use this when someone wants their schema markup or JSON-LD checked on a specific page. Reports which schema types the page declares, which blocks fail to parse, and whether the fields that help an engine attribute a claim (sameAs, Organization identity, FAQ answers) are filled in. One fetch, no AI.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://mcp.cuescout.com/mcp | streamable-http | answering | 118 ms | 3 min ago |
Alternatives to CueScout
same job, measured the same wayAgentwatch
by comiza
Check if ChatGPT, Claude and Perplexity can reach, read and quote a website.
AI Brand Visibility Tracker
by cookient16
Check if ChatGPT, Perplexity & Gemini mention or cite a brand. Share of voice + GEO/AEO tracking.
QQQ AI Visibility Checker
by qqq
Free AI visibility check: can AI crawlers read a site, and do ChatGPT, Gemini, Perplexity cite it?
Rankli: AI search readiness
by rankli-www
Checks if ChatGPT, Claude, Gemini and Perplexity can reach and read a website, with ranked fixes.
TraceFlow Lens
by traceflowlabs-lens
SEO and GEO audit: check if a site can be read and cited by Google, ChatGPT, Perplexity and Claude.
A
Agentready
by puluceno
Can ChatGPT, Claude and Perplexity reach and read a website? Score, problems found and fixes.
Firemark AI
by tryfiremark
Read how often ChatGPT, Perplexity, Gemini and Google AI name your brand, its rivals and sources.
AI Readiness
by epistemedeus
Check if a website is visible to AI search (ChatGPT, Perplexity, Claude) and get per-gap fixes.
CueScout — questions
Answers built from our own checks of this server.
What can CueScout do?
It exposes 14 tools, read directly from the server on our last check. Among them: check_ai_crawler_access, check_ai_readiness, check_ai_visibility, check_sitemap, get_ai_visibility, get_profile and 8 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
Is CueScout working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 118 ms. The bar chart above shows every period we have measured.
How do I connect CueScout?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does CueScout need an API key?
No. CueScout completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 14 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is CueScout?
It answers our handshake in 118 ms on average, which is faster than 94% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.