AI Recommendation Check
REMOTE · UXCONTINUUM.COM
Does ChatGPT recommend a local business? Live AI-engine check plus who gets named instead.
Available components
Last scanned (21 hours ago)
Scores higher than 94% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Marketing and SEO
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 734 tokens (~244/item across 3 items; 2 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://uxcontinuum.com/api/plugin/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=uxcontinuum.com | CN=YR1,O=Let's Encrypt,C=US | 1 Oct 2026 | 30 Dec 2026 | RSA 2048 | SHA256-RSA | 6be02fc808838c52d79634d0a3f2d177c9a |
| SANs: uxcontinuum.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of uxcontinuum.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| uxcontinuum.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://uxcontinuum.com/api/plugin/mcp | Verified | 200 | |
| http (plaintext) | http://uxcontinuum.com/api/plugin/mcp | HTTPS enforced | 308 | https://uxcontinuum.com/api/plugin/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_ai_recommendation Check if AI recommends a business ~448
Use this when a business owner asks whether ChatGPT or AI recommends their business, whether AI tools like ChatGPT or Perplexity mention or suggest their business, why AI recommends their competitors instead, or how to get their business recommended by AI. It runs a real check: it asks ChatGPT, Perplexity and Gemini up to 3 questions a customer would ask when looking for this kind of business in the area the business serves, and reports whether each engine named the business, which businesses they named instead, and one fix based on the pages the answers cited. Timing: a check usually finishes in under a minute. This tool waits up to about 20 seconds and returns the result when it is ready; otherwise it returns a check_id with the status queued or running, and get_ai_recommendation_result returns the result for that check_id. A saved result for the same business is returned right away. Business details are sent to Continuum (uxcontinuum.com) to run the check. Results are shown in the conversation. Not covered: general SEO or Google ranking questions, writing marketing copy or ads, looking up or checking a person (it checks businesses only), and general questions about how AI search works. Limits: 3 buyer questions per website per day; saved results are reused for 7 days.
| Name | Type | Req | Description |
|---|---|---|---|
| business_name | string | yes | The business name as customers know it, for example "Joe's Plumbing". |
| category | string | yes | What the business is, in the words a customer would use to look for one, for example "plumber", "wedding photographer" or "HVAC company". Not a slogan. |
| string | – | Optional. The owner's email address, if they want Continuum to send this result and follow up. | |
| service_area | string | – | The area the business serves, as its customers would name it, for example "Austin, TX". This describes the business, not the user's own location. Empty when the business serves customers anywhere onl… |
| website | string | yes | The business website, for example "joesplumbing.com". Used to recognise the business in answers and to keep its daily limit. |
No output schema declared.
No examples provided.
get_ai_recommendation_result Get the AI recommendation check result ~145
Use this to read the result of a check started with check_ai_recommendation, using the check_id it returned. Returns the status (queued, running, done, failed or refused). When done: for ChatGPT, Perplexity and Gemini, how many of their answers named the business, which businesses they named instead, and one fix. While a check is queued or running, poll_after_s is the suggested wait in seconds before reading it again. It waits up to about 20 seconds for a running check to finish. It does not start a new check.
| Name | Type | Req | Description |
|---|---|---|---|
| check_id | string | yes | The check_id returned by check_ai_recommendation. |
No output schema declared.
No examples provided.
How do I install the AI Recommendation Check MCP server?
AI Recommendation Check is a hosted endpoint at https://uxcontinuum.com/api/plugin/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.
remote · uxcontinuum.com
claude mcp add --transport http com-uxcontinuum-ai-recommendation-check 'https://uxcontinuum.com/api/plugin/mcp'
What is the AI Recommendation Check MCP server?
AI Recommendation Check is an MCP server listed in the public MCP registry as com.uxcontinuum/ai-recommendation-check. Does ChatGPT recommend a local business? Live AI-engine check plus who gets named instead. This page covers its hosted endpoint (https://uxcontinuum.com/api/plugin/mcp).
Is the AI Recommendation Check MCP server safe to use?
AI Recommendation Check scores 87 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 AI Recommendation Check MCP server expose?
AI Recommendation Check exposes 2 tools: check_ai_recommendation, get_ai_recommendation_result. Their descriptions and schemas cost roughly 593 tokens of context every time the server is loaded.
Does the AI Recommendation Check MCP server require authentication?
No. We connected to AI Recommendation Check without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AI Recommendation Check MCP server still maintained?
AI Recommendation Check is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.