ZBS Index What actually exists in applied AI, with the source next to it

mcp server

seo-audit

Score any site or Shopify store for AEO/GEO/LLMO readiness — how likely AI search is to cite it.

Description as published by the maintainer. Source

  • version 1.3.2
  • active
  • retrieval

active — Most recent push to the repository was 2026-06-14. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.

What this server can do

3 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.

ai_search_diagnostic(url)
Audit ANY URL for AI-search readiness only (AEO/GEO/LLMO) — how likely ChatGPT, Claude, Perplexity & Google AI are to cite it. Checks ~7 AI-citation signals (FAQ/structured-data/entity schema, citable stats, llms.txt, author/E-E-A-T, OG). Returns a weighted 0–100 AI-readiness score + top fixes. Takes a `url`. Use full_seo_audit for the broader SEO picture, or get_my_store_audit for the user's own connected store. Required: url.
full_seo_audit(url)
Crawl-audit ANY URL across the WHOLE SEO surface (no login needed): the AI-search signals PLUS on-page SEO (title/meta/headings/content), technical SEO (HTTPS, robots.txt, XML sitemap, canonical, mobile), and — for Shopify stores — product/offer/review/breadcrumb schema and image-alt coverage. Returns a weighted 0–100 score + top issues. Takes a `url`. This audits an arbitrary website by crawling it — for the user's OWN connected store with real analytics, use get_my_store_audit. Required: url.
get_my_store_audit(api_key)
Get the user's OWN connected Shopify store audit — the deep 12-category report Inxy runs INSIDE the app using the store's real catalog, performance and analytics (technical, performance, on-page, schema, AEO, analytics, e-commerce, etc.) — far beyond what crawling a URL can see. Takes no url. Needs an Inxy API key (free at inxy.ai → Settings) + a connected store: pass the key either as `Authorization: Bearer inxy_sk_…` or as the `api_key` argument.

Last successful function declaration observed on . Source: https://inxy.ai/api/mcp. We list what the server declared; we do not call any of these functions.

Endpoint status observed on . Source: https://inxy.ai/api/mcp.

Signals

These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.

Signal Value What it measures Window Observed Source
GitHub stars 0 Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. cumulative, all time GitHub
Last commit 2026-06-14 Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. point in time GitHub
Open issues 0 Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. as of fetch GitHub
Latest published version 1.3.2 Latest version string the maintainer published to the registry. as of fetch Model Context Protocol
Registry record last updated 2026-06-14 When the registry record was last updated by its maintainer. point in time Model Context Protocol
First listed in the MCP Registry 2026-06-14 Date this server was first published to the official MCP Registry. Not a usage or quality measure. point in time Model Context Protocol
repository status active The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. as of fetch GitHub
mcp tools declared 3 tools Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. as of probe inxy.ai
mcp endpoint status ok The server listed 3 functions when asked. as of probe inxy.ai

Where to get it

Also from riverliu8

This record as data

Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.

GET /api/v1/entries/mcp_server.json

Sources

  1. riverliu8/inxy-mcp on GitHub — GitHub, observed , trust tier 3.
  2. Tools declared by the MCP server at https://inxy.ai/api/mcp — inxy.ai, observed , trust tier 1.
  3. Official MCP Registry — Model Context Protocol, observed , trust tier 1.