UX Arabia MCP server

• Registry nameai.xfix/xfixverified in the MCP registry

The registry name sits under xfix.ai. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-28
• Tools7
• Server calls itselfxfix
• Server version1.1.0
• Protocol version2025-06-18

On 2026-10-28 the server answered initialize and tools/list without a sign-in. First answer in 610 ms.

• Its tools do check whether Google and AI assistants can read a page, but not find revenue-losing steps in product, cart and checkout; check a government site against its national design standard.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP score81 of 100answers 100 · does the job 33 · definitions 100 · context 100 · connects 100
• What an agent can do with it1 of 3 use cases
• Answered100% of days7 of 7 daily checks
• Median first answer576 ms
• Space in an agent's context≈ 1,323 tokensthe definitions of all its tools (8), which an agent carries on every turn
• Tool definitionsA · 100 of 100
• Typed results8 of 8 toolsdeclared outputSchema: results come typed, read once

• Every tool passes all six checks.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• check_store_ai_readiness

  Checks whether AI assistants and shopping agents can read an online store. Fetches the public store pages the user names, without running JavaScript. Returns the store's AI Shopping Readiness Index score if the store is in the Index…

• check_ai_crawler_access

  Reads a site's robots.txt the way 9 crawlers do (Googlebot, Bingbot, Applebot, OAI-SearchBot, ChatGPT-User, Claude-SearchBot, Claude-User, PerplexityBot, Perplexity-User) and returns which may fetch the given page and the rule that blocks…

• check_page_readability

  Fetches the public page at the given URL without running JavaScript and reports whether its main text is present in the HTML. Checks one page only. Use when the user asks whether a page's content can be read without JavaScript.

• check_product_page

  Fetches one public product page without running JavaScript and reports whether the price and stock are in the HTML and which of six product structured data fields are present: price, availability, brand, identifier (gtin or sku), shipping…

• check_page_visibility

  Runs the xfix search check on one public page: fetches it without running JavaScript, checks robots.txt for 9 crawlers, measures mobile speed and reviews text, headings and title. Returns a score out of 100, a grade, coverage, any failed…

• get_page_visibility_result

  Returns the result of an xfix search check started earlier, or its progress if it is still running.

• lookup_index_score

  Looks up a store domain in the xfix AI Shopping Readiness Index and returns its published score and the fields shown on the public Index page, or says the store is not in the Index. Does not fetch the store.