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.

MaxAEO AI Visibility MCP

NPM · MAXAEO-AI-VISIBILITY-MCP · SCANNED SEP 22

Local-first MCP server for AI visibility, GEO/AEO, llms.txt, and AI crawler readiness audits.

Available components

npm · maxaeo-ai-visibility-mcp 83
0 this week 83 Trust /100
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 Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 26 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 619 tokens (~206/item across 3 items; 3 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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
Install

How do I install the MaxAEO AI Visibility MCP server?

MaxAEO AI Visibility MCP runs locally as an npm package, launched with npx -y maxaeo-ai-visibility-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 · maxaeo-ai-visibility-mcp

# add to Claude Code
claude mcp add maxaeo-maxaeo-ai-visibility-mcp -- npx -y maxaeo-ai-visibility-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "maxaeo-maxaeo-ai-visibility-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "maxaeo-ai-visibility-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "maxaeo-maxaeo-ai-visibility-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "maxaeo-ai-visibility-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add maxaeo-maxaeo-ai-visibility-mcp -- npx -y maxaeo-ai-visibility-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "maxaeo-maxaeo-ai-visibility-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "maxaeo-ai-visibility-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add maxaeo-maxaeo-ai-visibility-mcp --command npx --arg -y --arg maxaeo-ai-visibility-mcp
# ~/.hermes/config.yaml
mcp_servers:
  maxaeo-maxaeo-ai-visibility-mcp:
    command: "npx"
    args: ["-y", "maxaeo-ai-visibility-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "maxaeo-maxaeo-ai-visibility-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "maxaeo-ai-visibility-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add maxaeo-maxaeo-ai-visibility-mcp -t stdio -c npx -a -y maxaeo-ai-visibility-mcp
// mcp.json
{
  "mcpServers": {
    "maxaeo-maxaeo-ai-visibility-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "maxaeo-ai-visibility-mcp"
      ]
    }
  }
}
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.

  • 22 Sept 26 +1
    • Stability: 0.97 → pass security
  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 15 Sept 26 +1
    • Stability: 0.97 → pass security
  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 −3
    • Stability: pass → 0.80 functional
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 22 Sept 2026 · Analysed npm/maxaeo-ai-visibility-mcp@0.4.0

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 →

Dependencies 95 packages
Packages resolved 95
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~619 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_ai_crawler_readiness ~184

Check robots rules, AI crawler access basics, homepage metadata, canonical, noindex, and JSON-LD schema. No MaxAEO APIs are called.

NameTypeReqDescription
ctaBaseUrlstring–Optional custom MaxAEO CTA base URL. Overrides market defaults and MAXAEO_CTA_URL_* environment variables.
localestring–Output locale. Supported values and aliases: en-US, en, global, zh-CN, zh, cn. Defaults to en-US or MAXAEO_LOCALE.
marketstring–Promotion market for the MaxAEO CTA. global uses maxaeo.ai; cn uses maxaeo.cn. Defaults from locale or MAXAEO_MARKET.
timeoutMsinteger–Request timeout in milliseconds. Defaults to 10000.
urlstringyesPublic website URL to audit.

No output schema declared.

No examples provided.

build_ai_visibility_report ~215

Run local/public-web AI visibility checks and return dual scores, evidence gaps, an action plan, and a transparent MaxAEO CTA.

NameTypeReqDescription
checkLinksboolean–Whether to check linked URLs. Defaults to true.
ctaBaseUrlstring–Optional custom MaxAEO CTA base URL. Overrides market defaults and MAXAEO_CTA_URL_* environment variables.
localestring–Output locale. Supported values and aliases: en-US, en, global, zh-CN, zh, cn. Defaults to en-US or MAXAEO_LOCALE.
marketstring–Promotion market for the MaxAEO CTA. global uses maxaeo.ai; cn uses maxaeo.cn. Defaults from locale or MAXAEO_MARKET.
maxLinksinteger–Maximum llms.txt links to check. Defaults to 15.
timeoutMsinteger–Request timeout in milliseconds. Defaults to 10000.
urlstringyesPublic website URL to audit.

No output schema declared.

No examples provided.

check_llms_txt ~220

Validate /llms.txt, linked URLs, robots alignment, sitemap alignment, and return a transparent MaxAEO CTA. No MaxAEO APIs are called.

NameTypeReqDescription
checkLinksboolean–Whether to check linked URLs. Defaults to true.
ctaBaseUrlstring–Optional custom MaxAEO CTA base URL. Overrides market defaults and MAXAEO_CTA_URL_* environment variables.
localestring–Output locale. Supported values and aliases: en-US, en, global, zh-CN, zh, cn. Defaults to en-US or MAXAEO_LOCALE.
marketstring–Promotion market for the MaxAEO CTA. global uses maxaeo.ai; cn uses maxaeo.cn. Defaults from locale or MAXAEO_MARKET.
maxLinksinteger–Maximum llms.txt links to check. Defaults to 30.
timeoutMsinteger–Request timeout in milliseconds. Defaults to 10000.
urlstringyesPublic website URL to audit.

No output schema declared.

No examples provided.

Common questions

What is the MaxAEO AI Visibility MCP server?

MaxAEO AI Visibility MCP is listed in the public MCP registry as io.github.maxaeo/maxaeo-ai-visibility-mcp. Local-first MCP server for AI visibility, GEO/AEO, llms.txt, and AI crawler readiness audits. This page covers its npm package (maxaeo-ai-visibility-mcp).

Is the MaxAEO AI Visibility MCP server safe to use?

MaxAEO AI Visibility MCP scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 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 MaxAEO AI Visibility MCP server expose?

MaxAEO AI Visibility MCP exposes 3 tools: check_llms_txt, audit_ai_crawler_readiness, build_ai_visibility_report. Their descriptions and schemas cost roughly 619 tokens of context every time the server is loaded.

Is the MaxAEO AI Visibility MCP server still maintained?

MaxAEO AI Visibility MCP is still listed as active in the MCP registry. We last reached this channel on 22 September 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 MaxAEO AI Visibility MCP server under?

MaxAEO AI Visibility MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.