Skip to content

SeoAiX SEO Audit MCP server

com.seoaix/seo-auditseoaix.comstreamable-httpv1.6.0Scanned

Free SEO & AI-search audits, an llms.txt generator, and store tools to review and approve fixes.

12 tools: 1 do something that can't be undone, 5 change things and 6 only read.

Tools: 0 delete, 1 irreversible, 5 write, 6 read.
  • Reads private data · 2
  • Reads text others write · 3
  • Can send data out · 4
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

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 SeoAiX SEO Audit MCP server can do

The SeoAiX SEO Audit MCP server is published by seoaix.com, a domain the MCP Registry verified. It has 12 tools. It can do things that cannot be undone, such as sending, paying or publishing (publish_draft) and create or change data (5 tools: full_seo_audit, generate_llms_txt, email_seo_report, subscribe_to_seoaix and 1 more), but cannot delete data. 6 tools only read.

2 tools read private data (ai_search_diagnostic and get_store_status); 3 tools bring in text other people can write (ai_search_diagnostic, full_seo_audit and get_my_store_audit); 4 tools can send data out of your system (ai_search_diagnostic, full_seo_audit, generate_llms_txt and 1 more). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

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, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 18, 2026, version 1.6.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.

12 tools

Can't be undone 1Claude Code: ask
  • publish_draftPublish ONE ready article draft live on the user's own store (its Shopify blog, or the SeoAiX-hosted blog for a software site) (ids from list_pending_approvals).Can send data outNo findings

    Why it is in this group

    • The name "publish_draft" says "publish": a word for a change that another call does not undo.

    What it can reach

    • outboundThe name "publish_draft" says "publish": it sends or publishes something to other people.
    Description, as the server wrote it
    Publish ONE ready article draft live on the user's own store (its Shopify blog, or the SeoAiX-hosted blog for a software site) (ids from list_pending_approvals). Takes TWO calls. Call it first WITHOUT confirmToken: nothing changes, and you get a preview plus a confirmToken (valid 10 minutes, single use). Show the preview to the user and ask them. Only if they clearly say yes, call again with the same arguments plus that confirmToken. Never confirm on your own judgement, and never loop over many items. Needs a key with the "approve" permission.
Changes things 5Claude Code: ask
  • decide_recommendationApprove or reject ONE pending SeoAiX recommendation for the user's own store (ids from list_pending_approvals).No findings

    Why it is in this group

    • The description's first verb is "approve": a word for a change.
    Description, as the server wrote it
    Approve or reject ONE pending SeoAiX recommendation for the user's own store (ids from list_pending_approvals). Approving can change the live store. Takes TWO calls. Call it first WITHOUT confirmToken: nothing changes, and you get a preview plus a confirmToken (valid 10 minutes, single use). Show the preview to the user and ask them. Only if they clearly say yes, call again with the same arguments plus that confirmToken. Never confirm on your own judgement, and never loop over many items. Needs a key with the "approve" permission.
  • email_seo_reportALWAYS 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 …No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • full_seo_auditCrawl-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 site…Reads text others writeCan send data outNo 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 description's first sentence says "crawl": it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.
  • generate_llms_txtGenerate an llms.txt file (llmstxt.org format) for ANY website, no login needed.Can send data outNo findings

    Why it is in this group

    • The name "generate_llms_txt" says "generate": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Generate an llms.txt file (llmstxt.org format) for ANY website, no login needed. Reads the home page, robots.txt, the XML sitemap and a sample of key pages (pricing, about, docs, products…), then returns a ready-to-publish llms.txt: `# Site name`, a one-line summary, and `## Section` link lists with page descriptions. Also reports whether the site already serves a real /llms.txt. Takes a `url`. Built from the site's own titles and meta descriptions (no AI rewriting) — review before publishing at the site root as /llms.txt.
  • subscribe_to_seoaixStart 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/…No findings

    Why it is in this group

    • The name "subscribe_to_seoaix" says "subscribe": a word for a change.
    Description, as the server wrote it
    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.
Only reads 6Show 6 read-only tools
  • ai_search_diagnosticAudit ANY URL for AI-search readiness only (AEO/GEO/LLMO) — how likely ChatGPT, Claude, Perplexity & Google AI are to cite it.Reads private dataReads text others writeCan send data outNo findings

    Why it is in this group

    • The name "ai_search_diagnostic" says "search": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "chat": it reads messages.
    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
    • untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Claude Code: ask, because it is tagged outbound.

    Description, as the server wrote it
    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.
  • get_my_store_auditGet 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, perf…Reads text others writeNo findings

    Why it is in this group

    • The name "get_my_store_audit" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "get" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.
  • get_recent_changesWhat moved for the user's own store over the last 7 or 28 days versus the period before: store audit score, Search Console clicks/impressions and keyword positions, GA4 sessions wi…No findings

    Why it is in this group

    • The name "get_recent_changes" says "get": a word for reading.
    Description, as the server wrote it
    What moved for the user's own store over the last 7 or 28 days versus the period before: store audit score, Search Console clicks/impressions and keyword positions, GA4 sessions with top rising/falling pages, Merchant Center clicks. Optional `days` (7 or 28, default 7).
  • get_store_statusWhat is going on with the user's OWN connected SeoAiX store right now: Search Console / GA4 / Merchant Center connection and sync state, content plan, indexing coverage, items wait…Reads private dataNo findings

    Why it is in this group

    • The name "get_store_status" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "note": it reads notes.
    Description, as the server wrote it
    What is going on with the user's OWN connected SeoAiX store right now: Search Console / GA4 / Merchant Center connection and sync state, content plan, indexing coverage, items waiting on the merchant, and notes explaining anything that looks wrong. Needs a store-bound SeoAiX API key.
  • get_weekly_reportThis week's SeoAiX report for the user's own store: headline traffic, revenue and keyword changes, what SeoAiX did, a short narrative, and this week's priorities.No findings

    Why it is in this group

    • The name "get_weekly_report" says "get": a word for reading.
    Description, as the server wrote it
    This week's SeoAiX report for the user's own store: headline traffic, revenue and keyword changes, what SeoAiX did, a short narrative, and this week's priorities. Optional `week_start` (YYYY-MM-DD, the Monday a past report covers).
  • list_pending_approvalsEverything waiting on the merchant in their own store: recommendations that need a decision (escalated ones first, with what to check) and article drafts ready to publish.No findings

    Why it is in this group

    • The name "list_pending_approvals" says "list": a word for reading.
    Description, as the server wrote it
    Everything waiting on the merchant in their own store: recommendations that need a decision (escalated ones first, with what to check) and article drafts ready to publish. Returns the ids decide_recommendation and publish_draft take.

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.

24 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 2 private-data tools breaks every one.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out4
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__seo-audit__ai_search_diagnostic",
      "mcp__seo-audit__get_store_status"
    ]
  }
}

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.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:46 UTC, unchanged since Nov 6, 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
6
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
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 6 tools that change things (1 irreversible, 5 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://seoaix.com/api/mcp: tools/list returned 12 tools to an anonymous client, including publish_draft (irreversible), full_seo_audit (write), generate_llms_txt (write), email_seo_report (write), subscribe_to_seoaix (write) and 1 more

    What this check looks for

Posture changes

  1. Nov 6, 2026
    • Tools that change things, listed without credentials: 3 to 6

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.

  1. Tools1 changed.~1 changedView diff
  2. Tools7 added.+7 addedView diff
  3. PostureRemote posture changed. Tools that change things, listed without credentials: 3 -> 6.View diff
    • Tools that change things, listed without credentials: 3 to 6

Install

Pinned to version 1.6.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http seo-audit https://seoaix.com/api/mcp
claude mcp add --transport http seo-audit https://seoaix.com/api/mcp

Run 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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__seo-audit__get_my_store_audit",
      "mcp__seo-audit__get_store_status",
      "mcp__seo-audit__get_weekly_report",
      "mcp__seo-audit__list_pending_approvals",
      "mcp__seo-audit__get_recent_changes"
    ],
    "ask": [
      "mcp__seo-audit__ai_search_diagnostic",
      "mcp__seo-audit__full_seo_audit",
      "mcp__seo-audit__generate_llms_txt",
      "mcp__seo-audit__email_seo_report",
      "mcp__seo-audit__subscribe_to_seoaix",
      "mcp__seo-audit__decide_recommendation",
      "mcp__seo-audit__publish_draft"
    ],
    "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 seo-audit. Review it before you use it.

Capability tags behind 6 rules
  • mcp__seo-audit__ai_search_diagnostic private-data, untrusted-input, outbound
  • mcp__seo-audit__full_seo_audit untrusted-input, outbound
  • mcp__seo-audit__generate_llms_txt outbound
  • mcp__seo-audit__get_my_store_audit untrusted-input
  • mcp__seo-audit__get_store_status private-data
  • mcp__seo-audit__publish_draft outbound

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.seoaix/seo-audit/verify?hash=0b0fb2a50a359f1def887dad1e510760d2c79dde1234bd290e7fa0fc8bcda1a9" | jq -e '.changed == false'

Pinned hash 0b0fb2a50a35, from Nov 18, 2026, 06:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.seoaix/seo-audit/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.seoaix/seo-audit
[![Anlyon Radar](https://radar.anlyon.com/badge/com.seoaix/seo-audit.svg)](https://radar.anlyon.com/servers/com.seoaix/seo-audit)

Source: MCP Registry · repository. Synced Nov 18, 2026, 06:17 UTC.

SeoAiX SEO Audit MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the SeoAiX SEO Audit MCP server safe?

No scan can promise that. What its definitions show: 12 tools, 6 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 SeoAiX SEO Audit MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the SeoAiX SEO Audit MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: publish_draft.

What tools does the SeoAiX SEO Audit MCP server have?

12 tools: 1 irreversible, 5 write, 6 read. publish_draft, full_seo_audit, generate_llms_txt, email_seo_report, subscribe_to_seoaix, decide_recommendation, ai_search_diagnostic, get_my_store_audit and 4 more.

Does the SeoAiX SEO Audit MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the SeoAiX SEO Audit MCP server send data to outside services?

4 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): ai_search_diagnostic, full_seo_audit, generate_llms_txt and publish_draft.

Has the SeoAiX SEO Audit MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 18, 2026. Every change is on this page and in its Atom feed.