Remote MCP · Endpoint

AI Recommendation Check MCP server

No. AI Recommendation Check answered an MCP handshake 55 minutes ago.

UpLast checked 55 minutes ago

Server URL

https://uxcontinuum.com/api/plugin/mcp

The last check completed an MCP handshake.

Registry name
com.uxcontinuum/ai-recommendation-check
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
162 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Does ChatGPT recommend a local business? Live AI-engine check plus who gets named instead.
Listing
From the official MCP registry (active).
Recent checks of AI Recommendation Check
CheckedResultHandshake
55 minutes agoHandshake completed162 ms
1 day agoHandshake completed142 ms
4 days agoHandshake completed128 ms
7 days agoHandshake completed137 ms
9 days agoHandshake completed131 ms
11 days agoHandshake completed155 ms
13 days agoHandshake completed222 ms
15 days agoHandshake completed94 ms
17 days agoHandshake completed206 ms
19 days agoHandshake completed124 ms
21 days agoHandshake completed99 ms
22 days agoHandshake completed137 ms
23 days agoHandshake completed173 ms
24 days agoHandshake completed122 ms

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

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 AI Recommendation Check and makes no claim about it beyond what these checks measured.