# CueScout (remote · mcp.cuescout.com)

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

- Trust score: 75/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `mcp.cuescout.com`: 75/100 (this document), [markdown](https://verifymcp.io/servers/telman03-cuescout/mcp.md), [page](https://verifymcp.io/servers/telman03-cuescout/mcp)

## Channel facts

- Endpoint: `https://mcp.cuescout.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-17.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 87/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1705 tokens (~94/item across 18 items; 14 tools + 4 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 96% of tool parameters carry a description.
  - Structured output schemas are declared (21% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the CueScout MCP server?

CueScout is a hosted endpoint at https://mcp.cuescout.com/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.

### Claude

```bash
claude mcp add --transport http telman03-cuescout 'https://mcp.cuescout.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "telman03-cuescout": {
      "url": "https://mcp.cuescout.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "telman03-cuescout": {
      "type": "http",
      "url": "https://mcp.cuescout.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.telman03-cuescout]
url = "https://mcp.cuescout.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "telman03-cuescout": {
      "type": "remote",
      "url": "https://mcp.cuescout.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add telman03-cuescout --url 'https://mcp.cuescout.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  telman03-cuescout:
    url: "https://mcp.cuescout.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "telman03-cuescout": {
      "Transport": "http",
      "Url": "https://mcp.cuescout.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add telman03-cuescout -t streamable-http -u 'https://mcp.cuescout.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "telman03-cuescout": {
      "type": "http",
      "url": "https://mcp.cuescout.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-17 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-16 (score 74, 0)

- [security] Tool “check_ai_readiness” rewrote its description, which is the text the model reads
- [security] Tool “get_prompt_answers” rewrote its description, which is the text the model reads
- [security] Tool “get_site_audit” rewrote its description, which is the text the model reads
- [security] Tool “get_todo” rewrote its description, which is the text the model reads

### 2026-10-15 (score 74, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-14 (score 73)

First indexed and scored.

## MCP tools (14)

### `check_ai_visibility` (~222 tokens)

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.

Input parameters:

- `brand` (string, required): The brand or product name to look for in the answer.
- `competitors` (array): Up to 3 competitor names to check for in the same answer.
- `domain` (string): The brand's domain. Supplying it enables citation detection, not just name matching.
- `engine` (string): Which engine answers: perplexity (the default) or chatgpt.
- `question` (string, required): A question a buyer would actually type, e.g. "best tool for tracking AI search visibility". Not a keyword: the engines answer questions.

Output parameters:

- `brand` (string)
- `cited` (boolean)
- `competitors` (array)
- `engine` (string)
- `mentioned` (boolean)
- `question` (string)
- `rank` (number|null)
- `sentiment` (string|null)
- `snippet` (string|null)
- `sources` (array)

### `check_ai_readiness` (~121 tokens)

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.

Input parameters:

- `url` (string, required): The site or page URL to check. A bare domain like example.com is fine.

### `check_ai_crawler_access` (~102 tokens)

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.

Input parameters:

- `url` (string, required): The site or page URL to check. A bare domain like example.com is fine.

### `validate_structured_data` (~96 tokens)

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.

Input parameters:

- `url` (string, required): The site or page URL to check. A bare domain like example.com is fine.

### `check_sitemap` (~79 tokens)

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.

Input parameters:

- `url` (string, required): The site or page URL to check. A bare domain like example.com is fine.

### `get_profile` (~27 tokens)

Show the connected CueScout account

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

Output parameters:

- `email` (string)
- `id` (string)
- `name` (string)

### `list_brands` (~42 tokens)

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.

### `get_ai_visibility` (~152 tokens)

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.

Input parameters:

- `brand` (string): Which brand, by name or id, when the account tracks more than one. Leave empty to use the only brand; list_brands shows them all.
- `days` (number): The window to report on, in days. Defaults to 28.

Output parameters:

- `answers` (number)
- `app_url` (string)
- `brand` (string)
- `brand_id` (string)
- `days` (number)
- `engines` (array)
- `low_sample` (boolean)
- `questions` (number)
- `rankings` (array)

### `list_prompts` (~132 tokens)

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.

Input parameters:

- `brand` (string): Which brand, by name or id, when the account tracks more than one. Leave empty to use the only brand; list_brands shows them all.
- `days` (number): The window to report on, in days. Defaults to 28.

### `get_prompt_answers` (~111 tokens)

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.

Input parameters:

- `brand` (string): Which brand, by name or id, when the account tracks more than one. Leave empty to use the only brand; list_brands shows them all.
- `prompt_id` (string, required): The prompt id, from list_prompts.

### `list_citation_sources` (~144 tokens)

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.

Input parameters:

- `brand` (string): Which brand, by name or id, when the account tracks more than one. Leave empty to use the only brand; list_brands shows them all.
- `days` (number): The window to report on, in days. Defaults to 28.
- `limit` (integer): How many pages to return. Defaults to 15.

### `list_todos` (~108 tokens)

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.

Input parameters:

- `brand` (string): Which brand, by name or id, when the account tracks more than one. Leave empty to use the only brand; list_brands shows them all.
- `status` (string)

### `get_todo` (~91 tokens)

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.

Input parameters:

- `brand` (string): Which brand, by name or id, when the account tracks more than one. Leave empty to use the only brand; list_brands shows them all.
- `todo_id` (string, required): The To-do id, from list_todos.

### `get_site_audit` (~109 tokens)

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.

Input parameters:

- `brand` (string): Which brand, by name or id, when the account tracks more than one. Leave empty to use the only brand; list_brands shows them all.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/telman03-cuescout/mcp#diagnostics

## Score history

- 2026-10-17: 75
- 2026-10-16: 74
- 2026-10-15: 74
- 2026-10-14: 73

## Common questions

### What is the CueScout MCP server?

CueScout is an MCP server listed in the public MCP registry as io.github.telman03/cuescout. Check if ChatGPT or Perplexity names a brand for a buying question, and if AI bots can read a site. This page covers its hosted endpoint (https://mcp.cuescout.com/mcp).

### Is the CueScout MCP server safe to use?

CueScout scores 75 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 CueScout MCP server expose?

CueScout exposes 14 tools: check_ai_visibility, check_ai_readiness, check_ai_crawler_access, validate_structured_data, check_sitemap, and 9 more. Their descriptions and schemas cost roughly 1,536 tokens of context every time the server is loaded.

### Does the CueScout MCP server require authentication?

No. We connected to CueScout without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the CueScout MCP server still maintained?

CueScout is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.cuescout.com/mcp
- Website: https://cuescout.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/telman03-cuescout/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/telman03-cuescout/mcp.json
- HTML version of this page: https://verifymcp.io/servers/telman03-cuescout/mcp