AEO Auditor — AI Search & Agent Readiness Engine
REMOTE · API.AEOAUDITING.COM
Live AEO, GEO, JSON-LD Schema, robots.txt AI crawler, and Agent Readiness diagnostic auditor.
Available components
Last scanned (11 hours ago)
Scores higher than 43% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
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 Security49
- 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 3 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 check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 289 tokens (~96/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "audit_domain" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 −6
- Authorization: partial → unverified ▼ security
- Tool “audit_domain” rewrote its description, which is the text the model reads security
- Tool “get_domain_benchmark” rewrote its description, which is the text the model reads security
- Tool “validate_robots_txt” rewrote its description, which is the text the model reads security
- Schema quality: fail → pass ▲ functional
- Schema quality: excellent → good functional
- “audit_domain” reworded the description of “url” cosmetic
- Tool “audit_domain” changed its title: Audit Domain cosmetic
- Tool “get_domain_benchmark” changed its title: Get Domain Benchmark cosmetic
- Tool “validate_robots_txt” changed its title: Validate Robots Txt cosmetic
- 31 Oct 26 +2
- DNSSEC: fail → pass ▲ security
- 30 Oct 26 +7
- Authorization: unverified → partial ▲ security
- Tool “audit_domain” rewrote its description, which is the text the model reads security
- Tool “get_domain_benchmark” rewrote its description, which is the text the model reads security
- Tool “validate_robots_txt” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Schema quality: good → excellent functional
- “audit_domain” reworded the description of “url” cosmetic
- Tool “audit_domain” changed its title: Audit Domain cosmetic
- Tool “get_domain_benchmark” changed its title: Get Domain Benchmark cosmetic
- Tool “validate_robots_txt” changed its title: Validate Robots Txt cosmetic
- 29 Oct 26 56
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 5 Nov 2026 · Probed https://api.aeoauditing.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=aeoauditing.com | CN=WE1,O=Google Trust Services,C=US | 22 Oct 2026 | 20 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | af9cafb5e0d8e1d413a5778eac9b3666 |
| SANs: aeoauditing.com, api.aeoauditing.com, *.api.aeoauditing.com | ||||||
| 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 secure
Validation of api.aeoauditing.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| aeoauditing.com. | DS published | 2371 | 13 | Verified |
| api.aeoauditing.com. | Verified address RRset verified with the apex keys |
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://api.aeoauditing.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.aeoauditing.com/mcp | Served over HTTP | 200 |
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_domain ~84
Execute a live real-time Answer Engine Optimization (AEO), Generative Engine Optimization (GEO), JSON-LD Schema AST, and AI Agent Readiness (/llms.txt & /.well-known) diagnostic audit on any domain or URL.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Target domain or full URL to audit (e.g. "stripe.com" or "https://stripe.com"). |
No output schema declared.
No examples provided.
get_domain_benchmark ~99
Look up a domain AEO readiness benchmark score and 4-pillar breakdown, or query the industry leaderboard directory.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional industry category filter when listing leaderboard benchmarks (e.g. "AI & ML", "FinTech", "DevTools", "SaaS"). |
| domain | string | – | Optional domain name to retrieve benchmark profile (e.g. "openai.com"). Omit to list top leaderboard domains. |
No output schema declared.
No examples provided.
validate_robots_txt ~106
Validate a robots.txt file or live domain robots.txt against 10 AI search crawlers (GPTBot, ChatGPT-User, PerplexityBot, ClaudeBot, Google-Extended, Applebot-Extended, etc.) and generate a 100/100 compliant configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | Optional domain to fetch live /robots.txt from (e.g. "example.com"). |
| robotsTxtContent | string | – | Optional raw robots.txt content string to validate directly. |
No output schema declared.
No examples provided.
How do I install the AEO Auditor — AI Search & Agent Readiness Engine MCP server?
AEO Auditor — AI Search & Agent Readiness Engine is a hosted endpoint at https://api.aeoauditing.com/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 · api.aeoauditing.com
claude mcp add --transport http com-aeoauditing-aeo-auditor-mcp 'https://api.aeoauditing.com/mcp'
What is the AEO Auditor — AI Search & Agent Readiness Engine MCP server?
AEO Auditor — AI Search & Agent Readiness Engine is an MCP server listed in the public MCP registry as com.aeoauditing/aeo-auditor-mcp. Live AEO, GEO, JSON-LD Schema, robots.txt AI crawler, and Agent Readiness diagnostic auditor. This page covers its hosted endpoint (https://api.aeoauditing.com/mcp).
Is the AEO Auditor — AI Search & Agent Readiness Engine MCP server safe to use?
AEO Auditor — AI Search & Agent Readiness Engine scores 61 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 Auditor — AI Search & Agent Readiness Engine MCP server expose?
AEO Auditor — AI Search & Agent Readiness Engine exposes 3 tools: audit_domain, get_domain_benchmark, validate_robots_txt. Their descriptions and schemas cost roughly 289 tokens of context every time the server is loaded.
Does the AEO Auditor — AI Search & Agent Readiness Engine MCP server require authentication?
No. We connected to AEO Auditor — AI Search & Agent Readiness Engine without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AEO Auditor — AI Search & Agent Readiness Engine MCP server still maintained?
AEO Auditor — AI Search & Agent Readiness Engine 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 Auditor — AI Search & Agent Readiness Engine MCP server?
VerifyMCP ran 12 checks on AEO Auditor — AI Search & Agent Readiness Engine, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about AEO Auditor — AI Search & Agent Readiness Engine: Authorization. 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.