CueScout

io.github.telman03Published by GitHub account telman03v1.2.0Updated Oct 25, 2026

Check if ChatGPT or Perplexity names a brand for a buying question, and if AI bots can read a site.

VerifiedStreamable HTTPWeb executableDeveloper ToolsData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

CueScout checks whether AI answer engines name or cite a brand, audits a site's AI readiness, and reports tracked prompts, citations and to-dos.

What you can do
Check AI visibility: send a buying question to a search-grounded engine and see whether the brand was named or its domain cited, and which competitors appeared instead, or read visibility, share of voice and citation results already collected for a brand and its competitors. Audit a site for AI readiness: crawler access in robots.txt, llms.txt, structured data and JSON-LD, sitemap, canonical and meta tags, server-rendered copy, and about and pricing pages. Review tracked prompts with the latest verdict per engine, mention and citation rates, and the actual answers each engine gave. List the pages AI answers cite most in the brand's category, and read prioritized to-dos with steps and the Cue
When to use it
Useful for SEO, content and marketing work where the question is whether AI assistants recommend a brand for buying questions, why a site is not being cited, or which pages to target for mentions. Also fits when someone wants a quick audit of a site's AI crawler access and structured data.
Requirements
A remote streamable HTTP endpoint; no local runtime, package, environment variable or header is declared. Account tools such as get_profile, list_brands and the visibility and prompt tools act on a connected CueScout account, so a CueScout account is implied. Network access to the endpoint and to the audited sites is needed.
Before you install
The account tools read the connected CueScout account's brands, prompts, answers and audit results, and get_profile returns the account name and email. check_ai_visibility sends a question to an external search-grounded engine through its API, so the question text leaves the assistant. Audit tools fetch the target site's robots.txt, sitemap and pages. Results are CueScout's stored data and may be stale; get_site_audit does not re-run the audit.

Installation

In SourceWeft

  1. Open CueScout in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.telman03%2Fcuescout/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "cuescout": {
      "type": "http",
      "url": "https://mcp.cuescout.com/mcp"
    }
  }
}

Tools

14

check_ai_visibility

Check whether an AI engine recommends a brand

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.

Parametersbrandrequireddomainenginequestionrequiredcompetitors

check_ai_readiness

Check whether AI engines can read a site

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.

Parametersurlrequired

check_ai_crawler_access

Check whether AI crawlers are blocked in robots.txt

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.

Parametersurlrequired

validate_structured_data

Validate the JSON-LD on a page

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.

Parametersurlrequired

check_sitemap

Check whether a crawler gets a usable page list

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.

Parametersurlrequired

get_profile

Show the connected CueScout account

Use this when someone asks which CueScout account is connected. Returns the account name and email.

Takes no parameters.

list_brands

List the brands in the CueScout account

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.

Takes no parameters.

get_ai_visibility

Show AI visibility for a tracked brand

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.

Parametersdaysbrand

list_prompts

List the tracked prompts and how each engine answered

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.

Parametersdaysbrand

get_prompt_answers

Show the latest AI answers to one tracked prompt

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.

Parametersbrandprompt_idrequired

list_citation_sources

List the pages AI answers cite for a brand

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.

Parametersdaysbrandlimit

list_todos

List the brand's To-dos

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.

Parametersbrandstatus

get_todo

Show one To-do with its steps and evidence

Use this when someone wants the details of one To-do: why it matters, the steps to do it, and the evidence behind it.

Parametersbrandtodo_idrequired

get_site_audit

Show the brand's 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.

Parametersbrand

Version history

1
  1. v1.2.0LatestOct 14, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.