AI Recommendation Check MCP server
com.uxcontinuum/ai-recommendation-checkuxcontinuum.comstreamable-httpv1.0.0Scanned
Does ChatGPT recommend a local business? Live AI-engine check plus who gets named instead.
2 tools: 1 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the AI Recommendation Check MCP server can do
The AI Recommendation Check MCP server is published by uxcontinuum.com, a domain the MCP Registry verified. It has 2 tools. It can create or change data (1 tool: check_ai_recommendation), but cannot delete data. 1 tool only reads.
1 tool brings in text other people can write (check_ai_recommendation).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 14, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
2 tools
Changes things 1Claude Code: ask
check_ai_recommendationUse 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 recommend…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: true
- idempotentHint: true
Only reads 1Show 1 read-only tool
get_ai_recommendation_resultUse this to read the result of a check started with check_ai_recommendation, using the check_id it returned.No findings
Why it is in this group
- The name "get_ai_recommendation_result" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:49 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://uxcontinuum.com/api/plugin/mcp: tools/list returned 2 tools to an anonymous client, including check_ai_recommendation (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http ai-recommendation-check https://uxcontinuum.com/api/plugin/mcpclaude mcp add --transport http ai-recommendation-check https://uxcontinuum.com/api/plugin/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__ai-recommendation-check__get_ai_recommendation_result"
],
"ask": [
"mcp__ai-recommendation-check__check_ai_recommendation"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as ai-recommendation-check. Review it before you use it.
Capability tags behind 1 rule
- mcp__ai-recommendation-check__check_ai_recommendation untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.uxcontinuum/ai-recommendation-check/verify?hash=8f372c72455221f555135f18685c3311fc244f36f85d6922a099238e2ea332fb" | jq -e '.changed == false'Pinned hash 8f372c724552, from Nov 14, 2026, 17:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.uxcontinuum/ai-recommendation-check/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.uxcontinuum/ai-recommendation-check)Source: MCP Registry. Synced Oct 21, 2026, 18:10 UTC.
AI Recommendation Check MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the AI Recommendation Check MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the AI Recommendation Check MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the AI Recommendation Check MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the AI Recommendation Check MCP server have?
- 2 tools: 1 write, 1 read. check_ai_recommendation and get_ai_recommendation_result.
Does the AI Recommendation Check MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the AI Recommendation Check MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the AI Recommendation Check MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 14, 2026.