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.

io.github.AutomateLab-tech/ai-seo

NPM · @AUTOMATELAB/AI-SEO-MCP

MCP server for AI-SEO auditing: schema, robots.txt, llms.txt, citation scoring, and AEO/GEO rewrites

Available components

npm · @automatelab/ai-seo-mcp 70
−1 this week 70 Trust /100

Last scanned (56 minutes ago)

Scores higher than 38% of npm servers

Category Marketing and SEO

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.29.0, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 33 of 124 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency23
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 752 tokens (~57/item across 13 items; 13 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 5 Nov 26 0
    • CVE-2026-9678 affects this package: high ▼ security
    • CVE-2026-16729 affects this package: high ▼ security
    • CVE-2026-18149 affects this package: high ▼ security
    • CVE-2026-109932 affects this package: high ▼ security
    • CVE-2026-85008 affects this package: high ▼ security
    • CVE-2026-111771 affects this package: high ▼ security
    • CVE-2026-15157 affects this package: high ▼ security
    • CVE-2026-84933 affects this package: high ▼ security
    • GHSA-f897-62hf-6gxq affects this package: high ▼ security
    • CVE-2026-84890 affects this package: high ▼ security
    • CVE-2026-84947 affects this package: high ▼ security
    • CVE-2026-84961 affects this package: high ▼ security
    • CVE-2026-19534 affects this package: high ▼ security
    • CVE-2026-109869 affects this package: high ▼ security
    • CVE-2026-13697 affects this package: high ▼ security
    • CVE-2026-14643 affects this package: high ▼ security
    • CVE-2026-109829 affects this package: high ▼ security
    • CVE-2026-109841 affects this package: high ▼ security
    • CVE-2026-111768 affects this package: high ▼ security
    • CVE-2026-6734 affects this package: high ▼ security
    • CVE-2026-18540 affects this package: high ▼ security
    • CVE-2026-111769 affects this package: high ▼ security
    • CVE-2026-109924 affects this package: high ▼ security
    • CVE-2026-11525 affects this package: high ▼ security
    • CVE-2026-87018 affects this package: high ▼ security
    • CVE-2026-9679 affects this package: high ▼ security
    • CVE-2023-54404 affects this package: high ▼ security
    • CVE-2026-109383 affects this package: high ▼ security
    • CVE-2026-85014 affects this package: high ▼ security
    • CVE-2026-6733 affects this package: high ▼ security
    • CVE-2026-104850 affects this package: high ▼ security
    • CVE-2026-111767 affects this package: high ▼ security
    • CVE-2026-16728 affects this package: high ▼ security
    • CVE-2026-12151 affects this package: high ▼ security
    • CVE-2026-87029 affects this package: high ▼ security
    • CVE-2026-118663 affects this package: high ▼ security
    • CVE-2026-9697 affects this package: high ▼ security
  • 4 Nov 26 +1
    • CVE-2026-9678 affects this package: high ▼ security
    • CVE-2026-16729 affects this package: high ▼ security
    • CVE-2026-18149 affects this package: high ▼ security
    • CVE-2026-109932 affects this package: high ▼ security
    • CVE-2026-85008 affects this package: high ▼ security
    • CVE-2026-111771 affects this package: high ▼ security
    • CVE-2026-15157 affects this package: high ▼ security
    • CVE-2026-84933 affects this package: high ▼ security
    • GHSA-f897-62hf-6gxq affects this package: high ▼ security
    • CVE-2026-84890 affects this package: high ▼ security
    • CVE-2026-84947 affects this package: high ▼ security
    • CVE-2026-84961 affects this package: high ▼ security
    • CVE-2026-19534 affects this package: high ▼ security
    • CVE-2026-109869 affects this package: high ▼ security
    • CVE-2026-13697 affects this package: high ▼ security
    • CVE-2026-14643 affects this package: high ▼ security
    • CVE-2026-109829 affects this package: high ▼ security
    • CVE-2026-109841 affects this package: high ▼ security
    • CVE-2026-111768 affects this package: high ▼ security
    • CVE-2026-6734 affects this package: high ▼ security
    • CVE-2026-18540 affects this package: high ▼ security
    • CVE-2026-111769 affects this package: high ▼ security
    • CVE-2026-109924 affects this package: high ▼ security
    • CVE-2026-11525 affects this package: high ▼ security
    • CVE-2026-87018 affects this package: high ▼ security
    • CVE-2026-9679 affects this package: high ▼ security
    • CVE-2023-54404 affects this package: high ▼ security
    • CVE-2026-109383 affects this package: high ▼ security
    • CVE-2026-85014 affects this package: high ▼ security
    • CVE-2026-6733 affects this package: high ▼ security
    • CVE-2026-104850 affects this package: high ▼ security
    • CVE-2026-111767 affects this package: high ▼ security
    • CVE-2026-16728 affects this package: high ▼ security
    • CVE-2026-12151 affects this package: high ▼ security
    • CVE-2026-87029 affects this package: high ▼ security
    • CVE-2026-118663 affects this package: high ▼ security
    • CVE-2026-9697 affects this package: high ▼ security
  • 3 Nov 26 −2
    • CVE-2026-9678 affects this package: high ▼ security
    • CVE-2026-16729 affects this package: high ▼ security
    • CVE-2026-18149 affects this package: high ▼ security
    • CVE-2026-109932 affects this package: high ▼ security
    • CVE-2026-85008 affects this package: high ▼ security
    • CVE-2026-111771 affects this package: high ▼ security
    • CVE-2026-15157 affects this package: high ▼ security
    • CVE-2026-84933 affects this package: high ▼ security
    • GHSA-f897-62hf-6gxq affects this package: high ▼ security
    • CVE-2026-84890 affects this package: high ▼ security
    • CVE-2026-84947 affects this package: high ▼ security
    • CVE-2026-84961 affects this package: high ▼ security
    • CVE-2026-19534 affects this package: high ▼ security
    • CVE-2026-109869 affects this package: high ▼ security
    • CVE-2026-13697 affects this package: high ▼ security
    • CVE-2026-14643 affects this package: high ▼ security
    • CVE-2026-109829 affects this package: high ▼ security
    • CVE-2026-109841 affects this package: high ▼ security
    • CVE-2026-111768 affects this package: high ▼ security
    • CVE-2026-6734 affects this package: high ▼ security
    • CVE-2026-18540 affects this package: high ▼ security
    • CVE-2026-111769 affects this package: high ▼ security
    • CVE-2026-109924 affects this package: high ▼ security
    • CVE-2026-11525 affects this package: high ▼ security
    • CVE-2026-87018 affects this package: high ▼ security
    • CVE-2026-9679 affects this package: high ▼ security
    • CVE-2023-54404 affects this package: high ▼ security
    • CVE-2026-109383 affects this package: high ▼ security
    • CVE-2026-85014 affects this package: high ▼ security
    • CVE-2026-6733 affects this package: high ▼ security
    • CVE-2026-104850 affects this package: high ▼ security
    • CVE-2026-111767 affects this package: high ▼ security
    • CVE-2026-16728 affects this package: high ▼ security
    • CVE-2026-12151 affects this package: high ▼ security
    • CVE-2026-87029 affects this package: high ▼ security
    • CVE-2026-118663 affects this package: high ▼ security
    • CVE-2026-9697 affects this package: high ▼ security
    • Stability: pass → 0.90 functional
  • 2 Nov 26 0
    • CVE-2026-9678 affects this package: high ▼ security
    • CVE-2026-16729 affects this package: high ▼ security
    • CVE-2026-18149 affects this package: high ▼ security
    • CVE-2026-109932 affects this package: high ▼ security
    • CVE-2026-85008 affects this package: high ▼ security
    • CVE-2026-111771 affects this package: high ▼ security
    • CVE-2026-15157 affects this package: high ▼ security
    • CVE-2026-84933 affects this package: high ▼ security
    • GHSA-f897-62hf-6gxq affects this package: high ▼ security
    • CVE-2026-84890 affects this package: high ▼ security
    • CVE-2026-84947 affects this package: high ▼ security
    • CVE-2026-84961 affects this package: high ▼ security
    • CVE-2026-19534 affects this package: high ▼ security
    • CVE-2026-109869 affects this package: high ▼ security
    • CVE-2026-13697 affects this package: high ▼ security
    • CVE-2026-14643 affects this package: high ▼ security
    • CVE-2026-109829 affects this package: high ▼ security
    • CVE-2026-109841 affects this package: high ▼ security
    • CVE-2026-111768 affects this package: high ▼ security
    • CVE-2026-6734 affects this package: high ▼ security
    • CVE-2026-18540 affects this package: high ▼ security
    • CVE-2026-111769 affects this package: high ▼ security
    • CVE-2026-109924 affects this package: high ▼ security
    • CVE-2026-11525 affects this package: high ▼ security
    • CVE-2026-87018 affects this package: high ▼ security
    • CVE-2026-9679 affects this package: high ▼ security
    • CVE-2023-54404 affects this package: high ▼ security
    • CVE-2026-109383 affects this package: high ▼ security
    • CVE-2026-85014 affects this package: high ▼ security
    • CVE-2026-6733 affects this package: high ▼ security
    • CVE-2026-104850 affects this package: high ▼ security
    • CVE-2026-111767 affects this package: high ▼ security
    • CVE-2026-16728 affects this package: high ▼ security
    • CVE-2026-12151 affects this package: high ▼ security
    • CVE-2026-87029 affects this package: high ▼ security
    • CVE-2026-118663 affects this package: high ▼ security
    • CVE-2026-9697 affects this package: high ▼ security
  • 1 Nov 26 0
    • CVE-2026-9678 affects this package: high ▼ security
    • CVE-2026-16729 affects this package: high ▼ security
    • CVE-2026-18149 affects this package: high ▼ security
    • CVE-2026-109932 affects this package: high ▼ security
    • CVE-2026-85008 affects this package: high ▼ security
    • CVE-2026-111771 affects this package: high ▼ security
    • CVE-2026-15157 affects this package: high ▼ security
    • CVE-2026-84933 affects this package: high ▼ security
    • GHSA-f897-62hf-6gxq affects this package: high ▼ security
    • CVE-2026-84890 affects this package: high ▼ security
    • CVE-2026-84947 affects this package: high ▼ security
    • CVE-2026-84961 affects this package: high ▼ security
    • CVE-2026-19534 affects this package: high ▼ security
    • CVE-2026-109869 affects this package: high ▼ security
    • CVE-2026-13697 affects this package: high ▼ security
    • CVE-2026-14643 affects this package: high ▼ security
    • CVE-2026-109829 affects this package: high ▼ security
    • CVE-2026-109841 affects this package: high ▼ security
    • CVE-2026-111768 affects this package: high ▼ security
    • CVE-2026-6734 affects this package: high ▼ security
    • CVE-2026-18540 affects this package: high ▼ security
    • CVE-2026-111769 affects this package: high ▼ security
    • CVE-2026-109924 affects this package: high ▼ security
    • CVE-2026-11525 affects this package: high ▼ security
    • CVE-2026-87018 affects this package: high ▼ security
    • CVE-2026-9679 affects this package: high ▼ security
    • CVE-2023-54404 affects this package: high ▼ security
    • CVE-2026-109383 affects this package: high ▼ security
    • CVE-2026-85014 affects this package: high ▼ security
    • CVE-2026-6733 affects this package: high ▼ security
    • CVE-2026-104850 affects this package: high ▼ security
    • CVE-2026-111767 affects this package: high ▼ security
    • CVE-2026-16728 affects this package: high ▼ security
    • CVE-2026-12151 affects this package: high ▼ security
    • CVE-2026-87029 affects this package: high ▼ security
    • CVE-2026-118663 affects this package: high ▼ security
    • CVE-2026-9697 affects this package: high ▼ security
  • 31 Oct 26 0

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

    • CVE-2026-9678 affects this package: high ▼ security
    • CVE-2026-16729 affects this package: high ▼ security
    • CVE-2026-18149 affects this package: high ▼ security
    • CVE-2026-109932 affects this package: high ▼ security
    • CVE-2026-85008 affects this package: high ▼ security
    • CVE-2026-111771 affects this package: high ▼ security
    • CVE-2026-15157 affects this package: high ▼ security
    • CVE-2026-84933 affects this package: high ▼ security
    • GHSA-f897-62hf-6gxq affects this package: high ▼ security
    • CVE-2026-84890 affects this package: high ▼ security
    • CVE-2026-84947 affects this package: high ▼ security
    • CVE-2026-84961 affects this package: high ▼ security
  • 28 Oct 26 +1

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

  • 27 Oct 26 −1

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

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 5 Nov 2026 · Analysed npm/@automatelab/ai-seo-mcp@0.1.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 37 findings
ID CVE Severity Vector Fix available
GHSA-rmxm-3fg6-px4f CVE-2026-118663 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N yes
GHSA-22jm-h49p-29qw CVE-2026-111767 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L yes
GHSA-46jr-4wx8-v453 CVE-2026-111768 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-6prh-2h8m-c8cw CVE-2026-111769 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N yes
GHSA-6qxp-vccf-f47h CVE-2026-104850 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-f897-62hf-6gxq high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-rvq5-wwqv-78pq CVE-2026-111771 medium CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N yes
GHSA-2gqq-gqf2-x968 CVE-2026-84947 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-2jfj-6hjv-fm6j CVE-2026-84933 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N yes
GHSA-2m5v-pch6-74hx CVE-2026-109383 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N yes
GHSA-35p6-xmwp-9g52 CVE-2026-6733 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-3xpg-4rpp-hhhm CVE-2026-84890 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-4cwx-7wf7-3272 CVE-2026-13697 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H yes
GHSA-4qv8-2p9j-2685 CVE-2026-109924 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-4w7w-5xrc-9h26 CVE-2026-109829 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N yes
GHSA-55wc-3pg8-jfw6 CVE-2026-87029 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-8436-99hf-9mmv CVE-2026-85008 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-8xcm-r25x-g524 CVE-2026-16728 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N yes
GHSA-9fm3-97px-rjf6 CVE-2026-109932 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-f72v-6w45-q472 CVE-2026-109841 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N yes
GHSA-g8m3-5g58-fq7m CVE-2026-11525 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-hm92-r4w5-c3mj CVE-2026-6734 high CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H yes
GHSA-jr45-8vmc-qm54 CVE-2026-14643 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-m8rv-5g2x-5cg5 CVE-2026-15157 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N yes
GHSA-p88m-4jfj-68fv CVE-2026-9679 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N yes
GHSA-pmjh-fq2x-6v4x CVE-2026-18149 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-pr7r-676h-xcf6 CVE-2026-9678 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-qrxm-fqhp-jwvm CVE-2026-87018 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-r53p-7pc4-xj5r CVE-2026-18540 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-rfgv-xxqx-mfg5 CVE-2026-19534 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-rx4f-c7p8-82vq CVE-2026-85014 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-v3r7-h72x-cjcm CVE-2026-16729 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N yes
GHSA-vmh5-mc38-953g CVE-2026-9697 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N yes
GHSA-vxpw-j846-p89q CVE-2026-12151 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-w293-vg96-wgc3 CVE-2026-84961 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N yes
GHSA-xjj6-f33q-929c CVE-2026-109869 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 124 packages
Packages resolved 124
Deprecated 1
Stale 33
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 13 exposed · ~752 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
audit_canonical ~44

Audit canonical link integrity, trailing-slash hygiene, self-referencing, and og:url consistency.

NameTypeReqDescription
respect_robotsboolean––
urlstringyes–

No output schema declared.

No examples provided.

audit_page ~62

Run a full AI-SEO audit on a single URL and return categorized findings with severity, fix instructions, and a 0-100 score.

NameTypeReqDescription
include_raw_htmlboolean––
respect_robotsboolean––
urlstringyes–

No output schema declared.

No examples provided.

audit_schema ~56

Validate JSON-LD structured data on a URL or raw JSON string against Schema.org rules and AI-citation best practices.

NameTypeReqDescription
respect_robotsboolean––
schema_jsonstring––
urlstring––

No output schema declared.

No examples provided.

check_robots ~38

Parse a domain's robots.txt and report per-crawler allow/disallow posture for all known AI crawlers.

NameTypeReqDescription
domainstringyes–

No output schema declared.

No examples provided.

check_sitemap ~49

Validate a domain's XML sitemap for presence, accessibility, URL count, lastmod freshness, and AI-search attributes.

NameTypeReqDescription
domainstringyes–
max_urls_to_checkinteger––

No output schema declared.

No examples provided.

check_technical ~52

Audit a page's HEAD for canonical, OpenGraph, Twitter Card, hreflang, HTTPS, noindex, and title hygiene.

NameTypeReqDescription
respect_robotsboolean––
urlstringyes–

No output schema declared.

No examples provided.

extract_entities ~52

Extract named entities, linked concepts, and sameAs graph nodes from a page's content and structured data.

NameTypeReqDescription
respect_robotsboolean––
textstring––
urlstring––

No output schema declared.

No examples provided.

generate_llms_txt ~70

Generate a valid llms.txt (and optionally llms-full.txt) for a domain from its sitemap.

NameTypeReqDescription
domainstringyes–
include_fullboolean––
max_pagesinteger––
site_descriptionstring––
site_namestring––

No output schema declared.

No examples provided.

rewrite_for_aeo ~78

Rewrite a content block for Answer Engine Optimization - adds BLUF opening, FAQ structure, and schema additions.

NameTypeReqDescription
formatstring––
max_wordsinteger––
respect_robotsboolean––
target_querystringyes–
textstring––
urlstring––

No output schema declared.

No examples provided.

rewrite_for_geo ~77

Rewrite a content block for Generative Engine Optimization - entity-rich, comparison-ready, synthesis-friendly.

NameTypeReqDescription
add_comparison_tableboolean––
max_wordsinteger––
respect_robotsboolean––
target_querystringyes–
textstring––
urlstring––

No output schema declared.

No examples provided.

score_ai_overview_eligibility ~52

Score a page's probability of appearing in Google AI Overviews using published 2025-2026 correlation factors.

NameTypeReqDescription
respect_robotsboolean––
urlstringyes–

No output schema declared.

No examples provided.

score_citation_worthiness ~69

Score how citable a page or text block is for AI engines: BLUF, FAQ patterns, statistic density, entity clarity.

NameTypeReqDescription
respect_robotsboolean––
target_querystring––
textstring––
urlstring––

No output schema declared.

No examples provided.

validate_llms_txt ~53

Validate an existing llms.txt or llms-full.txt against the spec, checking structure and broken links.

NameTypeReqDescription
check_linksboolean––
contentstring––
urlstring––

No output schema declared.

No examples provided.

Install

How do I install the io.github.AutomateLab-tech/ai-seo MCP server?

io.github.AutomateLab-tech/ai-seo runs locally as an npm package, launched with npx -y @automatelab/ai-seo-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @automatelab/ai-seo-mcp

# add to Claude Code
claude mcp add automatelab-tech-ai-seo -- npx -y @automatelab/ai-seo-mcp
Common questions

What is the io.github.AutomateLab-tech/ai-seo MCP server?

io.github.AutomateLab-tech/ai-seo is an MCP server listed in the public MCP registry as io.github.AutomateLab-tech/ai-seo. MCP server for AI-SEO auditing: schema, robots.txt, llms.txt, citation scoring, and AEO/GEO rewrites. This page covers its npm package (@automatelab/ai-seo-mcp).

Is the io.github.AutomateLab-tech/ai-seo MCP server safe to use?

io.github.AutomateLab-tech/ai-seo scores 70 out of 100 on VerifyMCP. We recorded 37 known advisories against it as of 5 November 2026. It declares no install or post-install scripts. 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 io.github.AutomateLab-tech/ai-seo MCP server expose?

io.github.AutomateLab-tech/ai-seo exposes 13 tools: audit_page, audit_schema, audit_canonical, check_robots, check_sitemap, and 8 more. Their descriptions and schemas cost roughly 752 tokens of context every time the server is loaded.

Is the io.github.AutomateLab-tech/ai-seo MCP server still maintained?

io.github.AutomateLab-tech/ai-seo is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.AutomateLab-tech/ai-seo MCP server under?

io.github.AutomateLab-tech/ai-seo declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.