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 vans.com ready for AI agents?

AI agent readiness report · platform: Custom · checked 2026-09-04 · 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

0/20 AI crawlers reached the homepage20 blocked

Ranks above 17% of 66 sites checkedcorpus avg 26/100

Not agent-ready

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

Assessment

1 of 9 agent-readiness checks verified. 20 AI crawler(s) blocked at the edge despite robots.txt allowing them. 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/agentic-commerce.json (and platform is not a UCP-shipping host)Not 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 Q1135366 (Vans)Verified

.well-known files

.well-known/mcp.jsonnot found403

Mcp Well Known Altnot found403

/mcp endpointnot found403

Ai Plugin Legacynot found403

.well-known/agent.jsonnot found403

.well-known/agent-card.jsonnot found403

Anp Didnot found403

Openapi Well Knownnot found403

Openapi Rootnot found403

Openapi Apinot found403

Ucp Well Knownnot found403

Ap2 Well Knownnot found403

Llms Txtnot found403

Llms Full Txtnot found403

robots.txt668 bytes200

sitemap.xmlnot found403

AI crawler audit

0 of 20 AI user-agents reached the homepage; 20 were blocked despite robots.txt allowing them.

GPTBotHTTP 403Blocked

OAI-SearchBotHTTP 403Blocked

ChatGPT-UserHTTP 403Blocked

anthropic-aiHTTP 403Blocked

ClaudeBotHTTP 403Blocked

Claude-UserHTTP 403Blocked

Claude-SearchBotHTTP 403Blocked

PerplexityBotHTTP 403Blocked

What this means for vans.com

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

Without JavaScript, your brand name still appears in the raw HTML, so crawlers that do not run JS can read it.

vans.com scores higher than 17% of the 66 sites checked here so far; the average readiness score is 26/100.

Make vans.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 vans.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 16 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?