What does the agent readiness check test?

Real protocol probes of .well-known files (openapi.json, mcp.json, ai-plugin.json, security.txt), a live MCP initialize handshake, A2A agent-card validation, a 20-user-agent crawler audit, and a JS-parity check.

Is glassesusa.com ready for AI agents?

AI agent readiness report · platform: Custom · checked 2026-10-20 · log in to re-run

11%

Readiness

1/9

Verified

Custom

Platform

Not agent-ready

Mcp

Webmcp

A2a

Anp

Ucp

Ap2

Openapi

Llms Txt

Wikidata

18/18 AI crawlers reached the homepage0 blocked

Ranks above 17% of 127 sites checkedcorpus avg 24/100

Not agent-ready

glassesusa.com has 1 of 9 readable agent standards in place; missing Mcp, Webmcp, A2a, Anp, Ucp, Ap2, Openapi, Llms Txt.

Assessment

1 of 9 readable agent-readiness checks verified. See per-protocol drawers for evidence and fix-it files.

Per-protocol verdicts

Mcpno /.well-known/mcp.json, /mcp, or /.well-known/mcpNot found

Webmcpno navigator.modelContext.register, <script type="webmcp">, or <link rel="modelcontext"> in HTMLNot found

A2ano /.well-known/agent.json or /.well-known/agent-card.jsonNot found

Anpno /.well-known/did.jsonNot found

Ucpno /.well-known/ucpNot found

Ap2no /.well-known/ap2.jsonNot found

Openapino /openapi.json, /api/openapi.json, or /.well-known/openapi.jsonNot found

Llms Txtno /llms.txtNot found

WikidataWikidata entity Q25245502 (GlassesUSA)Verified

.well-known files

.well-known/mcp.json580 bytes247

Mcp Well Known Alt580 bytes247

/mcp endpoint580 bytes247

Ai Plugin Legacy580 bytes247

.well-known/agent.json580 bytes247

.well-known/agent-card.json580 bytes247

Anp Did580 bytes247

Openapi Well Known580 bytes247

Openapi Root580 bytes247

Openapi Api580 bytes247

Ucp Profile580 bytes247

Ap2 Well Known580 bytes247

Llms Txt580 bytes247

Llms Full Txt580 bytes247

robots.txt580 bytes247

sitemap.xml580 bytes247

AI crawler audit

18 of 18 AI user-agents reached the homepage.

9 of 18 were tested with the operator's published user-agent string and the rest with the bare token, since no published string was found. A request that only names a user-agent does not prove the real crawler would be treated the same.

What this means for glassesusa.com

On glassesusa.com (Custom), 1 of 9 readable agent standards are in place: Wikidata. Missing: Mcp, Webmcp, A2a, Anp, Ucp, Ap2, Openapi, Llms Txt.

Without JavaScript, your brand name does not appear in the raw HTML, so crawlers that do not run JS see an empty shell.

glassesusa.com scores higher than 17% of the 127 sites checked here so far; the average readiness score is 24/100.

Make glassesusa.com agent-ready

Start with the highest-impact gap: Mcp. Publish a working MCP endpoint at /.well-known/mcp.json (the initialize handshake must succeed, not just return 200), add an A2A agent card, and keep the crawler path clean.

Frequently asked questions

Are these real probes or AI guesses?

Real probes. We fetch the actual files, run a real MCP initialize handshake, and validate A2A cards against their schema. No model decides a verdict.

Does glassesusa.com need every standard to pass?

No. Start with the highest-impact gap above, then add the rest. Most sites win the most by shipping a working MCP endpoint and keeping the crawler path clean.

Check your own site free

Run the same protocol probes on any URL, then sign up free for the copy-paste fix-it files and the full 20-crawler audit.

Run a free check

Agent readiness on Custom

We have checked 64 other sites on Custom. The Custom hub aggregates protocol verification rates and average readiness scores across every Custom site checked here.

Is Custom ready for AI agents?