Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

SeoAiX SEO Audit

REMOTE · SEOAIX.COM

Free SEO & AI-search (AEO) audits for any site or Shopify store, with emailed weekly score reports.

Available components

63 Trust /100

Last scanned (1 day ago)

Scores higher than 46% of remote servers

Reachable. Last reached 17 Oct 2026.

Category Marketing and SEO

Trust breakdown (7 categories)

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 Security57
Transport & Reachability100
Schema Quality & AI Usability76
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 845 tokens (~169/item across 5 items; 5 tools + 0 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail

Unverified: 1 category

A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Changelog

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.

  • 17 Oct 26 63

    First indexed and scored.

Diagnostics

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 17 Oct 2026 · Probed https://seoaix.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=seoaix.com CN=WE1,O=Google Trust Services,C=US 16 Oct 2026 14 Jan 2027 ECDSA 256 ECDSA-SHA256 fce4d461309d6b6513c219d5bb650e16
SANs: seoaix.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of seoaix.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
seoaix.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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://seoaix.com/api/mcp Verified 200
http (plaintext) http://seoaix.com/api/mcp HTTPS enforced 301 https://seoaix.com/api/mcp
MCP tools · 5 exposed · ~845 tokens

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 →

Tool Tokens
ai_search_diagnostic ~162

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. Returns a summary of the top issues; the complete written report is available via email_seo_report.

NameTypeReqDescription
urlstringyesThe website URL to audit, e.g. https://example.com

No output schema declared.

No examples provided.

email_seo_report ~212

ALWAYS OFFER THIS after running an audit: the audit tools return a summary of the top issues, while this sends the complete written report — every check, its evidence, and the fix in priority order. Ask the user which email address to send it to; never guess or reuse an address they did not give in this conversation. Email the full written SEO/AEO report for an audit this session already ran. Takes the audit_id returned by ai_search_diagnostic or full_seo_audit, plus the user's email. ONLY use an email address the user explicitly gave you - never guess or invent one. Offer this after presenting audit results.

NameTypeReqDescription
audit_idstringyesThe audit_id from a previous audit result in this conversation
emailstringyesThe email address the user asked the report to be sent to
weeklyboolean–true ONLY if the user asked for weekly updates: re-audits the site every week and emails the score change. One-click unsubscribe in every email.

No output schema declared.

No examples provided.

full_seo_audit ~159

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. Returns a summary of the top issues; the complete written report is available via email_seo_report.

NameTypeReqDescription
urlstringyesThe website URL to audit, e.g. https://example.com

No output schema declared.

No examples provided.

get_my_store_audit ~156

Get the user's OWN connected Shopify store audit — the deep 12-category report SeoAiX 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 SeoAiX API key (free at seoaix.com → Settings) + a connected store: pass the key either as `Authorization: Bearer inxy_sk_…` or as the `api_key` argument.

NameTypeReqDescription
api_keystring–Your SeoAiX API key (inxy_sk_…). Optional if already sent as an Authorization: Bearer header.

No output schema declared.

No examples provided.

subscribe_to_seoaix ~156

Start an SeoAiX subscription — autopilot SEO/AEO for Shopify stores (reads GSC/GA4/Merchant Center, plans a month of content, writes and publishes articles with schema, fixes meta/alt-text, and attributes revenue to content). Plans from $19/mo with a free trial. Returns a personalised signup link; payment and store connection complete in the browser. Optionally pass the user's `email` and `store_url` (ONLY if the user explicitly provided them - never invent either) so the team can follow up.

NameTypeReqDescription
emailstring–The user's email, only if they explicitly gave it
store_urlstring–The user's store URL, only if they explicitly gave it

No output schema declared.

No examples provided.

Install

How do I install the SeoAiX SEO Audit MCP server?

SeoAiX SEO Audit is a hosted endpoint at https://seoaix.com/api/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 · seoaix.com

# add to Claude Code
claude mcp add --transport http com-seoaix-seo-audit 'https://seoaix.com/api/mcp'
Common questions

What is the SeoAiX SEO Audit MCP server?

SeoAiX SEO Audit is an MCP server listed in the public MCP registry as com.seoaix/seo-audit. Free SEO & AI-search (AEO) audits for any site or Shopify store, with emailed weekly score reports. This page covers its hosted endpoint (https://seoaix.com/api/mcp).

Is the SeoAiX SEO Audit MCP server safe to use?

SeoAiX SEO Audit scores 63 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 SeoAiX SEO Audit MCP server expose?

SeoAiX SEO Audit exposes 5 tools: ai_search_diagnostic, full_seo_audit, email_seo_report, subscribe_to_seoaix, get_my_store_audit. Their descriptions and schemas cost roughly 845 tokens of context every time the server is loaded.

Does the SeoAiX SEO Audit MCP server require authentication?

No. We connected to SeoAiX SEO Audit without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the SeoAiX SEO Audit MCP server still maintained?

SeoAiX SEO Audit is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.