AEO Scanner
REMOTE · AEO-MCP.CONVRGENT.AI · 2 COMPONENTS · SCANNED SEP 20
AI visibility for ChatGPT/Perplexity/Claude — triple score (AEO+GEO+Agent) with fix code. Free.
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 Security46
- 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 4 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 enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1032 tokens (~206/item across 5 items; 4 tools + 1 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
How do I install the AEO Scanner MCP server?
AEO Scanner is a hosted endpoint at https://aeo-mcp.convrgent.ai/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 · aeo-mcp.convrgent.ai
claude mcp add --transport http convrgent-aeo-scanner 'https://aeo-mcp.convrgent.ai/mcp'
{
"mcpServers": {
"convrgent-aeo-scanner": {
"url": "https://aeo-mcp.convrgent.ai/mcp"
}
}
} {
"servers": {
"convrgent-aeo-scanner": {
"type": "http",
"url": "https://aeo-mcp.convrgent.ai/mcp"
}
}
} [mcp_servers.convrgent-aeo-scanner] url = "https://aeo-mcp.convrgent.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"convrgent-aeo-scanner": {
"type": "remote",
"url": "https://aeo-mcp.convrgent.ai/mcp",
"enabled": true
}
}
} openclaw mcp add convrgent-aeo-scanner --url 'https://aeo-mcp.convrgent.ai/mcp' --transport streamable-http
mcp_servers:
convrgent-aeo-scanner:
url: "https://aeo-mcp.convrgent.ai/mcp" {
"McpServers": {
"convrgent-aeo-scanner": {
"Transport": "http",
"Url": "https://aeo-mcp.convrgent.ai/mcp"
}
}
} assistant mcp add convrgent-aeo-scanner -t streamable-http -u 'https://aeo-mcp.convrgent.ai/mcp'
{
"mcpServers": {
"convrgent-aeo-scanner": {
"type": "http",
"url": "https://aeo-mcp.convrgent.ai/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.
- 26 Aug 26 +1
- 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.
- 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
- 30 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
- 27 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
- 26 Jul 26 0
First indexed and scored.
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://aeo-mcp.convrgent.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=convrgent.ai | CN=WE1,O=Google Trust Services,C=US | 28 Jul 2026 | 26 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 771a08ab415cf9850ed9f14ede0dbae4 |
| SANs: convrgent.ai, aeo-mcp.convrgent.ai, *.aeo-mcp.convrgent.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 aeo-mcp.convrgent.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| convrgent.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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://aeo-mcp.convrgent.ai/mcp | Verified | 200 | |
| http (plaintext) | http://aeo-mcp.convrgent.ai/mcp | Inconclusive | 406 |
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 →
audit_site ~313
Full AI visibility audit across 77+ checks in 12 categories (4 AEO + 4 GEO + 4 Agent Readiness). Returns detailed per-check scores with specific issues and recommendations, AI Identity Card with mention readiness and detected competitors, and business profile. GEO checks include 3 research-backed citation signals: factual density, answer frontloading, and source citations. Agent Readiness covers emerging agent-discovery standards Cloudflare's isitagentready.com evaluates: RFC 9727 api-catalog, SEP-1649 MCP Server Card, and IETF Content-Signal (draft-romm-aipref). Does NOT generate fix code — pass this response's id as scan_id to fix_site (within 1 hour) to get fixes WITHOUT a re-crawl, or use compare_sites to benchmark against a competitor. Pay per call ($1.00) via x402 — USDC on Base or Solana. Machine payment via signed X-PAYMENT header; see https://www.x402.org/. On payment_required, the response includes the full x402 payload with payTo/amount/asset.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | – | Filter to specific categories: structured_data, meta_technical, ai_accessibility, content_quality, brand_narrative, citation_readiness, authority_signals, entity_definition, machine_identity, api_dis… |
| pages | integer | – | Number of pages to audit (1-10) |
| url | string | yes | Full URL to audit |
No output schema declared.
No examples provided.
compare_sites ~160
Competitive gap analysis — scans two sites concurrently, shows side-by-side scores, category-by-category winners, competitive gaps (checks where the competitor scored 20+ higher), and generated overtake fix code with projected scores after closing gaps. Use this when the user wants to benchmark against a competitor or when scan_site detects competitors in the AI Identity Card. Pay per call ($3.00) via x402 — USDC on Base or Solana. On payment_required, the response includes the full x402 payload with payTo/amount/asset.
| Name | Type | Req | Description |
|---|---|---|---|
| competitorUrl | string | yes | Competitor site URL to benchmark against |
| pages | integer | – | Number of pages to scan per site (1-5) |
| url | string | yes | Your site URL |
No output schema declared.
No examples provided.
fix_site ~261
Generate complete fix code for all AI visibility issues across AEO, GEO, and Agent Readiness. Returns working code you can apply directly — schema generation, robots.txt, sitemap, llms.txt, meta tags, structured data, citation signals, entity markup. Also returns two-tier score projections: quick wins (critical + high fixes only) and full implementation ceiling (all fixes). TIP: pass scan_id from a fresh audit_site result (kept 1 hour) to skip the re-crawl — instant response, same price. Content recommendations include research citations. Run scan_site first to see which issues exist. Pay per call ($5.00) via x402 — USDC on Base or Solana. On payment_required, the response includes the full x402 payload with payTo/amount/asset.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Output format: generic or claude_code (optimized for Claude Code) |
| pages | integer | – | Number of pages to analyze (1-10); ignored when scan_id is used |
| scan_id | string | – | id from a recent audit_site response — reuses that crawl (1h TTL), instant response |
| url | string | – | Full URL to generate fixes for (required unless scan_id is given) |
No output schema declared.
No examples provided.
scan_site ~180
Quick AI visibility scan. Returns three scores: AEO Score (0-100, AI search engine findability), GEO Score (0-100, AI citation readiness), and Agent Readiness Score (0-100, AI agent interaction capability). Also returns AI Identity Card with mention readiness (0-100, predicts how likely AI will mention the brand), detected competitors, business profile (commerce/saas/media/general), and top 5 issues. 77+ checks across 12 categories. Free — no API key needed. Does NOT return per-check details or fix code — use audit_site for full breakdown, fix_site for generated fixes, compare_sites to benchmark against a competitor.
| Name | Type | Req | Description |
|---|---|---|---|
| pages | integer | – | Number of pages to scan (1-5) |
| url | string | yes | Full URL to scan (e.g. https://example.com) |
No output schema declared.
No examples provided.
What is the AEO Scanner MCP server?
AEO Scanner is an MCP server listed in the public MCP registry as io.github.Convrgent/aeo-scanner. AI visibility for ChatGPT/Perplexity/Claude, triple score (AEO+GEO+Agent) with fix code. Free. This page covers its hosted endpoint (https://aeo-mcp.convrgent.ai/mcp).
Is the AEO Scanner MCP server safe to use?
AEO Scanner scores 75 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 Scanner MCP server expose?
AEO Scanner exposes 4 tools: scan_site, audit_site, fix_site, compare_sites. Their descriptions and schemas cost roughly 914 tokens of context every time the server is loaded.
Does the AEO Scanner MCP server require authentication?
No. We connected to AEO Scanner without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AEO Scanner MCP server still maintained?
AEO Scanner 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.