Remote MCP · Endpoint

CueScout MCP server

No. CueScout answered an MCP handshake 13 minutes ago.

UpLast checked 13 minutes ago

Server URL

https://mcp.cuescout.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.telman03/cuescout
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
376 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Check if ChatGPT or Perplexity names a brand for a buying question, and if AI bots can read a site.
Listing
From the official MCP registry (active).
Recent checks of CueScout
CheckedResultHandshake
13 minutes agoHandshake completed376 ms
10 days agoHandshake completed338 ms
10 days agoHandshake completed333 ms
11 days agoHandshake completed334 ms
13 days agoHandshake completed356 ms
14 days agoHandshake completed337 ms
14 days agoHandshake completed343 ms
15 days agoHandshake completed540 ms
17 days agoHandshake completed359 ms
19 days agoHandshake completed332 ms
21 days agoHandshake completed340 ms
24 days agoHandshake completed361 ms
26 days agoHandshake completed331 ms
28 days agoHandshake completed335 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 16 responding of 16.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with CueScout and makes no claim about it beyond what these checks measured.