Agent readiness report

Is advanceautoparts.com ready for AI agents?

AI agent readiness report · platform: Unknown · checked 2026-11-07 · log in to re-run
11%
Not agent-ready
advanceautoparts.com · 6 standards read
advanceautoparts.com has 1 of 6 readable agent standards in place; missing Mcp, A2a, Ucp, Ap2, Llms Txt. 3 could not be read because the site refused our request (Webmcp, Anp, Openapi), so they are not counted.
Not agent-readyUnknown1/6 readable verified
Agent standards verified1/6
Mcp
Webmcp
A2a
Anp
Ucp
Ap2
Openapi
Llms Txt
Wikidata
10/18 AI crawlers reached the homepage (8 blocked)56%
Ranks above 46% of 285 sites checked (corpus avg 21/100)46%

Assessment

1 of 6 readable agent-readiness checks verified (3 could not be read: the site refused our request). Our request with an ordinary browser user-agent was refused too, so the crawler results describe our checker being blocked, not rules about AI crawlers. See per-protocol drawers for evidence and fix-it files.

Per-protocol results

Mcpno MCP endpoint declared in /.well-known/ucp, and none at the draft discovery addresses /.well-known/mcp.json, /.well-known/mcp or /mcp (MCP has no agreed discovery address yet)Not found
Webmcpcould not read the homepage HTML, so page-source markers could not be checkedCould not read
A2ano /.well-known/agent.json or /.well-known/agent-card.jsonNot found
Anpcould not read /.well-known/did.json (520) - the site refused our request, so this is not a findingCould not read
Ucpno /.well-known/ucpNot found
Ap2no /.well-known/ucp, so no AP2 declaration (AP2 is declared as a UCP capability)Not found
Openapicould not read /api/openapi.json (520) - the site refused our request, so this is not a findingCould not read
Llms Txtno /llms.txtNot found
WikidataWikidata entity Q4686051 (Advance Auto Parts)Verified

.well-known files

.well-known/mcp.json6138 bytes200
Mcp Well Known Alt6138 bytes200
/mcp endpoint6138 bytes200
Ai Plugin Legacycould not read520
.well-known/agent.json6138 bytes200
.well-known/agent-card.json6138 bytes200
Anp Discovery6138 bytes200
Anp Didcould not read520
Openapi Well Known6138 bytes200
Openapi Root6138 bytes200
Openapi Apicould not read520
Ucp Profile6138 bytes200
Llms Txtnot found404
Llms Full Txtnot found404
robots.txt977 bytes200
sitemap.xml6138 bytes200

AI crawler audit

10 of 18 AI user-agents reached the homepage.
Our request with an ordinary browser user-agent was refused as well (HTTP 200 before, 0 after). This site was blocking our checker, so read these counts as "could not check", not as rules about AI crawlers.
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.

Fix these first

  1. Let our checker read your site: 3 of our checks could not be read (WebMCP, ANP, OpenAPI), so they are left out of your score. Serve /.well-known/*, /llms.txt and /robots.txt to automated requests without a block or a redirect, then run the check again.
  2. llms.txt: Publish /llms.txt: a plain text file at your site root that lists your key pages (main categories, best sellers, shipping and returns) with one line on each. You can write it yourself in an hour.
  3. UCP: Publish a UCP profile at /.well-known/ucp so AI agents can find your catalog, cart and checkout. Shopify serves one for every store; on other platforms it takes an app or a developer.
  4. MCP: Run an MCP server and declare it, for example at /.well-known/mcp.json, so AI assistants can search your catalog as a tool. The initialize handshake has to succeed, not just return a 200.
  5. A2A: Publish an A2A agent card at /.well-known/agent.json if you run an agent that other agents can hand tasks to.
Run it again for today's result, then sign up free for one fix file per gap. Not yours? Put your own store in.

What this means for advanceautoparts.com

On advanceautoparts.com (Unknown), 1 of 6 readable agent standards are in place: Wikidata. Missing: Mcp, A2a, Ucp, Ap2, 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.

advanceautoparts.com scores higher than 46% of the 285 sites checked here so far; the average readiness score is 21/100.

Make advanceautoparts.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 the result.

Does advanceautoparts.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 Unknown

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

Is Unknown ready for AI agents?