ai.inxy/seo-audit
REMOTE · INXY.AI · SCANNED SEP 20
Free SEO & AI-search (AEO) audits for any site or Shopify store, with emailed weekly score reports.
Available components
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 839 tokens (~167/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
How do I install the ai.inxy/seo-audit MCP server?
ai.inxy/seo-audit is a hosted endpoint at https://inxy.ai/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 · inxy.ai
claude mcp add --transport http ai-inxy-seo-audit 'https://inxy.ai/api/mcp'
{
"mcpServers": {
"ai-inxy-seo-audit": {
"url": "https://inxy.ai/api/mcp"
}
}
} {
"servers": {
"ai-inxy-seo-audit": {
"type": "http",
"url": "https://inxy.ai/api/mcp"
}
}
} [mcp_servers.ai-inxy-seo-audit] url = "https://inxy.ai/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-inxy-seo-audit": {
"type": "remote",
"url": "https://inxy.ai/api/mcp",
"enabled": true
}
}
} openclaw mcp add ai-inxy-seo-audit --url 'https://inxy.ai/api/mcp' --transport streamable-http
mcp_servers:
ai-inxy-seo-audit:
url: "https://inxy.ai/api/mcp" {
"McpServers": {
"ai-inxy-seo-audit": {
"Transport": "http",
"Url": "https://inxy.ai/api/mcp"
}
}
} assistant mcp add ai-inxy-seo-audit -t streamable-http -u 'https://inxy.ai/api/mcp'
{
"mcpServers": {
"ai-inxy-seo-audit": {
"type": "http",
"url": "https://inxy.ai/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 2 Sept 26 −1
- Tool “ai_search_diagnostic” rewrote its description, which is the text the model reads security
- Tool “email_seo_report” rewrote its description, which is the text the model reads security
- Tool “full_seo_audit” rewrote its description, which is the text the model reads security
- Schema quality: 146 → 167 ▼ functional
- 29 Aug 26 −1
- MCP protocol: pass → fail ▼ functional
- MCP protocol version: 2025-11-25 → 2025-06-18 functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Aug 26 −1
- Schema quality: 433 → 734 ▼ functional
- New tool “email_seo_report” functional
- New tool “subscribe_to_inxy” functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 20 Sept 2026 · Probed https://inxy.ai/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=inxy.ai | CN=WE1,O=Google Trust Services,C=US | 6 Sept 2026 | 5 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 427d912fcf40222913c29f2f58ff2530 |
| SANs: inxy.ai | ||||||
| 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 inxy.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| inxy.ai. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://inxy.ai/api/mcp | Verified | 200 | |
| http (plaintext) | http://inxy.ai/api/mcp | HTTPS enforced | 301 | https://inxy.ai/api/mcp |
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 →
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The 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.
| Name | Type | Req | Description |
|---|---|---|---|
| audit_id | string | yes | The audit_id from a previous audit result in this conversation |
| string | yes | The email address the user asked the report to be sent to | |
| weekly | boolean | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The website URL to audit, e.g. https://example.com |
No output schema declared.
No examples provided.
get_my_store_audit ~152
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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Your Inxy API key (inxy_sk_…). Optional if already sent as an Authorization: Bearer header. |
No output schema declared.
No examples provided.
subscribe_to_inxy ~154
Start an inxy 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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | The user's email, only if they explicitly gave it | |
| store_url | string | – | The user's store URL, only if they explicitly gave it |
No output schema declared.
No examples provided.
What is the ai.inxy/seo-audit MCP server?
ai.inxy/seo-audit is an MCP server listed in the public MCP registry as ai.inxy/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://inxy.ai/api/mcp).
Is the ai.inxy/seo-audit MCP server safe to use?
ai.inxy/seo-audit scores 79 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 ai.inxy/seo-audit MCP server expose?
ai.inxy/seo-audit exposes 5 tools: ai_search_diagnostic, full_seo_audit, email_seo_report, subscribe_to_inxy, get_my_store_audit. Their descriptions and schemas cost roughly 839 tokens of context every time the server is loaded.
Does the ai.inxy/seo-audit MCP server require authentication?
No. We connected to ai.inxy/seo-audit without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ai.inxy/seo-audit MCP server still maintained?
ai.inxy/seo-audit is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.