
Company News
Free Business Plan Upgrades for Open Source Maintainers
Open source maintainers are under more pressure than ever. We're raising our open source program from the Team plan to the Business plan, free.
aeo-scanner
Advanced tools
MCP server for AI search visibility auditing. Triple scoring: AEO (search findability), GEO (citation readiness), Agent Readiness (agent interaction). Plus AI Identity Card and business profile detection.
AI search visibility audit for any website. Three scores, one scan.
Remote server (recommended) — zero install, just add the URL:
# Claude Code
claude mcp add --transport http aeo-scanner https://aeo-mcp.convrgent.ai/mcp
# Claude Desktop / Claude.ai
# Settings → Connectors → Add custom connector → https://aeo-mcp.convrgent.ai/mcp
# Cursor — add to .cursor/mcp.json
{ "aeo-scanner": { "url": "https://aeo-mcp.convrgent.ai/mcp" } }
Then ask your AI assistant: "Scan example.com for AI visibility"
Alternative: local install via PyPI (stdio transport):
claude mcp add aeo-scanner -- uvx aeo-scanner
| Tool | What it does | Price |
|---|---|---|
scan_site | Quick triple-score scan + AI Identity Card + mention readiness + business profile + top issues | Free |
audit_site | Full 77+ check breakdown across 12 categories (4 AEO + 4 GEO + 4 Agent) | $1.00 |
compare_sites | Two-site gap analysis + category winners + overtake fix code | $3.00 |
fix_site | Generated fix code with two-tier score projections — apply directly with Claude Code | $5.00 |
scan_site works without any authentication. No API key, no wallet, no setup.
Rate limits: 20 scans/hour per IP, 5 per URL per day.
audit_site, compare_sites, and fix_site are pay-per-call via the x402 protocol — USDC on Base or Solana. No API key, no account.
Without payment, the tool returns a structured payment_required error containing the full x402 payload (payTo address, amount, asset). x402-capable clients retry automatically with a signed X-PAYMENT header; other agents can relay the payment details to their operator.
The included optimize_site prompt guides the full workflow:
77+ checks across 12 categories. See the built-in aeo://reference/scoring-methodology resource for full details.
AEO categories: Structured Data (30%), Meta & Technical (20%), AI Accessibility (25%), Content Quality (25%)
GEO categories: Brand Narrative Clarity (25%), Citation Readiness (25%), Authority Signals (25%), Entity Definition (25%)
Agent Readiness categories: Machine Identity (30%), API Discoverability (25%), Structured Actions (25%), Programmatic Access (20%)
Grades: A (90+), B (75-89), C (60-74), D (40-59), F (0-39)
GEO checks are backed by peer-reviewed research: Princeton KDD 2024 (+115% visibility from citing sources), Growth Memo (44.2% citations from first 30% of content), Cornell (+28% from quantitative claims), and more. See scoring methodology for full citations.
Built by Convrgent — AI visibility tools for agents.
FAQs
MCP server for AI search visibility auditing. Triple scoring: AEO (search findability), GEO (citation readiness), Agent Readiness (agent interaction). Plus AI Identity Card and business profile detection.
The pypi package aeo-scanner receives a total of 114 weekly downloads. As such, aeo-scanner popularity was classified as not popular.
We found that aeo-scanner demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Company News
Open source maintainers are under more pressure than ever. We're raising our open source program from the Team plan to the Business plan, free.

Security News
The supply chain control that delays freshly published gems now covers lockfile generation and gem vendoring in Ruby projects.

Security News
During a UK cyber test, a Mythos 5 agent used sockpuppets, social engineering, and prompt injection to try to get a maintainer to merge malware.