# AEO Visibility (remote · aeo.advancelabs.dev)

Check whether AI answer engines cite your site, and for which prompts. Uses your own Perplexity key.

- Trust score: 73/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `aeo.advancelabs.dev`: 73/100 (this document), [markdown](https://verifymcp.io/servers/dev-advancelabs-aeo-visibility/api-mcp-ai-visibility-mcp.md), [page](https://verifymcp.io/servers/dev-advancelabs-aeo-visibility/api-mcp-ai-visibility-mcp)

## Channel facts

- Endpoint: `https://aeo.advancelabs.dev/api/mcp/ai-visibility/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 434 tokens (~86/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 90/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 71% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the AEO Visibility MCP server?

AEO Visibility is a hosted endpoint at https://aeo.advancelabs.dev/api/mcp/ai-visibility/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.

### Claude

```bash
claude mcp add --transport http dev-advancelabs-aeo-visibility 'https://aeo.advancelabs.dev/api/mcp/ai-visibility/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-advancelabs-aeo-visibility": {
      "url": "https://aeo.advancelabs.dev/api/mcp/ai-visibility/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-advancelabs-aeo-visibility": {
      "type": "http",
      "url": "https://aeo.advancelabs.dev/api/mcp/ai-visibility/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-advancelabs-aeo-visibility]
url = "https://aeo.advancelabs.dev/api/mcp/ai-visibility/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-advancelabs-aeo-visibility": {
      "type": "remote",
      "url": "https://aeo.advancelabs.dev/api/mcp/ai-visibility/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-advancelabs-aeo-visibility --url 'https://aeo.advancelabs.dev/api/mcp/ai-visibility/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-advancelabs-aeo-visibility:
    url: "https://aeo.advancelabs.dev/api/mcp/ai-visibility/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-advancelabs-aeo-visibility": {
      "Transport": "http",
      "Url": "https://aeo.advancelabs.dev/api/mcp/ai-visibility/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-advancelabs-aeo-visibility -t streamable-http -u 'https://aeo.advancelabs.dev/api/mcp/ai-visibility/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-advancelabs-aeo-visibility": {
      "type": "http",
      "url": "https://aeo.advancelabs.dev/api/mcp/ai-visibility/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 73, +1)

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

### 2026-11-01 (score 72, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-31 (score 71)

First indexed and scored.

## MCP tools (5)

### `analyze_website_aeo` (~59 tokens)

Analyze website AEO

Crawl a URL, parse its HTML and structured data, and score it for answer-engine optimization (AEO). Returns an AEO-focused summary, AI-bot access, and crawl-hint files.

Input parameters:

- `url` (string, required)

### `check_ai_visibility` (~94 tokens)

Check AI visibility

Query Perplexity Sonar with a prompt and inspect its citations to determine whether the given URL is cited as a source, and at what rank.

Input parameters:

- `perplexityApiKey` (string, required): Your Perplexity API key (BYOK). Request-scoped; never stored or logged.
- `prompt` (string, required): The end-user question to test.
- `url` (string, required): The site URL to check for citations.

### `discover_ranking_prompts` (~114 tokens)

Discover ranking prompts

Generate realistic user prompts a site should aim to be cited for on a topic, using Perplexity Sonar. Optionally tests a few of them for live visibility.

Input parameters:

- `perplexityApiKey` (string, required): Your Perplexity API key (BYOK). Request-scoped; never stored or logged.
- `testCount` (integer): How many generated prompts to live-test (default 3).
- `topic` (string, required): The topic / niche to generate prompts for.
- `url` (string, required)

### `get_visibility_report` (~83 tokens)

Get visibility report

Combine an AEO audit of a URL with per-prompt AI-visibility checks into a single report with an overall citation rate.

Input parameters:

- `perplexityApiKey` (string, required): Your Perplexity API key (BYOK). Request-scoped; never stored or logged.
- `prompts` (array, required): Prompts to test for visibility.
- `url` (string, required)

### `compare_competitor_visibility` (~84 tokens)

Compare competitor visibility

Run one Perplexity Sonar query and rank several competitor URLs by whether and where each is cited for the prompt.

Input parameters:

- `perplexityApiKey` (string, required): Your Perplexity API key (BYOK). Request-scoped; never stored or logged.
- `prompt` (string, required)
- `urls` (array, required): Two or more competitor URLs to rank.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-advancelabs-aeo-visibility/api-mcp-ai-visibility-mcp#diagnostics

## Score history

- 2026-11-05: 73
- 2026-11-04: 73
- 2026-11-03: 72
- 2026-11-02: 72
- 2026-11-01: 72
- 2026-10-31: 71

## Common questions

### What is the AEO Visibility MCP server?

AEO Visibility is an MCP server listed in the public MCP registry as dev.advancelabs/aeo-visibility. Check whether AI answer engines cite your site, and for which prompts. Uses your own Perplexity key. This page covers its hosted endpoint (https://aeo.advancelabs.dev/api/mcp/ai-visibility/mcp).

### Is the AEO Visibility MCP server safe to use?

AEO Visibility scores 73 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 AEO Visibility MCP server expose?

AEO Visibility exposes 5 tools: analyze_website_aeo, check_ai_visibility, discover_ranking_prompts, get_visibility_report, compare_competitor_visibility. Their descriptions and schemas cost roughly 434 tokens of context every time the server is loaded.

### Does the AEO Visibility MCP server require authentication?

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

### Is the AEO Visibility MCP server still maintained?

AEO Visibility 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 did VerifyMCP test on the AEO Visibility MCP server?

VerifyMCP ran 13 checks on AEO Visibility, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://aeo.advancelabs.dev/api/mcp/ai-visibility/mcp
- Repository: https://github.com/Advance-Labs/aeo-toolkit
- Website: https://aeo.advancelabs.dev/mcp
- Changelog RSS feed: https://verifymcp.io/servers/dev-advancelabs-aeo-visibility/api-mcp-ai-visibility-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-advancelabs-aeo-visibility/api-mcp-ai-visibility-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dev-advancelabs-aeo-visibility/api-mcp-ai-visibility-mcp.json
- HTML version of this page: https://verifymcp.io/servers/dev-advancelabs-aeo-visibility/api-mcp-ai-visibility-mcp